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:

• 
  tog² (@tog128) reported 7 minutes ago

  @leviackermanft It's all experience based. My Apple Maps experience is horrific in the UK. Google Maps imo is functionally superior. Waze is FAR better than both but lately it isn't announcing alerts for camera etc and I have the same problem.

• 
  Mr. Zombie Reagan-We will survive. Am Yisrael Chai (@tattooedsaint1) reported 10 minutes ago

  @jessisajew Yep. I'm a happy Waze customer in the US, and excited to continue to use it in Israel. Now about that Moovit app... it's tied with Pango, and I'm having trouble getting them to change out a card that I used 3 years ago because it now requires Israeli ID to use?

• 
  RonniRN (@RonniRN) reported 10 minutes ago

  @MagaSgt @waze This is main problem...MAGA represents roughly 0.65% to 0.75% of global population. Waze is an international company found in 185 countries. Everytime yah do this cancel bs on a company it doesn't work...cause companies are not local anymore...we live in a global economy. SIGH.

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

• 
  Wayne Kennedy (@lilwaynekennedy) reported 11 minutes ago

  @401_da_sarpanch This is the exact thing I've been saying. These ******* clowns don't speak English, have no idea where they are going and will cross five lanes of traffic last minute to hit an exit because their Waze is slow. I've seen mother ******* backing up on DVP exits. @OPP_HSD

• 
  Rex_Tudor_Coup (@iamgnurr) reported 13 minutes ago

  @Serk_TX @deaflibertarian Fine by me. Waze is slow and irritating. Google never gets me lost. And, as a dude, I'll never pull over and ask somebody. :)

• 
  Sara Higdon (@SaraHigdon) reported 16 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 16 minutes ago

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

• 
  Joshua (@xzinft) reported 16 minutes ago

  @Baloney_and @THPLawrencebur Waze could also identify those flocks and we’d just slow down b4 it

• 
  Wáhálá (@thewahalaboy) reported 17 minutes ago

  Don’t ever use the Waze app in Lagos if you don’t want problems with LASTMA. #noteToSelf

• 
  404prophet (@lightscaner) reported 21 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.

• 
  AMPed UP (@DoublepPradhan) reported 28 minutes ago

  @bauminater I always have WAZE on while my phone is on the charger. and look at it to see where cops . do the same!! I ensure to slow down before about 3/4 miles prior. Problem solved

• 
  Paugus Tadmuck (@PaugusSpdragoo) reported 29 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.

• 
  DeweyCheatemandHowe (@Obiewann) reported 36 minutes ago

  Verizon Cell Services still not working for Google Waze in Central Va. I81

• 
  · (@Thejacobdean) reported 38 minutes ago

  @NotATeslaApp No they should have FSD automatically slow down based off the Waze/apple/google police data though. I have 2 tickets in FSD mad max