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 (53%)
• App Crashing (25%)
• Online Features (21%)
• Sign in (1%)

Live Outage Map

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

City	Problem Type	Report Time
Lyon	Glitches	5 days ago
Paris	Glitches	6 days ago
Orléans	Glitches	7 days ago
Paris	App Crashing	8 days ago
Romoos	Glitches	10 days ago
Zürich	Online Features	12 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:

• 
  DJ (@congressdj) reported 3 minutes ago

  @SurScribbles It has problems integrating with many cars (believe, I feel like I always seem to rent them in my travels), I don’t think adding more stuff to the Tesla UI is the answer. Plus, my phone is always with me. I have access to all of the stuff CarPlay would carry over. I can stream music directly from my phone, or use Waze (which I do). At the end of the day, CarPlay is meant to bridge the car to its passenger. But with autonomy, none of that is necessary. Ultimately, you’ll be able to use your phone or laptop or anything else in the car. That’s why I think CarPlay is a step backwards. Not forward.

• 
  Wayne Kennedy (@lilwaynekennedy) reported 4 minutes ago

  This is the exact thing I've been saying. These ******* clowns don't speak English, have no idea where they are going and will cross five lanes of traffic last minute to hit an exit because their Waze is slow. I've seen mother ******* backing up on DVP exits. @OPP_HSD

• 
  bipo 🎈 (@bipobuilt) reported 6 minutes ago

  see the problem with google maps and waze is that waze has way better cop reporting but every time i try to use it for navigation that shits ***** me all up cause I dont go anywhere normal so I gotta use google maps but the reporting SUCKS ****

• 
  Alan (@bitforth) reported 11 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.

• 
  fluxity (@tjosephfluxity) reported 13 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.

• 
  Woody (@Porketh) reported 13 minutes ago

  @ListerLawrence Waze, for best updates of issues ahead. It once warned of "vehicle in lane ahead" on 4 lane, dark/ unlit rainy M1.... And there was a car stopped with faded hazards. Been loyal since then. Today, used LR nav as phone was dead. Took me down two closed roads in France.

• 
  Edgars Zīverts (@edziverts) reported 17 minutes ago

  @ChinaEV_Eng_Lif Try coming to Eastern Europe; Tesla cannot fix its maps for 2+ years. Waze really is the gold standard; too bad there is no native app.

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

• 
  Weave (@diaper) reported 24 minutes ago

  @ChuckCook It's aggravating to me because it's obvious mapmate or whatever mapping program they use has such bad speed limit data in it, and the car acts on that. Why couldn't they just use Waze for speed limits? If there's a problem with a speed limit in Waze, just hit the report button and a local editor fixes it within a day or so. Source: I've been a local Waze editor for 12 years.

• 
  Sean Eddy (@seaneddy) reported 24 minutes ago

  I've been known to tag a bunch of police cars on Waze throughout my shift so people slow down and I don't have to work accidents.

• 
  Michelle Jacobik (@michellejacobik) reported 30 minutes ago

  I had 3 obstacles this morning!! 🤬And to me this feels like the most important travel day of my year!! My Uber never showed up — got in my car to make it to the airport thank God I turned on my WAZE app!!! There were 2 bad accidents on the highway and I was rerouted right before I turned on !! Took back roads, which took me 50 minutes instead of 30 — Then our pilot came off plane to waiting area to say that he didn’t like the way he felt worse from Atlanta to Florida so he was going to have maintenance do some things and check some records (like a gut thing) That took us another hour and 15 minutes - just landed in Atlanta with like 12% battery - there were no chargers working in my row plane and I just got to my gate 10 minutes to spare!! Grateful I made it!!! My soldier 🇺🇸 is picking me up and tomorrow’s a pretty milestone day for him and why I’m here🥰🇺🇸 #reuniting #mompride

• 
  Craig Jones (@CraigJones62051) reported 31 minutes ago

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

• 
  Shän🤎 (@SharonNassanga2) reported 33 minutes ago

  The problem people be looking at you nga balowooza Waze kwetega🥲

• 
  Paugus Tadmuck (@PaugusSpdragoo) reported 33 minutes ago

  @MJBiercuk @qctrlHQ It depends on having an up-to-date map file in the system. While it may sound like how GPS works...it doesn't. With GPS, the receiver measures how long it takes to get the radio signal from the GPS constellation (since the speed of light in an atmosphere is pretty fixed), so it can calculate its position. Kind of like counting the time in seconds between seeing a lightning flash & hearing the thunder, then dividing by 6 to figure out how many miles away the lightning hit. At best, a gravitic-based sensor will tell you how far you might be from the closest portion of the Earth...but I suspect the math involved & the actual measurement & detection of the gravity field is much more complex than that. And since apparently they're saying "gravity fluxuates quite a bit as you travel through the ocean", that's why you need the updated map so that you can know where you're at. I also strongly suspect, now that I've had a few more days to think about it, that it also requires some sort of **initial** position fix to work. Because I would also suspect that, since a lot of the Earth's crust is made of similar materials, and there are sections of the ocean with similar depths & similar crust/coastal configurations, that the system can't just say "Given a gravitic flux of 0.xabcz, you are at latitude XX.YY.ZZ and longitude TT.UU.VV.", because that particular flux reading is probably **not** unique. Which makes this more akin to INS (which is ***highly*** dependent on knowing exactly where you started from to determine your current position)...unlike GPS, which (unless you're using Google Maps, Apple Maps, Waze, or some other routing app) doesn't give AF where you started from, because it doesn't need that to know where you're currently at.

• 
  Punished Sneed (@RacismFan45) reported 35 minutes ago

  @faustianwigger Reporting a crash on waze after i showed a cyclist the error of his ways (a hit and run).

• 
  Randall (@Randall145695) reported 35 minutes ago

  @Asor1113 @DoctorTurtleboy @ALL_WEDO_ISWORK Ok, so now it happened outside before Karen even got back to Meadows? What a fascinating goal post shift. The problem with that is the dog would've had to attack and incapacitate him within about 20 seconds. Here's why: The high accuracy Waze data shows the SUV coming to its first and only complete stop in front of the house by the flagpole at 12:24:38 a.m. John's phone then recorded no movement for about 7 minutes as he sat in the car with Karen. At 12:31:56 a.m., a brief 20-second step event began as he exited the car. And at 12:32:16 a.m., his phone stopped moving until 6:04 when the 3 women found him and called 911.

• 
  Jack (@jackcoder0) reported 36 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."

• 
  Just call me HC 🇨🇦 (@DogzBreakfest) reported 38 minutes ago

  @Garnet_2203 @googlemaps @waze I TRULY DON'T CARE!!!! We have far bigger problems than a stupid name. Get with the program & start posting about Canada's immigration problems. Drug problems. Homelessness. There is a plethora of massive issues here so a stupid map choice is not my MAIN CONCERN!

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

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

• 
  jdx (@jdxcode) reported 42 minutes ago

  @TheLaluka @waze @gouvernementFR I suspect if you were asking in the US they'd want nothing to do with it for liability reasons, no idea if there would be similar issues in France

• 
  Chinemerem (@Chineme85) reported 44 minutes ago

  @EstherUmoh10 Check waze if it is working in Nigeria

• 
  Brusimm.com (@Brusimm) reported 45 minutes ago

  Dear #Waze, wtf is your problem today, telling me to take the long way home. The way I've never taken, while my usual, shorter route was just fine??? I remember when waze was the better option. And now... ? SMH.

• 
  Matsobane ke lebitšo laka fela (@MatsobaneKgomo) reported 49 minutes ago

  Waze has been absolutely useless these days!!! @waze fix your nonsense

• 
  Narr Trek (@narrtrek) reported 55 minutes ago

  @JackLinFLL Just to check if it was working I used @waze to remind me if my attaché case was in the back seat.

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

• 
  Wáhálá (@thewahalaboy) reported 57 minutes ago

  Don’t ever use the Waze app in Lagos if you don’t want problems with LASTMA. #noteToSelf

• 
  J (@JayIn208) reported 58 minutes ago

  @MagaSgt @waze Oh no. I’m sure they’ll fix it after that comment. Their very existence is dependent on you having their app.

• 
  john Xanax lynch (@burnerversity) reported 58 minutes ago

  @waze fix the ******* wait times nothing has been accurate

• 
  Tinker 🇺🇸 (@TinkerTYJ) reported 59 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.

• 
  Chip Acker (@ChipAcker) reported 59 minutes ago

  Dear @waze I love your maps! However, since you added the animation at app launch, my app locks up and I can’t put in my desired address. It works about 50% of the time. Please fix it. In the meantime I’ll be using @Apple maps.