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:

• 
  fluxity (@tjosephfluxity) reported 5 minutes ago

  @KSTP People will just use Waze and slow down, more tax money wasted. Common nature of people has to be considered for this crap before it's put up. Washington DC had a ton of them and everyone just mapped them - dumb.

• 
  NancyH (@NancyH_60) reported 11 minutes ago

  @gotrice2024 20 minutes is brutal—I’ve been stuck nearly that long on a slow freight crawl with no U-turn option. Best move is to use Maps/Waze for detours on known problem crossings and always treat malfunctioning gates as active: better late than risking it. What’s your usual route?

• 
  Anoop Rao K | ಅನೂಪ್ ರಾವ್ (@anoopraok) reported 13 minutes ago

  This UI bug is causing lots of issues because I can't see the exit number and during driving I have to keep on seeing the map to exactly see the exit on maps and not the exit number on the top. @Waze_UAE @waze #waze

• 
  Drew Hayden Taylor (@TheDHTaylor) reported 13 minutes ago

  We’ve been trying to use WAZE to get home but there’s a problem. It keeps telling us Curve Lake has moved! I know we were once a migratory people but really ….

• 
  Bobby Boulders (@ItsBig_Earl) reported 14 minutes ago

  @SnooCompliments You guys seem to put a lot of faith into John’s Waze app and a correlation of time done by a guy who has been pursuing a 4 year degree for 18+ years…What exactly is the issue here? Trust the data right? Except when it implicates the house defendants….then it’s obviously just wrong.

• 
  Isisí (?) (@luisuxanz) reported 15 minutes ago

  @BowTiedPassport Trusting the Waze ETA is the ultimate error in CDMX

• 
  Lodeci 로데시 🏁 (@Lodeci_) reported 25 minutes ago

  Had Waze for almost 10 years it feels like , I had absolutely no problem deleting that bullshit.

• 
  baseball enjoyer 3000 (@TheNotoriousHRT) reported 26 minutes ago

  also has anyone else been having problems with Google and Waze on iPhone lately?? it feels like nothing loads. genuinely feel conspiratorial. I can have like two or three bars of 5G and it's just slow as ****. I mean NEVER loads.

• 
  blair’s beeper (@blairsbeeper) reported 27 minutes ago

  WHY ******** ARE YOU WORKING WITH ISRAEL YOU ******* SELLOUT FAKE *** AMERICAN COMPANY @waze ******* GET THOSE DEMONS OFF YOUR ******* CONTRACT NOW

• 
  Dave W (@Sir56ALot) reported 27 minutes ago

  @NationalHways @NRManc Then there are the errors; marking overnight closures as 24-hour closures is a particular annoyance. They’re clear to see because Waze routes around them but Google Maps shows green traffic both ways through the “closure”. The data’s useless if it’s not perfect.

• 
  🇩🇲 🍉 She Who Resembles God🪞 (@TiPassie) reported 30 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

• 
  Capxel Security (@capxel_security) reported 30 minutes ago

  Breach notices passed last year's total in the first half of 2026. That is not a louder alarm. It is a new instrument panel. When Waze made every driver a traffic sensor, roads changed. AI is doing the same to attack surfaces. Security teams need telemetry that sees the road, not just the crash.

• 
  Alan (@bitforth) reported 31 minutes ago

  @GergelyOrosz I am not surprised because I happen to have friends there. Google also uses them, Facebook names them differently but it's essentially the same thing. Especially in RL, the FANG documents, and so do most large tech companies. I would even challenge your claim that PRDs decide what should be built. In most companies, the core decision already exists before anyone opens the document either because a big customer problem has escalated, or an executive has set a priority, or sales demand a feature, a competitor has moved, or a small group has already agreed on the direction. A PRD RARELY creates that decision. They're mostly artifacts that large organizations require to make work visible to people who are not in the room where product decisions happen. You worked at Uber. You should know this better than most... the actual decision gets made in a meeting, a Slack thread, or a conversation between a few senior people. THEN the PRD is written just to formalize the decision, gather approvals, assign ownership, and create evidence of cross-functional collaboration. During calibration, that artifact becomes proof that someone “drove alignment” across six teams. The strongest case for a PRD is pretty much to stop people from building 6 different interpretations of the same idea, but then again... Google uses them aggressively and it is almost the perfect counterexample. It launched Allo and Duo while Hangouts already existed. It later killed Allo, split Hangouts into Chat and Meet, and eventually folded Duo into Meet. It ran Inbox beside Gmail for four years, then shut Inbox down and moved parts of it into Gmail. It acquired Waze in 2013, explicitly kept its product team separate, and still develops both Waze and Google Maps as overlapping navigation products more than a decade later. I am 100% SURE all of those teams had detailed PRDs. In fact, a polished PRD can make duplication worse. It gives every team a coherent narrative, supporting metrics, a roadmap, and a professional-looking artifact with which to defend its territory.

• 
  Kimmyb (@Kimmybme) reported 32 minutes ago

  @MAGA4Ever19 @MJTruthUltra @waze Are you going to fix your map?

• 
  AMPed UP (@DoublepPradhan) reported 33 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