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:

• 
  404prophet (@lightscaner) reported 10 minutes ago

  @thsottiaux Reverse engineering the USB protocol between lightburn/ezcad to a 100W fiber laser I have that I've avoided using because the software is so meh. Maybe if I build a programatic interface I'll actually use it. Launch an app I've been working on for months thats like super waze ; connects to radar detectors and shares the pings with other users. Spend a good evening reviewing new tools/skills and workflow stuff.

• 
  Legs (@legsanity) reported 10 minutes ago

  anyone else having trouble with the Waze app? i open it and it freezes

• 
  bipo 🎈 (@bipobuilt) reported 12 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 ****

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

• 
  Drew Hayden Taylor (@TheDHTaylor) reported 16 minutes ago

  We’ve been trying to use WAZE to get home but there’s a problem. It keeps telling us Curve Lake has moved! I know we were once a migratory people but really ….

• 
  J (@Junxid_) reported 16 minutes ago

  Waze needs to fix up

• 
  Lunchlady (@LunchLady1997) reported 19 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.

• 
  Weave (@diaper) reported 20 minutes ago

  @NevrEnoughX @billykyle @grok Which is why I wish Tesla used Waze maps for navigation. If there's an issue, click report button in app and someone local will be fixing it in a day or so. For example, when Virginia opened up 20 miles of new Express lanes on I-66, the day it opened Waze maps were already updated and routing people on it correctly.

• 
  Bobby Boulders (@ItsBig_Earl) reported 20 minutes ago

  @SnooCompliments You guys seem to put a lot of faith into John’s Waze app and a correlation of time done by a guy who has been pursuing a 4 year degree for 18+ years…What exactly is the issue here? Trust the data right? Except when it implicates the house defendants….then it’s obviously just wrong.

• 
  Sunny Spirit ❤ 🌻 (@SunnySpirit1919) reported 22 minutes ago

  I see the problem. You don't understand the data+are unable 2 synthesize info. SUV running clock SYNCED 2 REAL-WORLD TIME. John’s WAZE history CONFIRMS route= 💥WHEN+WHERE they were 💥Corroborated WHAT MAKES IT BULLETPROOF w/other OBJECTIVE DATA=Karen Read Techstream+Infotainment

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

• 
  blair’s beeper (@blairsbeeper) reported 24 minutes ago

  WHY ******** ARE YOU WORKING WITH ISRAEL YOU ******* SELLOUT FAKE *** AMERICAN COMPANY @waze ******* GET THOSE DEMONS OFF YOUR ******* CONTRACT NOW

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

• 
  Ahmedkhan (@Ahmed___khaan) reported 26 minutes ago

  Because your phone is basically a tiny traffic sensor. Google Maps doesn’t “see” traffic, it measures behavior. Thousands of phones on the same road continuously send anonymized GPS location and speed data. The system groups these signals by road segments and compares current speeds with historical patterns. When vehicles suddenly slow down, like from 60 km/h to 10 km/h, it flags congestion and turns the road red in real time. Then comes Waze. After Google acquired it, the real power was in combining data, not merging apps. Waze users actively report accidents, police, closures, and hazards, and that information flows directly into Google Maps. In return, Google’s massive data improves Waze’s routing and traffic predictions. So even if you never open Google Maps, your phone can still be contributing to traffic detection. You’re not just using the map. You are the map.

• 
  Tshepo Chiloane (@mohlakale) reported 26 minutes ago

  @jerry_peep @LimChronicle The problem is not using Waze. The problem is reckless driving