Waze Outage Map
The map below depicts the most recent cities worldwide where Waze users have reported problems and outages. If you are having an issue with Waze, make sure to submit a report below
The heatmap above shows where the most recent user-submitted and social media reports are geographically clustered. The density of these reports is depicted by the color scale as shown below.
Waze users affected:
Waze is GPS navigation software that works on smartphones and tablets with GPS support and provides turn-by-turn navigation information and user-submitted travel times and route details, while downloading location-dependent information over a mobile telephone network.
Most Affected Locations
Outage reports and issues in the past 15 days originated from:
| Location | Reports |
|---|---|
| Lyon, Auvergne-Rhône-Alpes | 6 |
| Paris, Île-de-France | 10 |
| Orléans, Centre | 1 |
| Romoos, LU | 1 |
| Zürich, ZH | 1 |
| Le Mont-sur-Lausanne, VD | 1 |
| Bordeaux, Nouvelle-Aquitaine | 2 |
| Nancy, ACAL | 1 |
| Angers, Pays de la Loire | 1 |
| Nîmes, Occitanie | 1 |
| Nantes, Pays de la Loire | 1 |
| Aldershot, England | 1 |
| Weiler-Simmerberg, Bavaria | 1 |
| Givors, Auvergne-Rhône-Alpes | 1 |
| Montreuil, Île-de-France | 1 |
| Marseille, Provence-Alpes-Côte d'Azur | 1 |
| Lège-Cap-Ferret, Nouvelle-Aquitaine | 1 |
| Guayaquil, Guayas | 1 |
| Bléré, Centre | 1 |
| Sartrouville, Île-de-France | 1 |
| Pierrefitte-Nestalas, Occitanie | 1 |
| Achères, Île-de-France | 1 |
| Curitiba, PR | 1 |
| Montauban, Occitanie | 1 |
| São Paulo, SP | 2 |
| Sandillon, Centre | 1 |
| Saint-Jean-de-Maurienne, Auvergne-Rhône-Alpes | 1 |
| Bertrange, ACAL | 1 |
| Toulouse, Occitanie | 1 |
| Pierre-Bénite, Auvergne-Rhône-Alpes | 1 |
Community Discussion
Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.
Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.
Waze Issues Reports
Latest outage, problems and issue reports in social media:
-
Joshua (@xzinft) reported@Baloney_and @THPLawrencebur Waze could also identify those flocks and we’d just slow down b4 it
-
Robert (@berge789) reported@AVGirl4Life 🇺🇸🇺🇸🇺🇸. If you assimilate to our Waze, we have no problem, but when you want to put your ideals in place, this is a problem. My country is full of capitalist not monarch.
-
Jack (@jackcoder0) reported1. Waze the speed trap app that saves you $200+ in tickets per year. The 2026 CarPlay interface for Waze is cleaner than ever, offering crowd-sourced data on speed traps, potholes, and traffic jams without cluttering your digital real estate. Waze is the one CarPlay app every driver should install regardless of whether they use it for navigation. Waze is the go-to CarPlay app for drivers who regularly deal with heavy traffic. Its community-sourced reporting system alerts you to accidents, road hazards, speed traps, and police presence in real time, often before other apps catch up. Real-time alerts from other Waze drivers: police ahead. Speed trap. Red light camera. Construction. Hazard on the road. Car stopped on the shoulder. Object in the road. You're driving 72 in a 65. A Waze alert pops up: "Police reported ahead." You slow to 65. You pass the speed trap. No ticket. The driver behind you without Waze gets pulled over. One avoided speeding ticket: $150-300. One avoided red light camera ticket: $75-150. Waze is free. The math is obvious. Beyond speed traps: Waze frequently finds faster routes than Apple Maps during heavy traffic because its routing algorithm uses real-time data from millions of active drivers, not just historical traffic patterns. If a highway exit is suddenly backed up because of a fender bender reported 3 minutes ago Waze reroutes you before Apple Maps knows it happened.
-
DeweyCheatemandHowe (@Obiewann) reportedVerizon Cell Services still not working for Google Waze in Central Va. I81
-
Stay focused 🇹🇹 (@caribehijabi) reportedWaze not working ???
-
Anoop Rao K | ಅನೂಪ್ ರಾವ್ (@anoopraok) reportedThis UI bug is causing lots of issues because I can't see the exit number and during driving I have to keep on seeing the map to exactly see the exit on maps and not the exit number on the top. @Waze_UAE @waze #waze
-
Nigel Poncewattle (@poncewattle) reported@oi8achevy @diaper @TeslaKing420 Also hate to say this, but Tesla does not use Waze nor Google for speed limit data so it won't fix THAT problem.
-
AnonyMassLawyer (@anonymasslawyer) reported@Suzybeau1 @Martine05885145 The WiFi login time came from Karen’s phone. Guarino’s testimony. Uncontested. The GPS data can be wrong within its stated error range, which was very small while Waze was activated.
-
crazy people out there (@ron_doingstuff) reported@congressdj @Spencer10438140 I was trying to get waze working, so at least it would alert me. I was having issues with waze bluetooth talking over the tesla audio. I could not hear both at the same time. Grok said there was some browser version of tesla waze. Too busy to figure this out so far :)
-
NancyH (@NancyH_60) reported@gotrice2024 20 minutes is brutal—I’ve been stuck nearly that long on a slow freight crawl with no U-turn option. Best move is to use Maps/Waze for detours on known problem crossings and always treat malfunctioning gates as active: better late than risking it. What’s your usual route?
-
Ihtesham Ali (@ihtesham2005) reportedA mathematician invented the algorithm inside every GPS on earth while sitting in a café in Amsterdam with no pen and no paper, worked it out in his head in 20 minutes, and did not bother publishing it for three years. His name was Edsger Dijkstra. He was born in Rotterdam in 1930, the son of a chemist father and a mathematician mother. He studied mathematics and physics at the University of Leiden, earned his PhD in computing from the University of Amsterdam in 1959, and became the first professional programmer in the Netherlands at age 21. The café story is real, and the detail that makes it strange is this: he was not trying to solve a famous problem. He was trying to find a demo impressive enough for a public audience. In 1956, his lab at the Mathematical Centre in Amsterdam had just finished building a new computer called the ARMAC. They needed to show it off at an inauguration ceremony to an audience of non-technical people. Dijkstra needed a problem that regular people could understand, with an answer they could verify. He landed on one: given a map of Dutch cities connected by roads, what is the shortest route between two of them? He was shopping with his fiancée Ria in Amsterdam when the solution came to him. They stopped at a café. He sat down, no paper, no pencil, and spent 20 minutes working through it entirely in his head. When he stood up, he had the algorithm. He used it for the inauguration. It worked. He then filed it away and did not publish it for three years because, as he later explained, he was not sure it was worth a paper. He thought it was too simple. That algorithm now has a name. Dijkstra's algorithm. It finds the shortest path between any two points in a network. Every GPS navigation system on earth runs it when you ask for directions. Every internet router runs it to decide where to send your data packets. Every airline uses it for flight path optimization. Every logistics company uses it to route deliveries. Google Maps, Apple Maps, Waze, every mapping tool you have ever opened, all of them are running a version of what one Dutch mathematician worked out in his head over a cup of coffee in 1956. He did not stop there. In 1965 he invented the concept of the semaphore, the mechanism that lets multiple programs share a computer's resources without crashing into each other. Every operating system on earth uses semaphores. Every time your phone runs ten apps at once without any of them corrupting each other's memory, that is Dijkstra's idea holding things together underneath. In 1968 he published a two-page letter to a computing journal with the title "Go To Statement Considered Harmful." The letter argued that a common programming instruction called goto, which let a program jump to any arbitrary point in its own code, was making programs impossible to understand and debug. He called for removing it from all serious programming languages entirely. The letter caused an immediate uproar. Programmers who had built careers on goto were furious. Dijkstra received angry letters for years. The programming community eventually concluded he was completely right. The structured programming approach he was advocating, where code flows through clear, predictable logic rather than jumping unpredictably around, became the foundation of how every modern programming language is designed. Python, JavaScript, Java, C#, every language you can name was built around the principle Dijkstra defended in two pages in 1968. He won the Turing Award in 1972. Now the part almost nobody knows. Dijkstra refused to own a television. He refused to own a video player. He never owned a mobile phone. He never sent an email. His house in Nuenen in the Netherlands was small and plain. He played the piano and listened to Mozart. From the early 1970s until his death in 2002, he wrote every research paper, every technical note, every letter, and every lecture by hand with a fountain pen. He numbered them sequentially using his initials as a prefix: EWD. EWD1, EWD2, all the way to EWD1318, his last note, written four months before he died. When he finished each one, he made photocopies and mailed them to colleagues around the world. That was his publishing system. Fountain pen, paper, photocopier, post office. More than 1,300 of those handwritten documents have been scanned and are now archived at the University of Texas. Researchers still read them. New papers still cite them. His reasoning for refusing computers in his own work was precise, not eccentric. He believed that the friction of writing by hand forced him to think more carefully before committing anything to paper. The ease of editing on a computer, he thought, made it too tempting to produce volume instead of clarity. He wanted every sentence to be worth the effort of writing it. He died on August 6, 2002, in Nuenen. He was 72. The man who invented the algorithm your phone uses to give you directions never used a phone. The man who shaped how every programmer writes code wrote his own work exclusively by hand. The man whose ideas run silently inside every connected device on earth chose to live without almost all of them. He just wanted to think clearly. Everything else followed.
-
AMPed UP (@DoublepPradhan) reported@bauminater I always have WAZE on while my phone is on the charger. and look at it to see where cops . do the same!! I ensure to slow down before about 3/4 miles prior. Problem solved
-
Dr Prakash Nayak (@SRIPRAKASH76) reportedWe had major problem following Waze directions traveling from London to Folkestone . Near or around Maidstone there was some road blocks. Waze kept sending us in circles repeatedly asking to take closed roads. It was getting dark. Stopped to download TomTom. @waze
-
nycwest45th (@westforties) reported@realericmoutsos @leahfiles who is ever going to have a problem with an app like WAZE that you would need to go to their home office?!
-
matt kalita (@mattkalita) reported@PatsKam Both of the mapping software that most people use Apple or Google maps even Waze, which is now Google anyways use the data from the phones so if a bunch of phones are sitting over a GPS location of a highway they’ll put that red as in stop traffic if it’s slow slowly moving from point a to point B they’ll color yellow and if it’s flowing, they’ll color it the green or blue whatever you have set It’s all based upon your phone data location And everyone else’s phone data location on the roadways