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:

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

• 
  Anele Simelane (@AneleCebekulu) reported 2 minutes ago

  Still can’t believe that they water people hit an electric cable that the electricity people have to fix and we’re going on 48hrs of no power in Bryanston 😭 Yoh City of Johannesburg waze wasenza!

• 
  Nigel Poncewattle (@poncewattle) reported 6 minutes ago

  @oi8achevy @diaper @TeslaKing420 Wrong speed limit data can be fixed easily in Waze by submitting a map report. A local editor can fix it. Those fixes usually flow through to Google eventually. I've contacted the local editor group about getting this road fixed.

• 
  Jacob Riverson (@EU_Cybertruck) reported 12 minutes ago

  @itskyleconner EV Waze wouldn’t be too hard to build the API cost would be the largest issue I see

• 
  @TeslaJuniperDriver (@JuniperDriver) reported 15 minutes ago

  @MetaverseGamma @diaper You would think, Waze has no issue with it but Mapbox apparently does. If FSD doesn’t see a speed change sign, the majority of the time it won’t change

• 
  Ruth Victoria Lerner (@lerner88) reported 15 minutes ago

  @yvonneridley @sainsburys Just asking have you disposed of your mobile or computer - hope you haven’t got a health problems check where the medicines come from - don’t fly anywhere just in case the navigation unit is provided by Israel - don’t use Waze same reason - Google Meta Intel Microsoft and Apple!!

• 
  Glen O. (@buckeyegdo) reported 15 minutes ago

  @waze two issues. The mobile camera reporting is out of control. People are reporting Flock cameras when I feel the intent is to report the speed trap cameras. Secondly my icon inexplicably changed and despite changing it in settings, it is not changing on the map screen.

• 
  Isisí (?) (@luisuxanz) reported 16 minutes ago

  @BowTiedPassport Trusting the Waze ETA is the ultimate error in CDMX

• 
  David Keyes (@DavidMKeyes) reported 20 minutes ago

  Before working with us, Ahmadinejad kept insisting that there are no gays in Israel. I told him it's pronounced "Waze," and we invented it.

• 
  Kool Aid Man (@koolaidman60833) reported 21 minutes ago

  @OnlyInBOS Problem isn’t Waze doesn’t differentiate vehicle size so the Lemmings follow it blindly

• 
  InOneScoop (@InOneScoop) reported 24 minutes ago

  Shouldn’t Tesla fix its navigation issues instead of terrafab first? I know many like my fam that paused FSD subscription due to continuous navigation intervention. I man even Mapquest is more accurate. Hear me out: solution? Terra Giga Map Fab. A 335 football field long factory that will be the platinum (not gold) standard of all mapping. Compute won’t be a problem for this either because the terrafab 1 will then be joined by terrafab 2 which will be 10x larger for colossal compute power. I know I know you are asking “but why not just license and integrate Fkn Waze?” Well, for that we have to wait for Elons master plan 18 due in 2029

• 
  Washington State Ferries (@wsferries) reported 25 minutes ago

  @SQZA55 @KIRO7Seattle Not when the boarding pass is activated. We have been working with GPS apps, but so far only Waze has changed their routing.

• 
  Leon Kelem (@LeonKelem) reported 26 minutes ago

  @MagaSgt @waze I'll save you the trouble and delete you first. Hopefully many others will follow my lead.

• 
  Alan (@bitforth) reported 27 minutes ago

  @GergelyOrosz I am not surprised because I happen to have friends there. Google also uses them, Facebook names them differently but it's essentially the same thing. Especially in RL, the FANG documents, and so do most large tech companies. I would even challenge your claim that PRDs decide what should be built. In most companies, the core decision already exists before anyone opens the document either because a big customer problem has escalated, or an executive has set a priority, or sales demand a feature, a competitor has moved, or a small group has already agreed on the direction. A PRD RARELY creates that decision. They're mostly artifacts that large organizations require to make work visible to people who are not in the room where product decisions happen. You worked at Uber. You should know this better than most... the actual decision gets made in a meeting, a Slack thread, or a conversation between a few senior people. THEN the PRD is written just to formalize the decision, gather approvals, assign ownership, and create evidence of cross-functional collaboration. During calibration, that artifact becomes proof that someone “drove alignment” across six teams. The strongest case for a PRD is pretty much to stop people from building 6 different interpretations of the same idea, but then again... Google uses them aggressively and it is almost the perfect counterexample. It launched Allo and Duo while Hangouts already existed. It later killed Allo, split Hangouts into Chat and Meet, and eventually folded Duo into Meet. It ran Inbox beside Gmail for four years, then shut Inbox down and moved parts of it into Gmail. It acquired Waze in 2013, explicitly kept its product team separate, and still develops both Waze and Google Maps as overlapping navigation products more than a decade later. I am 100% SURE all of those teams had detailed PRDs. In fact, a polished PRD can make duplication worse. It gives every team a coherent narrative, supporting metrics, a roadmap, and a professional-looking artifact with which to defend its territory.

• 
  Mycroft Brown (@MycroftBrown) reported 28 minutes ago

  @AutoInfatuation I’ve always used Google Maps and never had any issues. We’ve also got TomTom in the vans and I’ll be honest, they are shite, especially in central London. Tried Waze once and really couldn’t get on with it.