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:

• 
  Edgars Zīverts (@edziverts) reported 1 minute ago

  @ChinaEV_Eng_Lif Try coming to Eastern Europe; Tesla cannot fix its maps for 2+ years. Waze really is the gold standard; too bad there is no native app.

• 
  Property and Cars kings (@CarandProperty) reported 2 minutes ago

  @Julius_S_Malema @NgizweMchunnu Working for you is real colonisation. Imagine wasting all the time for your lawyer just for and apology? Chief use your resources very waze. How does and apologise benefit the ground flow of Eff? Yeah @FloydShivambu really was running the retail store for you.

• 
  bappingjump D. Oden❤️💙 (@bappingjump) reported 3 minutes ago

  @Lean78 @waze No me too since an update. Waiting for a fix

• 
  The Future is Autonomous (@SuperMajority18) reported 7 minutes ago

  @beyoncegarden I just dealt with a complete ******* Mass State Trooper working a detail at Logan Airport Departures Terminal E last night around 6 PM. I pulled up to drop off my fiancée, hopped out to grab her luggage, and was back in the car in under 30 seconds. Her phone was still connected, so I quickly switched it to mine to connect my Waze for the drive home. Total time parked curbside in the drop-off zone: less than 60 seconds. I wasn’t blocking anyone. This unhinged prick immediately starts waving me off, then yells “NOW! Get off your PHONE!” while aggressively marching toward my car. I nearly missed my exit home because of his bullshit. For no reason whatsoever, this douchebag escalated a perfectly normal drop-off into a hostile confrontation. This is exactly why law-abiding citizens despise cops and call them pigs. Zero justification, pure power-tripping aggression. Just another completely unnecessary, ****** interaction with police.

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

• 
  Nigel Poncewattle (@poncewattle) reported 11 minutes ago

  @oi8achevy @diaper @TeslaKing420 Also hate to say this, but Tesla does not use Waze nor Google for speed limit data so it won't fix THAT problem.

• 
  Jizas MacStina (@Tshepo_McStina1) reported 13 minutes ago

  @KayMatthews_10 @LimChronicle Problem is some see cops and assume waze will automatically know

• 
  crazy people out there (@ron_doingstuff) reported 13 minutes ago

  @congressdj @Spencer10438140 I was trying to get waze working, so at least it would alert me. I was having issues with waze bluetooth talking over the tesla audio. I could not hear both at the same time. Grok said there was some browser version of tesla waze. Too busy to figure this out so far :)

• 
  David Keyes (@DavidMKeyes) reported 14 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.

• 
  Ben (@ben_toto23) reported 15 minutes ago

  @TheHauskarl I agree 100%. Early 2025 this got very real for me. It emerged that the UK government had secretly served Apple with a Technical Capability Notice under the Investigatory Powers Act, demanding access to end to end encrypted iCloud data. Apple's response? They didn't weaken the system for everyone. Instead they pulled Advanced Data Protection, their best iCloud encryption option, for UK users. What really stuck with me wasn't just the demand. It was the secrecy. These notices come with a legal gag order. Companies aren't allowed to tell anyone they've received one. The only reason any of us know is that the story leaked to the press. Apple itself was never allowed to confirm it. Only Apple was named in the initial reports, with zero confirmation either way about Google or others. By design that silence tells you nothing. You're simply not meant to know this is happening. (see below for link to articles). That's when the alarm bells really rang for me. I've since built my own private setup. A Raspberry Pi handles my encrypted offsite backups. My phone runs GrapheneOS. My ThinkPad runs Debian. This fully replaced Google Drive and iCloud. The same principle applies to software. LibreOffice does everything I used to need Microsoft 365 for, free, private, and with nothing phoning home. For most paid tools solid open source alternatives exist if you look. For cheap offsite backups: Hetzner Storage Boxes, 1 TB for around 3.20 euros per month plus VAT, 5 TB for around 11.40 euros per month. Excellent value. Add Infomaniak (Swiss) as a second target. It sits outside the EU and UK entirely. For phone backups I use Syncthing on GrapheneOS. It syncs documents and photos directly to my Pi over my own private network, no third party accounts involved. The files stay on hardware I control. On the phone I also switched to Organic Maps (ditching Google Maps/Waze). You lose live traffic but I would rather keep my location data to myself. My documents and photos live on my own devices and back up to storage I fully control. Nothing important sits on services I can't inspect. The bigger issue is the devices themselves. Anything that phones home is a hard no for me. Firesticks, voice speakers, smart home gadgets and so on. They are designed to send data back constantly, often without clear visibility. Fitbit stands out because it is owned by Google. Every step, heartbeat and sleep record goes straight to them. Fun fact: Fitbit data has already been used as evidence in court cases. The same privacy logic applies to GrapheneOS on my phone. If a device can't be trusted to stay quiet it gets replaced. With digital ID and age verification rolling out fast, now is a good time to audit what you're storing where, what devices you're bringing into your home, and what data you're feeding into cloud based AI tools. My rule of thumb: Whenever something digital feels too convenient, ask yourself: what is this really going to cost me?

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

• 
  zeerusli (@zeerusli) reported 17 minutes ago

  @waze Wait your quick action to fix this. Most of users experiencing the same. So it should be general issue now. No need to be hassled submiting here and there.

• 
  DeweyCheatemandHowe (@Obiewann) reported 17 minutes ago

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

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

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