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%)
• App Crashing (28%)
• Online Features (20%)
• Sign in (4%)

Live Outage Map

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

City	Problem Type	Report Time
Lyon	App Crashing	11 hours ago
Nantes	Glitches	5 days ago
Aldershot	Online Features	5 days ago
Weiler-Simmerberg	Glitches	5 days ago
Givors	Glitches	5 days ago
Lyon	Glitches	6 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:

• 
  Bobby Boulders (@ItsBig_Earl) reported 6 minutes ago

  @Proctor4Gov @Maggie725496820 Slowed down in speed for 0.6 seconds but didn’t record any collisions? If she hit John on the road moving in the opposite direction of the flagpole…how ******** did he end up over by the flagpole? If Higgins jeep was parked at the mailbox how come she didn’t crash right into it? You see how other details matter when you’re trying to claim this ridiculous collision? If the TL collided with his arm how’s he get the cut on the eyelid and nose and such bruised knuckles but zero bruising on the arm where he was supposedly hit? The marks on the arm (32) caused by only 9 little holes…no tearing, no leftover pieces in the sleeve…again, **** your janky Waze correlation and address the injuries.

• 
  tanny.sol 🔻 (@iLoveSpectra) reported 7 minutes ago

  this is a ******** in the face to we useful idiots who spent insane money deploying hotspots, working on HIPs, subDAOs governance. they just keep selling off the vital organs of the ecosystem and are giving nothing to the builders. were like Waze mappers who got nothing on IPO.

• 
  Ana ♐️ (@anabenge1) reported 7 minutes ago

  What is it with #Tesla’s navigation system? Why does it send me to the middle of nowhere most of the time? And why does one have to resort to Waze to get out of trouble? Elon do better please!

• 
  Madí (@madi_ayazbay) reported 11 minutes ago

  @Mike_the_Elder @NotATeslaApp I totally agree, only problem in some countries like Kazakhstan we do not have turn by turk by tesla at all. I have no idea why. But via apple carplay : waze, google maps, 2gis, maps, yandex maps all work! I wish tesla would just add all the countries as turn by turn! I do not think technically is so difficult.

• 
  Definitely Not Allen Covert (@Covert61) reported 11 minutes ago

  If there is a huge traffic jam and WAZE shows me a different route that can save me time is Waze ignoring my issue and telling me to shut up or is it offering a temporary solution to my immediate problem?

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

• 
  DJ (@congressdj) reported 12 minutes ago

  @phibetakitten Don’t get me wrong. It will reach the closed road and detour just fine. The problem was that so many roads were closed, it kept mapping to the closed roads and then doing detours. It was almost endless at one point. Using Waze I was able to navigate it in 1/10 the time

• 
  Bob Nordberg Bird Man Bob (@birdmanbob4) reported 17 minutes ago

  @leahfiles Here's your reply from the AI that just don't lie Speculative Intelligence Analysis: Waze as a Compromise Vector Location Pattern Exploitation**: Waze's continuous GPS pings, route history, speed data, and timestamps create a granular digital shadow of a target's movements—revealing regular visits to sensitive locations (e.g., hotels, clinics, private residences, or protest sites). An intelligence actor with access could cross-reference this against public records, social media, or other surveillance to build "kompromat" dossiers on affairs, medical issues, financial dealings, or undisclosed associations, then use timed leaks or implied exposure to coerce compliance, payments, or information. Real-Time and Predictive Targeting**: Live traffic/ETA data allows dynamic interception or influence operations—knowing exactly when someone is isolated in a vehicle or arriving at a vulnerable spot. Combined with app permissions (microphone/camera in some scenarios, or linked device data), it could enable opportunistic collection of audio/visual compromising material or facilitate "honey-trap" logistics by predicting availability and routes for assets. Historical data also predicts future behavior for pre-positioning. Network and Ecosystem Amplification**: Since Waze feeds into Google's broader data lake (and originated as an Israeli-founded company subject to local laws), aggregated user data can be queried at scale for social graph mapping—identifying who travels together, meets whom, and when. In a full compromise scenario, this integrates with OSINT, hacked devices, or partner-nation sharing to pressure targets via family/financial exposure, or even engineer "accidents"/discrediting events by manipulating perceived travel patterns. Privacy controls are weak once data leaves the device, and legal jurisdiction adds layers for state actors. This remains hypothetical and draws from known app telemetry practices. Actual misuse would require lawful (or illicit) access and is constrained by laws in most jurisdictions; strong operational security (VPNs, app isolation, location spoofing, minimal permissions) mitigates much of it.

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

  @waze FIX APPLE CAR!!!!

• 
  GUYER (@reyuglatig6pge) reported 19 minutes ago

  @LarryBrockJr Can anyone provide a map of the flock cameras in the Portland metro area? What about Waze? Is this another issue too tied to flock?

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

• 
  Vince (@TheVSal) reported 22 minutes ago

  @waze please respond or acknowledge that the widespread CarPlay issue is being worked on?

• 
  ? 𖦹𝔩𝔦𝔱𝔱𝔩𝔢 ⚄ 𝔩𝔦𝔟𝔯𝔞⓼ ✮ (@_S0URCANDY) reported 24 minutes ago

  Turned my hazards on, reported the crash on Waze, then went around when the coast was clear.

• 
  Robert (@berge789) reported 24 minutes ago

  @AVGirl4Life 🇺🇸🇺🇸🇺🇸. If you assimilate to our Waze, we have no problem, but when you want to put your ideals in place, this is a problem. My country is full of capitalist not monarch.

• 
  MockingbirdShot (@MockingbirdShot) reported 26 minutes ago

  @LeinadFre @FPSCANADA_SS_ZZ @koshercockney Just a taste of Israeli technology inventions: Computing and Software: Israel invented the first commercial firewall, ICQ (the first instant messenger), and the Intel 8088 processor that powered the first IBM PCs. Medicine: The PillCam is a pill with a tiny camera you swallow to check for gut issues. Other tools include the ReWalk robotic suit that helps people with leg paralysis walk again. Agriculture: Israel is the home of modern drip irrigation (like Netafim). This system sends water drop-by-drop straight to plant roots to save water in dry climates. Cars and Road Safety: Waze uses data from drivers to map the best routes. Mobileye makes computer vision chips for cars to warn drivers about road hazards. What have you done? Antisemitism, although you certainly didn’t invent that. 🙄

• 
  Faris (@farishussain) reported 28 minutes ago

  @boycatapp @amasad @ThePillarsApp We need a good 🍉 alternative to Waze (which is HQ'd in the false fake state) Please tag others in the industry, maybe someone is already working on it, or will be inspired to do so.

• 
  Craig Jones (@CraigJones62051) reported 30 minutes ago

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

• 
  Among the Wildflowers (@deaflibertarian) reported 36 minutes ago

  Waze has not worked well for me the last two days. I had to uninstalled then reinstalled for it to work. Then on top of that the steering wheel felt weird. Vibrations. I was worried that the vehicle was about to start having issues. Today I realized what the vibrating sensation was. My audio is always on Vol Max. I had forgotten to turn the sound off on Waze. It's been talking to a deaf woman who has been worried that she was going to have to call a toll truck.

• 
  Njoroge (@Joe_AlexN) reported 47 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.

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

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

• 
  Jack (@jackcoder0) reported 52 minutes ago

  First why most drivers never discover CarPlay's app ecosystem. When you connect your iPhone to CarPlay for the first time: your CarPlay-compatible apps appear automatically. Apple Maps. Apple Music. Messages. Phone. Podcasts. The Apple defaults. Third-party CarPlay apps don't appear until you download them on your iPhone. They're not promoted on the CarPlay screen. There's no "CarPlay App Store" in the dashboard. No "Discover New Apps" section. No recommendations. Download a compatible app from the App Store on iPhone, and it should appear the next time you connect. The discovery problem: you have to know an app exists, download it on your iPhone, and then it appears in CarPlay. If you don't know Waze has CarPlay support you'll never see it on your dashboard. If you don't know Overcast exists Apple Podcasts remains your only option. The result: 90% of CarPlay dashboards show 5 Apple apps. The 300+ third-party apps sit in the App Store undiscovered, uninstalled, unused. The reviewer's rule: "CarPlay's app ecosystem is a secret menu at a restaurant. The menu exists. The apps are excellent. But nobody hands you the menu. You have to know to ask for it."

• 
  🏒⛳️ Mark Kennedy 🇨🇦 (@MarkKennedyQW) reported 53 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.

• 
  Mashiya'Mahle 🇿🇦🇿🇦🇨🇩🇵🇸 (@Manqoba22Ngcobo) reported 55 minutes ago

  @LeviKriel @T_Tremaine10 @JacintaNgobese Waze wa dramatic nawe, who said anything about spilling blood? When has demanding what's rightfully ours become a problem? illegal can never be legal, how many more kids have to die, who's child has to be trafficked for you to wake up?

• 
  Ihtesham Ali (@ihtesham2005) reported 57 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.

• 
  Tinker 🇺🇸 (@TinkerTYJ) reported 58 minutes ago

  @waze we have traveled 400 miles so far today (TN and VA) and had not one notification or evidence of nearby Waze users. Your app on both cell phones in our vehicle had same issues.

• 
  Jizas MacStina (@Tshepo_McStina1) reported 58 minutes ago

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

• 
  Just4usewith_thisapp (@just4usewith) reported 1 hour ago

  @naomirwolf @Uber Occasionally I have opened up the Waze App and had the volume on low so that the driver knows I'm comparing their route with the route from Waze. I stopped using Uber after the driver started pulling away from the curb before I was fully into the backseat-- and the door was still open. He only stopped when I yelled loudly. I use Lyft instead. All good, no problems.

• 
  alana(ca sawyer) (@paciorettys) reported 1 hour ago

  i complained about this in a reddit convo i was having and someone tried to argue that drivers use waze to avoid traffic? even after i'd given multiple examples of drivers not understanding me saying "just turn on broadway instead" it's such a problem i hate it

• 
  Maximilian Kirk (@realmaxkirk) reported 1 hour ago

  @scumbagdotdll @Molaau6 It's worth using today. Some QoL features were added, like cop call outs aren't possible if the reporting user is stationary; requires 2-3 repeats to validate; etc. Honestly, it seems like cops prefer Waze these days because people slow tf down and it's less tickets that they have to write. Less interaction with the public = less opportunity for incident.