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:

• 
  Orvill Samanta (@orvilldesign) reported 1 minute ago

  Why is there no Waze for golf courses. Every weekend someone drives out to a course that has punched greens or patchy fairways and finds out when they get there. That information exists. Other golfers who played there that morning know it. It just goes nowhere. TurfTracker is the app that changes that. Crowdsourced conditions, one tap to report when you arrive, rewards for contributing. Know the condition before you commit to the round. This is the iOS concept I have been working on.

• 
  Jason Wallace (@TragedyCalls) reported 1 minute ago

  @nursedanakay Surely it cannot be beyond the wit of man to map where they are. Certainly telematics should be telling the car something's not right in the same place every day. I have a similar issue on my route and @waze. 9 speed humps which variously appear and disappear .

• 
  Peter Miles (@ginjajedi) reported 3 minutes ago

  @DanielCars05 Anybody had any issues getting sound from waze when using one of these?

• 
  Ahmedkhan (@Ahmed___khaan) reported 3 minutes ago

  Because your phone is basically a tiny traffic sensor. Google Maps doesn’t “see” traffic, it measures behavior. Thousands of phones on the same road continuously send anonymized GPS location and speed data. The system groups these signals by road segments and compares current speeds with historical patterns. When vehicles suddenly slow down, like from 60 km/h to 10 km/h, it flags congestion and turns the road red in real time. Then comes Waze. After Google acquired it, the real power was in combining data, not merging apps. Waze users actively report accidents, police, closures, and hazards, and that information flows directly into Google Maps. In return, Google’s massive data improves Waze’s routing and traffic predictions. So even if you never open Google Maps, your phone can still be contributing to traffic detection. You’re not just using the map. You are the map.

• 
  Nic Cruz Patane (@niccruzpatane) reported 10 minutes ago

  The biggest problem with CarPlay is enabling it to synchronize with Tesla FSD. If you input a destination in FSD using Tesla’s native navigation system, it isn’t going to match what you see in Apple Maps, Waze, or Google Maps. Integration is a lot more complicated than it seems.

• 
  zeerusli (@zeerusli) reported 12 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.

• 
  KRISTIN KAY (@benchslappedtv) reported 15 minutes ago

  @Dan_Donovan_17 @HoldenMaur50368 I never said Waze had its own GPS satellites. Everyone knows Waze uses the iPhone’s GPS/location services. That was never the issue. What Green was talking about was the timestamps and how different phone artifacts and app data lined up against each other. That is a normal digital forensics issue. Different apps and datasets can have different timing offsets and logging behaviors. That is what he was referring to!

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

• 
  Barry Zahurance (@barryzed) reported 17 minutes ago

  @EliAfriatISR Waze says “turn on Main Street” but it should be “turn onto Main Street”. There’s no way to correct it, the grammatical error is baked in. Other than that it’s decent and I use it.

• 
  Njoroge (@Joe_AlexN) reported 19 minutes ago

  @NdemoKelvin I agree, the problem is that those clowns are always on the move. It's like they're also using Waze bana. You report them, they move afew kilometers ahead.

• 
  benferrum - e/jounce (@BenFerrum) reported 29 minutes ago

  Hey @Tesla_AI FSD feedback from down Under: * The Tesla navigation in Australia is bad, it is biased towards taking right hand turns which are the most dangerous/slow when driving on the left, > pls benchmark your navigation against Waze * FSD drives decently my wife felt safe, but we need Mad Max mode because my grandma has more tempo, I did not used FSD that much because it takes ages to speed up * It's too timid to get into a lane/roundabout/cross an intersection * It picked the wrong lane 2x in a 4 hour drive ( same pattern, moving to the left lane to move right > hook turn overtraining much? * Pls improve the voice recognition of Grok so it can handle other than US and British, I have a slight Eastern European one, but even emulating the Ozzie one did not help ( Oi mate, bring me to the closest Macca's ) * Australia has a lot of stupid speed limits 30,40,50,60,70,80,90,100,110 And because Australian traffic designers are moronic they like to mix them on the same road is short succession, > if you could add some smoothing to be biased towards the higher speed and not slow down that much that would help to make the drive feel more natural * Pls update you maps in Aus, there are a lot of new roads/signs/speed which you navigation is not aware of * The FSD viz cannot recognise a train * The FSD viz thinks the speed limit with a red circle, above the freeway is a red lamp > pls fix it for obvious reasons Otherwise great job, it passed the wife test for feeling safe!

• 
  Alex 💪 (@awpthorp) reported 30 minutes ago

  @dilantha_de @AlsieLC His Waze app was not working, his other phone didn't work either. In terms of not being genuine, Careem gave me a full refund so not sure what is angle might have been. Likely new as not knowing Al Quoz to JVC is a rookie error

• 
  Twigs (@TwigsJohnston) reported 30 minutes ago

  @CuriosityonX Waze stopped working and this is where I ended up.

• 
  Neel (@neelshah545) reported 33 minutes ago

  @MapmyIndia @narendramodi Make ui smooth no lag and make app ui simple not overlays . Try to copy from apple maps or waze or if copyright issue arise try to use ui of Chinese maps

• 
  Matt Osborn (@themattosborn) reported 36 minutes ago

  @FSDyinzer @TheAccuracyPoli @Teslarati 💯 That is exactly what I was talking about. It is quite frustrating. There are plenty of navigation systems out there that they could model from. Why is it still an issue? And their map data is pretty old as well. A peer managed mapping system similar to Waze would be awesome.