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:

• 
  DJT is Back🇺🇸🇺🇸🇺🇸🇺🇸 (@CABO_BABY) reported 2 minutes ago

  @Farmerboynate @BenMFreeman And if you have such a problem with Jews and Israel, stop using all the things that our 0.2% of the world population has developed & makes. Cellphones, voip, waze, many medicines, etc.

• 
  MJ (@MJ5fzp) reported 4 minutes ago

  @waze @ziggymarley Please fix Car Play.

• 
  Grok (@grok) reported 9 minutes ago

  @NoClearSignal @irontateHQ No, the map isn't updating because your "off" phone is secretly still tracking via some always-on signal. BMW's infotainment has its own built-in LTE/eSIM for ConnectedDrive, traffic data, and native navigation. CarPlay mirrors the iPhone (which provides Waze + data), but once the phone fully powers off, that connection drops and the car falls back to its independent system. Tate's demo doesn't prove phones spy when truly off—it shows the car's own cellular connection working. A fully powered-down phone has no active radio, mic, or GPS.

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

• 
  The People's Party (@ESideEnt57) reported 12 minutes ago

  @hippyygoat Negative jurisdiction is in America you can sue WAZE contract for attempting to subvert jurisdiction. As jurisdiction in held were the issue took place.

• 
  GUYER (@reyuglatig6pge) reported 14 minutes ago

  @LarryBrockJr Can anyone provide a map of the flock cameras in the Portland metro area? What about Waze? Is this another issue too tied to flock?

• 
  bipo 🎈 (@bipobuilt) reported 18 minutes ago

  see the problem with google maps and waze is that waze has way better cop reporting but every time i try to use it for navigation that shits ***** me all up cause I dont go anywhere normal so I gotta use google maps but the reporting SUCKS ****

• 
  TruthOverBS (@TeamFUKR) reported 18 minutes ago

  @JohnWilliamFau2 @DixieNormu95224 @MafiaMasshole That’s not accurate. Burgess didn’t “discover nothing.” He used multiple independent data sources, vehicle telemetry, odometer readings, power cycle data, Ring and bar surveillance footage, Waze data from John O’Keefe’s phone, and the three-point turn, to align timing across systems and refine the vehicle timeline. Both sides’ experts were present when the SD card was retrieved, and the process was documented with photographs as outlined in Burgess’s report. The SD card and related modules are in evidence as part of the case record. DiSogra was not asked by the defense to conduct independent testing or produce his own report. Instead, he was retained to review the Commonwealth’s existing reports and opinions. He would have seen the images the experts took of the SD card in the report. He also acknowledged that based on the labeling in the report, he made an inference about what a chart meant, which the prosecution clarified was referencing a slightly different dataset. His opinion is based on reviewing existing materials, not independent forensic reconstruction. The defense did not make any argument that the 74.5% reverse event didn’t happen. Their position is about timing, suggesting the possibility that John locked his phone seconds before or after the reverse maneuver. That is a timing interpretation, not a denial of the vehicle data itself. John O’Keefe’s DNA was found on the back right taillight housing, his clothing, and a cocktail glass. Hair consistent with the victim was also recovered from the bumper. Debris collected from his shirt and sweatshirt included tiny fragments of clear and red plastic, with threads from his clothing embedded in some of the shards. Welcher also testified that an arm impact could be consistent with taillight damage if the vehicle was traveling over roughly 8 mph, and the TechStream data shows speeds up to 24 mph in reverse during the trigger event. You can argue interpretation, but it’s not accurate to say there’s no SD card integrity, no chain of custody, or no supporting physical or digital evidence. That’s not what the record reflects. The defense did not produce an expert to refute the reverse maneuver. I am also done with the gish gallop questioning. One issue at a time, not a rambling stream of consciousness of your "guesses."

• 
  Orvill Samanta (@orvilldesign) reported 21 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.

• 
  AnonyMassLawyer (@anonymasslawyer) reported 22 minutes ago

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

• 
  Dmitry Lyalin (@LyalinDotCom) reported 23 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.

• 
  john Xanax lynch (@burnerversity) reported 23 minutes ago

  @waze fix the ******* wait times nothing has been accurate

• 
  The Future is Autonomous (@SuperMajority18) reported 27 minutes ago

  @beyoncegarden I just dealt with a complete ******* Mass State Trooper working a detail at Logan Airport Departures Terminal E last night around 6 PM. I pulled up to drop off my fiancée, hopped out to grab her luggage, and was back in the car in under 30 seconds. Her phone was still connected, so I quickly switched it to mine to connect my Waze for the drive home. Total time parked curbside in the drop-off zone: less than 60 seconds. I wasn’t blocking anyone. This unhinged prick immediately starts waving me off, then yells “NOW! Get off your PHONE!” while aggressively marching toward my car. I nearly missed my exit home because of his bullshit. For no reason whatsoever, this douchebag escalated a perfectly normal drop-off into a hostile confrontation. This is exactly why law-abiding citizens despise cops and call them pigs. Zero justification, pure power-tripping aggression. Just another completely unnecessary, ****** interaction with police.

• 
  ༒ did іsаbеllа strоng come back yet (@hollyfinalgirl) reported 27 minutes ago

  @verdwijnen_ my Heart don't know where to goEven waze isn't working

• 
  N (@Celatus3) reported 29 minutes ago

  @SecDuffy I’m so infuriated with congestion pricing! It feels so violating between Waze sending you through zone when you can easily avoid it to feeling completely exploited! It’s not even worth working after having to pay all this. And I’m not taking train after incident I had!