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:

• 
  DJ (@congressdj) reported 3 minutes ago

  @SurScribbles It has problems integrating with many cars (believe, I feel like I always seem to rent them in my travels), I don’t think adding more stuff to the Tesla UI is the answer. Plus, my phone is always with me. I have access to all of the stuff CarPlay would carry over. I can stream music directly from my phone, or use Waze (which I do). At the end of the day, CarPlay is meant to bridge the car to its passenger. But with autonomy, none of that is necessary. Ultimately, you’ll be able to use your phone or laptop or anything else in the car. That’s why I think CarPlay is a step backwards. Not forward.

• 
  Sean Eddy (@seaneddy) reported 7 minutes ago

  I've been known to tag a bunch of police cars on Waze throughout my shift so people slow down and I don't have to work accidents.

• 
  Bryce Tackett (@BryceTackett4) reported 8 minutes ago

  @TinkerTYJ @OmariYeager @waze Drove about 500 miles today, app is not working correctly didn’t get a single update of anything

• 
  Dmitry Lyalin (@LyalinDotCom) reported 11 minutes ago

  Just sent a detailed bug report to a director in Waze on a very odd map issue here in Florida. He was extremely excited to dive into this with me. People like this make all the difference in a big company.

• 
  Randall (@Randall145695) reported 12 minutes ago

  @Asor1113 @DoctorTurtleboy @ALL_WEDO_ISWORK Ok, so now it happened outside before Karen even got back to Meadows? What a fascinating goal post shift. The problem with that is the dog would've had to attack and incapacitate him within about 20 seconds. Here's why: The high accuracy Waze data shows the SUV coming to its first and only complete stop in front of the house by the flagpole at 12:24:38 a.m. John's phone then recorded no movement for about 7 minutes as he sat in the car with Karen. At 12:31:56 a.m., a brief 20-second step event began as he exited the car. And at 12:32:16 a.m., his phone stopped moving until 6:04 when the 3 women found him and called 911.

• 
  Kimmyb (@Kimmybme) reported 15 minutes ago

  @MAGA4Ever19 @MJTruthUltra @waze Are you going to fix your map?

• 
  אינספקטור קלוזו (@55Yosi555) reported 17 minutes ago

  @AbdulElSayed You won't be able to use Israeli technology. You'll have to buy it at a price 100 times higher than the "artificial intelligence" or cyber-aid. Sherry Watergen Drips ReWalk Copaxone Pill Cam Mobileye Waze ICQ USB Disk-on-Key If you have any problems, contact Muhammad to help you.

• 
  Bobby Boulders (@ItsBig_Earl) reported 19 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.

• 
  Lauran™ (@lauranruddy) reported 20 minutes ago

  @NYSDOTHV Any update on when this will reopen? Also, are you going to fix the signs stating that it's closed? And maybe alert @waze that it's still closed? They routed me there the other day and wah wah, still closed. Thanks.

• 
  william acevedo (@william74783332) reported 22 minutes ago

  The old Waze fail because there’s no restrictions on the billions of dollars if you have a restriction point it at this money will be used for homelessness. That’s a restriction no restriction they do whatever they want with it. That’s the problem. Federal funding a restriction

• 
  Bob Nordberg Bird Man Bob (@birdmanbob4) reported 23 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.

• 
  Texas Oil Man 🛢️ (@KentGra88631041) reported 23 minutes ago

  @JimHendley4NC Just purchased a new vehicle and it most certainly has the option to load and run “CarPlay” both wired and wirelessly. I use Waze via CarPlay without issue. I listen to X spaces wirelessly without issue. This thing even has a wireless charger, though it’s difficult to get alignment with a Gorilla Case on the IPhone!

• 
  Ihtesham Ali (@ihtesham2005) reported 26 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.

• 
  AMPed UP (@DoublepPradhan) reported 26 minutes ago

  @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

• 
  Lunchlady (@LunchLady1997) reported 28 minutes ago

  @GretchenVoss64 Laposata looked at no evidence. Scordi Belo said it was both likely and unlikely that he was hit. Also couldn’t say for certain as positioning not known. AARCa testing did not even use the weight and size of Officer O’Keefe and frankly a little bit shady… all those deleted signal messages and “ billing “questions. . They did state though that Karen backing into John’s traverse did not cause that damage. You all love to parrot “ he was not hit by a car”. He easily could have been side swiped and that is not impossible. Google accidents by side swipe. I believe in the timeline, tech stream data, Officer O’Keefe phone data, including Waze. Most importantly, per MS Read herself… on video and in written words.. her tailight was broken at 5:08 am. Before CPD ever got the call and beofre MSSP got the call. Voss got it right.