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 (47%)
• Online Features (24%)
• App Crashing (23%)
• Sign in (6%)

Live Outage Map

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

City	Problem Type	Report Time
Toulouse	Glitches	3 hours ago
Pierre-Bénite	Online Features	5 days ago
Manaus	App Crashing	7 days ago
Paris	App Crashing	8 days ago
Guimarães	Glitches	9 days ago
Paris	App Crashing	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:

• 
  (((Aaron Walker))) (@AaronWorthing) reported 6 minutes ago

  What the hell, @waze and @googlemaps I was trying to see a friend in the hospital and first I used Waze. I told the system not to put me on any toll roads and I knew from previous travel it was possible to get there without going on a toll road. Yet your system kept trying to put me on a toll road So I switched to Google Maps, and you guys were doing the same thing. I told you not to put me on toll roads and you kept trying to put me on a toll road. FIX THIS

• 
  🫶🏽forcoloredsonly. (@waytooblunt_) reported 9 minutes ago

  Waze was already based in Israel. Please stop the fake outrage every time yall discover a new piece of information. You move over to google or apple and you still gone have the same problem.

• 
  Ken (@GeauxTiger66) reported 9 minutes ago

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

• 
  Maqhawe Simelane (@Buqhawe) reported 13 minutes ago

  @zizipho50 Waze wayisilima we Oros, working with other countries is what we need, illegal immigrants must go back home and fix their papers.

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

• 
  Peter Miles (@ginjajedi) reported 21 minutes ago

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

• 
  LT (@LtMunst) reported 27 minutes ago

  @TeslaKing420 A simple fix if Tesla would just bite the bullet and license Waze.

• 
  Pablo Sarco (@jPabloSarco) reported 28 minutes ago

  It is the same with Waze or Google maps. Sometimes the route I selected is because different reasons and saving time is not important. Looks like a problem with all these routing software

• 
  ck (@OptimusUpRyan69) reported 32 minutes ago

  @vad3rt3sla they just need to ingest that data from waze and google maps to slow down. and then export that data out too (if they want to share)

• 
  SchumaModelY (@SchumaModel3) reported 33 minutes ago

  @TeslaTim2 @Tesla @Tesla_AI Hey Tesla, ask for help! Waze, google, whatever. Just FIX THIS ****!

• 
  paperwork nota (@icecoldbanger) reported 34 minutes ago

  @WormWoodMotorCO same issue @waze what’s happening ???

• 
  John_Hawkins (@JohnHawkin71262) reported 38 minutes ago

  @ClimateWarrior7 I just drive at normal speeds and slow down for the cameras. Use Waze and even alerts you to police mobile cameras. Never any points.

• 
  Jonathan Mills (@ICommunityNote) reported 38 minutes ago

  @DillonLoomis @butala_aryan Can they just partner with Waze and fix everything overnight? That would be good.

• 
  AmericanPowerUpgrade (@UpgradeAmerican) reported 41 minutes ago

  @SDembraski Would love if it pulled into MY driveway, not my neighbor's. Parking is a real issue — we need handicap placard support for spot selection. Navigation also needs work: FSD constantly takes scenic routes out of parking lots and even my cul-de-sac (starts a right turn, then yanks left to loop around the block). Surprisingly, Google Maps and Waze have the same problem.

• 
  Bob Nordberg Bird Man Bob (@birdmanbob4) reported 44 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.

• 
  Mashiya'Mahle 🇿🇦🇿🇦🇨🇩🇵🇸 (@Manqoba22Ngcobo) reported 48 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?

• 
  Tugg Speedman (@Tuggernutz87) reported 49 minutes ago

  @teslaloosa It’s more so a route planner issue. It would make FSD infinitely better if they use something like google or waze for routing.

• 
  Janek Mann (@janekm) reported 50 minutes ago

  @emollick And I'm convinced that Waze does the opposite... Always prefer the slow route through a residential neighbourhood so the users feels like they're taking a "shortcut".

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

• 
  BasedSouthAsian (@BasedSouthAsian) reported 51 minutes ago

  @CP24 Maybe she's too retarded to drive, the rates are well posted, there is a toll calculator online, even Waze calculates the toll for you... so if with all that you're still 'surprised', then that's a you problem.

• 
  AnonyMassLawyer (@anonymasslawyer) reported 57 minutes ago

  @Suzybeau1 @Martine05885145 She got within WiFi range at 12:36:39. Waze records very precise GPS data (error radius less than 5m) with accurate timestamps. From the time Waze was activated (12:20) to when then arrived at 34 Fairview (12:24:38) we have incredibly precise time/location data for the SUV

• 
  Tony (@TonyB_1997) reported 57 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.

• 
  Bundle (@jhbundle) reported 57 minutes ago

  @waze fix up

• 
  Snedley Grassbuckets (@sned) reported 57 minutes ago

  @wholemars Fix the bloody navigation. Use a reliable mapping service with local editors who fix problems quickly -- aka Waze.

• 
  Jacob Riverson (@EU_Cybertruck) reported 59 minutes ago

  @itskyleconner EV Waze wouldn’t be too hard to build the API cost would be the largest issue I see

• 
  Greg Prescott (@prescott_greg) reported 59 minutes ago

  @TheSuzieHunter Is your Waze not working??

• 
  Ty Lue Gambling (@LaceUpMyKickz) reported 1 hour ago

  @waze fix the apple carplay issue please

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

• 
  coco the pailot (@pailot_the_coco) reported 1 hour ago

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

• 
  Frank van der Wal (@frank_wal) reported 1 hour ago

  @WazeNederland @waze Hi, I’ll re-install the app on my Iphone and try if this will solve the problem