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:

• 
  Skylar Darkfox (@SkylarDarkfox) reported 1 minute ago

  @MatthewCappucci We have navigation apps, and we have weather apps. Why not bring them together? Issue an alert directly through Google Maps or whatever other app if there's some severe or other inclement weather situation ahead. Waze does this to a certain extent with fog and flooding...

• 
  Elkad (@Erezeneb) reported 2 minutes ago

  @JSX423 It should be using a tele lens and reports from apps like Waze to slow down when it sees a revenue cutter.

• 
  Grok (@grok) reported 3 minutes ago

  @VarunVa93348649 @googlemaps I see the glitch in your video—Google Maps can occasionally give inaccurate directions due to outdated data, GPS issues, or road changes. Report it in the app to help them update. For alternatives, try Mappls (strong in India for local accuracy), Waze for real-time traffic, or Apple Maps. What location was this?

• 
  Sophie Cahill (@sophiecahill) reported 7 minutes ago

  @KlaxonDelight @waze Hey I know this is an old post but did you ever get this sorted? Having the exact same issue

• 
  Weave (@diaper) reported 8 minutes ago

  @NotATeslaApp The map data in my area is so bad. What's frustrating is, it *used* to read the signs and no problem. But now I see the sign rendered on the vis OK but it still won't use it. Wish there was a way to report bad data, like you can with Waze.

• 
  Mr Dee 𝕏 (@CCTV_etc) reported 8 minutes ago

  @Uber_Support @Uber A problem with the driver choosing to not follow the uber app and use Waze instead….. ended up in me paying more money. Please advise

• 
  Meadow Ellis (@notameadow) reported 12 minutes ago

  And another thing, since I am ranting, and with regards to the Waze tweet. When I started cooking semi-professionally (three years ago), the idea of a homemade pasta sounded exciting. And it was. I almost bought a machine for all kinds of Italian oddities. I made it a few times. Very good. Completely pointless. When it comes to pasta, there are a few Italian brands that are *good*. They have been around and, yes, their pasta is not as good as homemade. Who cares. I may spend hours making, drying, cooking, and end up with a product that is maginally better than a good-branded one. If at all. And I would have wasted this time on making things that actually matter. Even a simple cacio e pepe is a skill that cannot be replaced with a store-bought jar. I can make pasta. All kinds of shapes. No one cares. So I focused on making better cacio e pepe. That is coding, and that is also my speciality: hardware security. I excel at this, but so does everyone else at my previous level. No one cares. Anyone can "dump the firmware". No secret with FTDI, even Saleale or derivates. Seven million blog posts about it. "Find three pads, get root." And there comes AI, which does all that anyway. I had to become better, so I did. I use AI for boring tasks because I cannot be bothered but also to know where I excel, where AI cannot go. I know why, I know how, I know how to direct my mechanical minion. And I will use it as my brain. And that is also coding. For my second job I need to make some hardware interface between X and Y. I used CharGPT to discuss needs, platforms, design considerations. I will use it to flesh out Alpha. Then I will ask it to make a prompt to Claude Code, and the latter will just do it, deal with ***, toolchains, all that. It will work. You know C and others and can write it efficiently? I am glad. I know C and others to fix code AI throws, and direct it. And I will have it ready in a fraction of a time. I can brag that I know .asm for several uCs, startink from 68k, 8051s, up to modern era. So what. No one cares. No one benefits. No one gets paid. I am not bragging about my skills; I am highlighting the issue with "AI will take my job" that I have realised seeing the Waze tweet. AI has already taken your job. I have no idea how to write .py, mostly because I am lazy. Now I do not have to. You do? Better that Claude? Maybe. I can make a better pasta than one can buy in-store. But I will make a better dinner.

• 
  SMSkulls (She/Her) (@SKolls) reported 15 minutes ago

  @mrmikeMTL Depends. If I’m not the fastest, no. If they’ve already caught someone - no (but I move over, if possible). I use waze - and do slow down for reported police.

• 
  Jordan Regan (@J_bean4) reported 16 minutes ago

  @SawyerMerritt @DirtyTesLa Agreed even without FSD this seems to be a Tesla Nav issue, constantly run into it not knowing closed roads though they’ve been closed for days for construction. Should switch to Waze as an app and not, is it google they license?

• 
  Bee (@Ayebeeeyo) reported 20 minutes ago

  Hey @waze can you fix the bug where the big red blob is going across Apple car play screens? It’s extremely distracting 🙃

• 
  JazzBeaton🇬🇾🇹🇹🇬🇧 (@JazzBeaton) reported 22 minutes ago

  @waze has been tweaking recently. Y’all done sent me everywhere and around the block but my destination. I love y’all app features but please fix the bugs. Y’all gonna make me understand why I couldn’t just use @googlemaps

• 
  Roshan - GoSats.io (@roshanaslam21) reported 24 minutes ago

  If you are having trouble navigating with Google Maps / Waze in the Middle East due to GPS jamming, try Apple Maps. Somehow that’s working.

• 
  Matthew Stevenson (@ENTP_Innovator) reported 24 minutes ago

  @bcasale @itskyleconner Can you not report the error in Apple maps? I do it in Waze and Google Maps.

• 
  Matty (@mattboy1i) reported 27 minutes ago

  @joshwoodward Gemini needs work in android auto with Waze it's broken DM for information I can't DM you.

• 
  Rachel (@DataDecoder11) reported 30 minutes ago

  @commcenterpod @fourensicroom @TuesdayGazette To start, Waze shows a 3-minute-1-second artifact. The prosecution dismissed it, but when you apply that offset to John’s Apple Health data, it lines up perfectly with his steps. It also lines up with Ryan Nagel’s testimony that he arrived right after Karen, and with Ryan’s text to his sister at 12:23. That’s three independent data points placing John there before 12:24. John arrives at the house at 12:21:05 Where he goes after that is speculation, because unfortunately no real investigation was done. My theory is that he walked up to the house and a fight broke out. Brian Albert has been in many fights, but this time it went too far. John fell backward, hit his head, and they knew he couldn’t be saved, consistent with what the medical doctors testified to. After arriving, John’s last recorded movements are at 12:24:22. What’s notable is that immediately after that, all of Jen’s devices go completely dark, phone, watch, heart rate, everything, starting at 12:25:16 for over ten minutes. That wouldn’t be remarkable on its own, except she claims she was repeatedly getting up, looking out the door, texting John, and sitting back down more than five times during that period. At that point, my theory is that they pivoted to a plan where John never entered the house, possibly blaming a plow, a slip, or something else. That plan only fell apart when Karen went looking for him. The phone data is critical here. From 1:36 to 6:04, the battery temperature drops only from 50°F to 43°F over more than four hours, an extremely slow cooling rate of 0.026°F/min. That tells us the phone was in an environment with an effective ambient temperature around 43°F, which is not outside in the snow. When the phone begins moving again in the morning, the temperature drops at a much faster rate (0.75°F/min) consistent with actual outdoor exposure. That cooling rate is dramatically faster than the rate overnight, when the phone was supposedly lying on frozen ground. The same frozen ground the prosecution claims was hard enough to fracture John’s skull.