1. Home
  2. Companies
  3. Waze
  4. Outage Map
Waze

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

Loading map, please wait...

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:

Less
More
Check Current Status

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
Pierre-Bénite, Auvergne-Rhône-Alpes 1
Manaus, AM 1
Paris, Île-de-France 15
Guimarães, Braga 1
Chamonix-Mont-Blanc, Auvergne-Rhône-Alpes 1
Montreuil, Île-de-France 1
Marseille, Provence-Alpes-Côte d'Azur 3
Épernay, ACAL 1
La Chapelle-Janson, Brittany 1
Châteauroux, Centre 1
Algiers, Algiers 1
Les Mureaux, Île-de-France 1
‘Ewa Beach, HI 1
Angoulême, Nouvelle-Aquitaine 1
Le Chesnay, Île-de-France 1
Meyreuil, Provence-Alpes-Côte d'Azur 1
Brussels, Brussels Capital 2
San Carlos, CA 1
Chantonnay, Pays de la Loire 1
Pittsburgh, PA 1
Bear, DE 1
Norristown, PA 1
Orlando, FL 1
Champigny-sur-Marne, Île-de-France 1
Pontivy, Brittany 1
Washington, D.C., DC 1
Marlborough, MA 1
Atwood, KS 1
Rio de Janeiro, RJ 1
Bordeaux, Nouvelle-Aquitaine 1
Check Current Status

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:

  • ItsBig_Earl
    Bobby Boulders (@ItsBig_Earl) reported

    @Proctor4Gov @Maggie725496820 Slowed down in speed for 0.6 seconds but didn’t record any collisions? If she hit John on the road moving in the opposite direction of the flagpole…how ******** did he end up over by the flagpole? If Higgins jeep was parked at the mailbox how come she didn’t crash right into it? You see how other details matter when you’re trying to claim this ridiculous collision? If the TL collided with his arm how’s he get the cut on the eyelid and nose and such bruised knuckles but zero bruising on the arm where he was supposedly hit? The marks on the arm (32) caused by only 9 little holes…no tearing, no leftover pieces in the sleeve…again, **** your janky Waze correlation and address the injuries.

  • ihtesham2005
    Ihtesham Ali (@ihtesham2005) reported

    A 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.

  • blessedbanele
    Blessed sibanda (@blessedbanele) reported

    @SengezoTsh17075 Ndoda waze asithengisa libalele nje do you even think about what you doing and I think ndebele people we should work up we can fix this by other means like ke this tshabangu guy should pay for what he did and what he's doing

  • JohnHawkin71262
    John_Hawkins (@JohnHawkin71262) reported

    @ClimateWarrior7 I just drive at normal speeds and slow down for the cameras. Use Waze and even alerts you to police mobile cameras. Never any points.

  • RobConquistador
    Rob Conquistador (@RobConquistador) reported

    @RobH02050318 @WallStreetApes Most self driving vehicles are going to induction charging. Think like the iPhone mag safe chargers. They would just park over the charger. The braking system is regenerative so they don’t need to be replaced as often as normal brakes. The sensors in the vehicle would allow the person at a main hub to see everything related to the vehicle like tire pressure, battery life, etc. GPS like Waze operate in realtime and many partner with the weather to warn of things like high winds and forest fires. Only issues I see are building the infrastructure (which the mass production of cybercabs this year will accelerate) and states adjusting their regulations to better accommodate self driving.

  • 1zSolace
    Mark (@1zSolace) reported

    @waze why does every intersection I pass, Waze thinks I am turning at? Every time the map turns thinking I turned when I never even touched the wheel. Can you fix that?

  • ben_toto23
    Ben (@ben_toto23) reported

    @TheHauskarl I agree 100%. Early 2025 this got very real for me. It emerged that the UK government had secretly served Apple with a Technical Capability Notice under the Investigatory Powers Act, demanding access to end to end encrypted iCloud data. Apple's response? They didn't weaken the system for everyone. Instead they pulled Advanced Data Protection, their best iCloud encryption option, for UK users. What really stuck with me wasn't just the demand. It was the secrecy. These notices come with a legal gag order. Companies aren't allowed to tell anyone they've received one. The only reason any of us know is that the story leaked to the press. Apple itself was never allowed to confirm it. Only Apple was named in the initial reports, with zero confirmation either way about Google or others. By design that silence tells you nothing. You're simply not meant to know this is happening. (see below for link to articles). That's when the alarm bells really rang for me. I've since built my own private setup. A Raspberry Pi handles my encrypted offsite backups. My phone runs GrapheneOS. My ThinkPad runs Debian. This fully replaced Google Drive and iCloud. The same principle applies to software. LibreOffice does everything I used to need Microsoft 365 for, free, private, and with nothing phoning home. For most paid tools solid open source alternatives exist if you look. For cheap offsite backups: Hetzner Storage Boxes, 1 TB for around 3.20 euros per month plus VAT, 5 TB for around 11.40 euros per month. Excellent value. Add Infomaniak (Swiss) as a second target. It sits outside the EU and UK entirely. For phone backups I use Syncthing on GrapheneOS. It syncs documents and photos directly to my Pi over my own private network, no third party accounts involved. The files stay on hardware I control. On the phone I also switched to Organic Maps (ditching Google Maps/Waze). You lose live traffic but I would rather keep my location data to myself. My documents and photos live on my own devices and back up to storage I fully control. Nothing important sits on services I can't inspect. The bigger issue is the devices themselves. Anything that phones home is a hard no for me. Firesticks, voice speakers, smart home gadgets and so on. They are designed to send data back constantly, often without clear visibility. Fitbit stands out because it is owned by Google. Every step, heartbeat and sleep record goes straight to them. Fun fact: Fitbit data has already been used as evidence in court cases. The same privacy logic applies to GrapheneOS on my phone. If a device can't be trusted to stay quiet it gets replaced. With digital ID and age verification rolling out fast, now is a good time to audit what you're storing where, what devices you're bringing into your home, and what data you're feeding into cloud based AI tools. My rule of thumb: Whenever something digital feels too convenient, ask yourself: what is this really going to cost me?

  • Lean78
    Lean (@Lean78) reported

    @zeerusli @waze Same problem!!

  • ginjajedi
    Peter Miles (@ginjajedi) reported

    @DanielCars05 Anybody had any issues getting sound from waze when using one of these?

  • lilwaynekennedy
    Wayne Kennedy (@lilwaynekennedy) reported

    This is the exact thing I've been saying. These ******* clowns don't speak English, have no idea where they are going and will cross five lanes of traffic last minute to hit an exit because their Waze is slow. I've seen mother ******* backing up on DVP exits. @OPP_HSD

  • Tshepo_McStina1
    Jizas MacStina (@Tshepo_McStina1) reported

    @KayMatthews_10 @LimChronicle Problem is some see cops and assume waze will automatically know

  • themattosborn
    Matt Osborn (@themattosborn) reported

    @FSDyinzer @TheAccuracyPoli @Teslarati 💯 That is exactly what I was talking about. It is quite frustrating. There are plenty of navigation systems out there that they could model from. Why is it still an issue? And their map data is pretty old as well. A peer managed mapping system similar to Waze would be awesome.

  • ottabag
    OTTA 💰 (@ottabag) reported

    How do I fix my Waze or Google maps my **** keeps teleporting me

  • sned
    Snedley Grassbuckets (@sned) reported

    @wholemars Fix the bloody navigation. Use a reliable mapping service with local editors who fix problems quickly -- aka Waze.

  • Buqhawe
    Maqhawe Simelane (@Buqhawe) reported

    @zizipho50 Waze wayisilima we Oros, working with other countries is what we need, illegal immigrants must go back home and fix their papers.

Check Current Status