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:

• 
  Sara Higdon (@SaraHigdon) reported 3 minutes ago

  @wholemars @DevinOlsenn It could be, if able to change the speed limit control on the screen. This could actually fix two major issues, current speed limits being wrong as the entire neuro-net could be updated in real time, like in Waze, and the system can properly adjust to user preferences as it would know what said preferences are

• 
  Jarek Hunt (@Gun2MoufCPR) reported 6 minutes ago

  @HenMazzig Who gives a **** about Waze? Figure out your under 30 in USA and their lack of support for Israel problem….

• 
  Kailash Mhetre (@KailashMhetre) reported 7 minutes ago

  @republic I think we are unnecessarily dragging the issue ,If only mumbai police wld hve properly ****** Waze he wld hve omitted the truth long back.

• 
  Dreadfully Despized (@DreadedT) reported 8 minutes ago

  @NotATeslaApp No, I don't see the benefit of using waze over what already exists. Tesla's already communicate to the "network" and report road issues/etc. If the use case is "reporting where police are", stop being illegal?

• 
  Anoop Rao K | ಅನೂಪ್ ರಾವ್ (@anoopraok) reported 11 minutes ago

  This 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

• 
  Lightheart (@IciclePrism) reported 11 minutes ago

  We’re not going to help these people by bringing in a few hundred thousand of them into our country. There is probably close to a billion of these people. Instead, we need to send people over there to train and educate as many of them as we can in Waze. They could work to fix this problem. They are extremely primitive people. They are inappropriate to be selected to live here in America. ________

• 
  𝘼𝙣𝙘𝙖𝙥 𝘼𝙞𝙧 🛫 (@AncapAir) reported 12 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.

• 
  Maximilian Kirk (@realmaxkirk) reported 13 minutes ago

  @scumbagdotdll @Molaau6 It's worth using today. Some QoL features were added, like cop call outs aren't possible if the reporting user is stationary; requires 2-3 repeats to validate; etc. Honestly, it seems like cops prefer Waze these days because people slow tf down and it's less tickets that they have to write. Less interaction with the public = less opportunity for incident.

• 
  AmericanPowerUpgrade (@UpgradeAmerican) reported 15 minutes ago

  @SDembraski Would love if it pulled into MY driveway, not my neighbor's. Parking is a real issue — we need handicap placard support for spot selection. Navigation also needs work: FSD constantly takes scenic routes out of parking lots and even my cul-de-sac (starts a right turn, then yanks left to loop around the block). Surprisingly, Google Maps and Waze have the same problem.

• 
  Justice (@VerityI952) reported 16 minutes ago

  @Suzybeau1 @WBergeson11310 @BostonDefender I'm saying you can't compare Life360 with Waze because Waze has better service, just like Verizon and AT&T have better service than U.S. Cellular and don't have the dropped-call problems and don't have the infrastructure the major networks have.

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

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

• 
  nycwest45th (@westforties) reported 20 minutes ago

  @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?!

• 
  TruthOverBS (@TeamFUKR) reported 20 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."

• 
  NancyH (@NancyH_60) reported 22 minutes ago

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