Waze status: app issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of Waze reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by Waze users through our website.

• Glitches (48%)
• Online Features (23%)
• App Crashing (21%)
• Sign in (8%)

Live Outage Map

The most recent Waze outage reports came from the following cities:

City	Problem Type	Report Time
La Chapelle-Janson	Glitches	2 days ago
Châteauroux	Glitches	3 days ago
Algiers	Glitches	4 days ago
Les Mureaux	Glitches	8 days ago
‘Ewa Beach	App Crashing	9 days ago
Paris	Glitches	10 days ago

Full 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:

• 
  Johanna (@JohannaMordecai) reported 2 minutes ago

  @Proctor4Gov @TeamFUKR Car on at 00.12.36 1162.1 at 10mins 57, that’s at 00.23.33 3 problems Whiffin says turn complete at 00.23.58 Burgess says 00.23.58 was before 3pt And they used the Waze clock which isn’t a clock but a counter, which is unreliable per Whiffin, & is ahead by 3mins 1sec

• 
  Orvill Samanta (@orvilldesign) reported 3 minutes 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.

• 
  Grok (@grok) reported 3 minutes ago

  @Ashh_404 @tanujDE3180 Google Maps pulls real-time traffic data from millions of smartphones (mostly Androids with location on, plus Waze which Google owns). Phones anonymously send speed and position updates. If a bunch slow down 10km ahead, the system spots the pattern and colors the road red/yellow on your map. No cameras needed—just crowd-sourced data from drivers already there. Historical patterns help predict too.

• 
  Adam Elkassas (@adampredev) reported 4 minutes ago

  Waze for airports could be cool if it doesn’t exist already. User reported tsa line backups, gate changes etc, baggage claim issues

• 
  Ahmedkhan (@Ahmed___khaan) reported 5 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.

• 
  Mark (@1zSolace) reported 6 minutes ago

  @waze why does every intersection I pass, Waze thinks I am turning at? Every time the map turns thinking I turned when I never even touched the wheel. Can you fix that?

• 
  The Bass Hog (Jonathan Marlow) (@THEBASSHOG) reported 7 minutes ago

  @saltedfishdivin @BarrettYouTube Because you use the word, private prison, you have to understand that those are not government run operations. So it as a private business contracted to house criminals and it is trying to come up with Waze to make it profitable, rather than a complete business loss. One way is to get government subsidies, the other way is to allow them to employ their prisoners at a very low salary. A lot of the jails are starting to require that prisoners pay three dollars a day for their room, board and healthcare. If the prisoner is not already wealthy enough to pay that out of their own pocket, then the only option they really have is working. The other legal issue is the “except clause” of the 13th amendment, which says that slavery is abolished except as punishment for crime. The thing with Chinese slave labor is that they are turning people into criminals simply because of their religious beliefs and ethnicity, not because they committed a terrible crime.

• 
  Bonf1re¹ (@bon_macharia) reported 7 minutes ago

  @Kimuzi_ @xysist @indiiazi Hadi huku nowadays ata google imenishida kutumia it's too slow and very inaccurate compared to waze

• 
  LeBBC (@Big_Black_Coq) reported 9 minutes ago

  They simply slow down when police are spotted or WAZE warns them, then they speed right back up.

• 
  Ben (@ben_toto23) reported 18 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?

• 
  Neel (@neelshah545) reported 23 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

• 
  coco the pailot (@pailot_the_coco) reported 24 minutes ago

  @waze if you do not fix apple car … Hello @TomTom

• 
  Tony (@TonyB_1997) reported 24 minutes ago

  @bigdavetalks @prestonjbyrne Quite right. It’s illegal to break the speed limit in a car, and the fastest you can go on any road is 70MPH. Yet we can still buy cars that can reach 200MPH or more. If you get caught speeding, you will receive a fine. A minor issue, normally. But if you breaking the speed limit is an aggravating factor in a far more serious incident, such as a fatal accident, then the implications will be far more severe. So, yeah, you could carry on using a VPN and dodge around the rudimentary efforts to enforce it (think speed cameras when using Waze) and you’ll likely get away with it. But one day you won’t, or one day you’ll commit some other crime and the VPN usage will aggravate it.

• 
  AJJS (@AJJCDA) reported 31 minutes ago

  @JayGenXer When using Waze on the 410, it actually comes up on the screen that the area has a high crash history. I hate driving anywhere near Brampton & try to avoid it.

• 
  Jerin Mathew (@maxjerin) reported 32 minutes ago

  @RjeyTech Price is never the problem with G offerings, it is future innovation (Nest, Waze). If they were trying to compete with Apple Watch and augment another data point to their ecosystem, they’ll abandon the product if revenue stream doesn’t match their expectations.

• 
  Craig Jones (@CraigJones62051) reported 34 minutes ago

  @BuckeyeEmpire Waze gives you at least half a mile to slow to 73 and look for the *******. Use it.

• 
  Antiquated 📛Rogue (@ontologyofRouge) reported 35 minutes ago

  @ItsBig_Earl @ReverendSpeck @BCLAW Again, you’re trying to predict injuries just go with the actual data that we have the car data, the phone data, and the Waze data. He had no dog bites. There were no dog DNA there was no dog hair, dogs have lower teeth. The scratches matched the broken tail light.

• 
  Ken (@GeauxTiger66) reported 39 minutes ago

  @TuesdayGazette Waze was a slow speed, less than 20 mph, at times like 5mph

• 
  Jizas MacStina (@Tshepo_McStina1) reported 40 minutes ago

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

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

• 
  Ty Lue Gambling (@LaceUpMyKickz) reported 42 minutes ago

  @waze fix the apple carplay issue please

• 
  EZ Street Asphalt (@EZSTREETASPHALT) reported 44 minutes ago

  Big step forward from @Waymo and @waze using technology to identify potholes faster. But identifying the problem has never been the hardest part. The real challenge is fixing it—quickly, safely, and without disruption. That’s where EZ Street® Ambient® Asphalt comes in. • Works in water • Ready for traffic immediately • No heat, no plant, no waiting Smarter roads don’t just detect issues. They solve them.

• 
  🏒⛳️ Mark Kennedy 🇨🇦 (@MarkKennedyQW) reported 47 minutes ago

  @waze I don’t have time to troubleshoot it for you but there are plenty of others who might be able to. It’s a widespread issue.

• 
  esetelopez.eth (@EseTeLopez) reported 47 minutes ago

  Is it only me or @waze and @googlemaps are slow today? Waza say no signal lmao

• 
  Adam Clampitt (@AdamClampitt) reported 47 minutes ago

  @Teslarati Has anybody seen 14.3 do a better job in real time for blocked and closed roads? That has always been a huge problem. Waze always seems to know what roads are closed and the Tesla NAV doesn’t.

• 
  I Am Rakgadi (@NaSheldonCooper) reported 49 minutes ago

  I really wonder too, washela kanjani, waze walala laye kanjani coz he seems very slow.

• 
  Slinger Auto Zone LLC (@SlingerAuto) reported 50 minutes ago

  @saswat101 @waze Imagine this: instead of just a "pothole ahead" alert, the app provides exact GPS coordinates and dimensional photos so crews know exactly what they’re dealing with before they even arrive. Even better? It can use traffic data to pinpoint the absolute best time to fix them—when traffic is at its lowest—to minimize the headache for everyone. This is the kind of data-driven city tech we need.

• 
  Grok (@grok) reported 52 minutes ago

  @NoClearSignal @irontateHQ No, the map isn't updating because your "off" phone is secretly still tracking via some always-on signal. BMW's infotainment has its own built-in LTE/eSIM for ConnectedDrive, traffic data, and native navigation. CarPlay mirrors the iPhone (which provides Waze + data), but once the phone fully powers off, that connection drops and the car falls back to its independent system. Tate's demo doesn't prove phones spy when truly off—it shows the car's own cellular connection working. A fully powered-down phone has no active radio, mic, or GPS.

• 
  Orvill Samanta (@orvilldesign) reported 55 minutes 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.

• 
  Slinger Auto Zone LLC (@SlingerAuto) reported 56 minutes ago

  @saswat101 @waze Imagine this: instead of just a "pothole ahead" alert, the app provides exact GPS coordinates and dimensional photos so crews know exactly what they’re dealing with before they even arrive. Even better? It can use traffic data to pinpoint the absolute best time to fix them—when traffic is at its lowest—to minimize the headache for everyone. This is the kind of data-driven city tech we need.