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:

• 
  Tracy Martin (@IAmATMFirearms) reported 51 seconds ago

  @CrudeOil4Life @Waze, fix your anti-America mistake.

• 
  Sean Eddy (@seaneddy) reported 3 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.

• 
  Navid Besharati (@NavidBesharati) reported 6 minutes ago

  @Garnet_2203 @googlemaps @waze Google owns Waze you retard. This is exactly the reason why libtards are the problem with Canada 😔

• 
  🇩🇲 🍉 She Who Resembles God🪞 (@TiPassie) reported 9 minutes ago

  If I say I don't use Waze because it's Israeli made then I'm pretentious/too woke/ doing too much. If I say I prefer a different app then it's no problem. I am so tired of the apathy of the world and it being a social sin to give a damn

• 
  Definitely Not Allen Covert (@Covert61) reported 12 minutes ago

  If there is a huge traffic jam and WAZE shows me a different route that can save me time is Waze ignoring my issue and telling me to shut up or is it offering a temporary solution to my immediate problem?

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

• 
  jojo🧷 (@faridssh6r) reported 18 minutes ago

  if it’s not broke don’t fix it fr WAZE IS NOT WORKING ON CARPLAY AND ITS PMMMMOOOOO

• 
  Brady Clark (@Brady12Clark) reported 19 minutes ago

  Thanks to the nationwide T-Mobile outage that just happened, I am now forced to deliver my first child on the side of a highway in Rhode Island. Our Waze app disconnected halfway through the ride to the nearest hospital. Please pray for my wife and I on a safe delivery.

• 
  spencer ¹⁷ 🐈‍⬛ (@svtquest) reported 24 minutes ago

  @sadorbrave @waze she is literally going to crash her car waze please

• 
  waze (@waze) reported 25 minutes ago

  @PURE_IGNORANCE 1/2Hey Jean Paul, I understand you're having routing issues. That can be frustrating. Waze navigation is crowd-sourced in real time, so reports depend on input from other drivers. If you see a report that isn't accurate, tap Not there to

• 
  Paugus Tadmuck (@PaugusSpdragoo) reported 30 minutes ago

  @MJBiercuk @qctrlHQ It depends on having an up-to-date map file in the system. While it may sound like how GPS works...it doesn't. With GPS, the receiver measures how long it takes to get the radio signal from the GPS constellation (since the speed of light in an atmosphere is pretty fixed), so it can calculate its position. Kind of like counting the time in seconds between seeing a lightning flash & hearing the thunder, then dividing by 6 to figure out how many miles away the lightning hit. At best, a gravitic-based sensor will tell you how far you might be from the closest portion of the Earth...but I suspect the math involved & the actual measurement & detection of the gravity field is much more complex than that. And since apparently they're saying "gravity fluxuates quite a bit as you travel through the ocean", that's why you need the updated map so that you can know where you're at. I also strongly suspect, now that I've had a few more days to think about it, that it also requires some sort of **initial** position fix to work. Because I would also suspect that, since a lot of the Earth's crust is made of similar materials, and there are sections of the ocean with similar depths & similar crust/coastal configurations, that the system can't just say "Given a gravitic flux of 0.xabcz, you are at latitude XX.YY.ZZ and longitude TT.UU.VV.", because that particular flux reading is probably **not** unique. Which makes this more akin to INS (which is ***highly*** dependent on knowing exactly where you started from to determine your current position)...unlike GPS, which (unless you're using Google Maps, Apple Maps, Waze, or some other routing app) doesn't give AF where you started from, because it doesn't need that to know where you're currently at.

• 
  Robert Scoble (@Scobleizer) reported 33 minutes ago

  @Financewisdom01 The guy who started Waze told me everyone is a bag of human patterns. The algorithms can do things we can’t. Like what if all the teslas in a parking lot started working together to see the grandmas passing behind in wheelchairs that are hard to see in mirrors.

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

• 
  Guy Lessard (@Guy_Lessard) reported 36 minutes ago

  @therealDeFlock Has anyone made an app that tracks them or maybe puts them into the Waze app since police sightings, accidents, and even pot holes are crowd sourced. Like reporting it as a broken traffic light. Make that a code for a flock camera on Waze.

• 
  TimmerMcGraw, CFI 🇺🇸🔎 (@TimmerMcGraw) reported 39 minutes ago

  @TheGreenOldDill My latest issue with Waze is it insisting I go down a closed road, and continuing to reroute me back to the closed road.