Waze Outage Map

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:

• 
  Definitely Not Allen Covert (@Covert61) reported 32 seconds ago

  If there is a huge traffic jam and WAZE shows me a different route that can save me time is Waze ignoring my issue and telling me to shut up or is it offering a temporary solution to my immediate problem?

• 
  DebtCollector (@DebtCollector15) reported 2 minutes ago

  @OGsDontFold Google Maps is so trash. Randomly won't give audio updates for turns, suggests locations further away for no sensible reason, randomly loses connection and stops updating directions. I have tried Waze and it gives me similar problems. There is no winning these days.

• 
  NMH (@nosmh_x) reported 4 minutes ago

  How my car crash happened At around 5:10 I was driving in Jackson on East Veterans Highway and I missed a left turn into Bowman Road, instead of doing the right thing I decided to make a “k turn” (the road wasn’t wide enough for a “u turn” since it was just 2 lanes, 1 each side) So I looked both ways, there wasn’t a car in the incoming lane for a while so I was safe there, there was a pickup truck behind me by quite a distance and against my better judgment I decided to make that “k turn” Anyways as I’m in middle of doing it and I’m in the OTHER lane I suddenly realize that the pick up drunk that was behind me is now trying to cut me off and was speeding at a much higher speed on the OTHER lane Before I knew what was going on he (I assume it was a man) went straight into me and I rolled over at least once and was then held upside down by my seatbelt Anyways I then hear a voice (I think from Waze) “were you in an accident?”, I said “yes”, “would you like to call emergency services?” And apparently they dialed 911 from my phone

• 
  jdx (@jdxcode) reported 5 minutes ago

  @TheLaluka @waze @gouvernementFR I suspect if you were asking in the US they'd want nothing to do with it for liability reasons, no idea if there would be similar issues in France

• 
  Bob Nordberg Bird Man Bob (@birdmanbob4) reported 8 minutes ago

  @leahfiles Here's your reply from the AI that just don't lie Speculative Intelligence Analysis: Waze as a Compromise Vector Location Pattern Exploitation**: Waze's continuous GPS pings, route history, speed data, and timestamps create a granular digital shadow of a target's movements—revealing regular visits to sensitive locations (e.g., hotels, clinics, private residences, or protest sites). An intelligence actor with access could cross-reference this against public records, social media, or other surveillance to build "kompromat" dossiers on affairs, medical issues, financial dealings, or undisclosed associations, then use timed leaks or implied exposure to coerce compliance, payments, or information. Real-Time and Predictive Targeting**: Live traffic/ETA data allows dynamic interception or influence operations—knowing exactly when someone is isolated in a vehicle or arriving at a vulnerable spot. Combined with app permissions (microphone/camera in some scenarios, or linked device data), it could enable opportunistic collection of audio/visual compromising material or facilitate "honey-trap" logistics by predicting availability and routes for assets. Historical data also predicts future behavior for pre-positioning. Network and Ecosystem Amplification**: Since Waze feeds into Google's broader data lake (and originated as an Israeli-founded company subject to local laws), aggregated user data can be queried at scale for social graph mapping—identifying who travels together, meets whom, and when. In a full compromise scenario, this integrates with OSINT, hacked devices, or partner-nation sharing to pressure targets via family/financial exposure, or even engineer "accidents"/discrediting events by manipulating perceived travel patterns. Privacy controls are weak once data leaves the device, and legal jurisdiction adds layers for state actors. This remains hypothetical and draws from known app telemetry practices. Actual misuse would require lawful (or illicit) access and is constrained by laws in most jurisdictions; strong operational security (VPNs, app isolation, location spoofing, minimal permissions) mitigates much of it.

• 
  David Makogon (@dmakogon) reported 10 minutes ago

  @AustyUSA Don’t forget all the people who hate on CarPlay, with snarky comments like… comparing to a coke freestyle machine. Tesla software is nowhere near perfect. Map/direction issues, non-trivial air control, small fonts & touch zones, no Waze, no proper group texts, on and on.

• 
  Noam Bardin (@noam) reported 13 minutes ago

  Launched a little experiment @maptoearn. User reports at Waze were always a scaling problem. Trying to fix it with incentives this time. x $M2E per report. No expectations, just a side project.

• 
  Ihtesham Ali (@ihtesham2005) reported 15 minutes ago

  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.

• 
  Matsobane ke lebitšo laka fela (@MatsobaneKgomo) reported 15 minutes ago

  Waze has been absolutely useless these days!!! @waze fix your nonsense

• 
  Just4usewith_thisapp (@just4usewith) reported 16 minutes ago

  @naomirwolf @Uber Occasionally I have opened up the Waze App and had the volume on low so that the driver knows I'm comparing their route with the route from Waze. I stopped using Uber after the driver started pulling away from the curb before I was fully into the backseat-- and the door was still open. He only stopped when I yelled loudly. I use Lyft instead. All good, no problems.

• 
  Nigel Poncewattle (@poncewattle) reported 20 minutes ago

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

• 
  Bobby Boulders (@ItsBig_Earl) reported 21 minutes ago

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

• 
  Orvill Samanta (@orvilldesign) reported 22 minutes ago

  Why is there no Waze for golf courses. Every weekend someone drives out to a course that has punched greens or patchy fairways and finds out when they get there. That information exists. Other golfers who played there that morning know it. It just goes nowhere. TurfTracker is the app that changes that. Crowdsourced conditions, one tap to report when you arrive, rewards for contributing. Know the condition before you commit to the round. This is the iOS concept I have been working on.

• 
  Jason Wallace (@TragedyCalls) reported 22 minutes ago

  @nursedanakay Surely it cannot be beyond the wit of man to map where they are. Certainly telematics should be telling the car something's not right in the same place every day. I have a similar issue on my route and @waze. 9 speed humps which variously appear and disappear .

• 
  𝘼𝙣𝙘𝙖𝙥 𝘼𝙞𝙧 🛫 (@AncapAir) reported 24 minutes ago

  @ArmitageX @waze I was the same way at first, but the hardware is actually solid. @GrapheneOS is working with Motorola to create a non-Google phone with the same hardware hardening they require, but that's still a ways out.