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 (27%)
• Online Features (21%)
• Sign in (4%)

Live Outage Map

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

City	Problem Type	Report Time
Montauban	Glitches	1 day ago
Bordeaux	Glitches	1 day ago
Paris	App Crashing	1 day ago
São Paulo	App Crashing	2 days ago
Paris	Glitches	4 days ago
Sandillon	App Crashing	7 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:

• 
  Mark Phillips (@iMarkPhillips) reported 5 minutes ago

  @waze You're suggesting that as only some the messages are spoken and others not that its a 'cache' problem????

• 
  paperwork nota (@icecoldbanger) reported 7 minutes ago

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

• 
  Maqhawe Simelane (@Buqhawe) reported 8 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.

• 
  Washington State Ferries (@wsferries) reported 9 minutes ago

  @SQZA55 @KIRO7Seattle Not when the boarding pass is activated. We have been working with GPS apps, but so far only Waze has changed their routing.

• 
  The Sentient Dog Group (@e_considine) reported 11 minutes ago

  @The_Suburbanist I would say the obvious problem with your original idea is coordination. How do you coordinate 'paying people' not to drive into an area to limit specific traffic jams? If Waze offered that I suspect some people would try to make money by driving into rush hour traffic.

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

• 
  Wayne Kennedy (@lilwaynekennedy) reported 12 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

• 
  Craig Jones (@CraigJones62051) reported 14 minutes ago

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

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

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

• 
  Michael Sibley (@michael_sibley) reported 15 minutes ago

  @MarkKennedyQW @waze Having the same problem, but will be back to Google Maps before Apple 😬

• 
  baseball enjoyer 3000 (@TheNotoriousHRT) reported 15 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.

• 
  LeBBC (@Big_Black_Coq) reported 15 minutes ago

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

• 
  Jackson (@phillygeordie) reported 22 minutes ago

  @Don312A @ardeiusmaleus @catgirlprostate How is it “extreme levels of favoritism” when other maps show the land as Israel and Waze doesn’t? I don’t really see the problem?

• 
  Adam Elkassas (@adampredev) reported 22 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

• 
  Mkhono onodaka🇿🇦 (@MSIZI_K95) reported 23 minutes ago

  @msimanga_wela @ISephara Baba waze wamdala ubheda , what about the victim whose identity was stolen?? The problem with you old people nicabanga kafushane , most of you are not patriotic . Corruption is rife and the economy is declining and Nina nibusy allowing criminals to prosper ?! Ay man sies

• 
  Dogsrgreat : pass the A1🤔 (@Dogsrgreat2) reported 23 minutes ago

  @FIRs_GIRs @BLKMDL3 They are working on a Waze integration. They already use Google Maps but I have heard rumors of this for a while. They try to cut every penny of cost. It’s about ROI. Software is cheap hardware is expensive.

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

• 
  Skullaz-san🇯🇲 (@xSkullaz) reported 30 minutes ago

  @jay26440083 @perryodontology nothing is wrong with using waze the app has a reporting feature that helps editors to fix routing issues. so unless someone reports it then it wont get fixed

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

• 
  DebtCollector (@DebtCollector15) reported 33 minutes ago

  @OGsDontFold Google Maps is so trash. Randomly won't give audio updates for turns, suggests locations further away for no sensible reason, randomly loses connection and stops updating directions. I have tried Waze and it gives me similar problems. There is no winning these days.

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

• 
  AI_4_Healthcare (@AI_4_Healthcare) reported 42 minutes ago

  𝒀𝒐𝒖 𝒄𝒂𝒏'𝒕 𝒑𝒖𝒕 𝒕𝒉𝒆 𝑱-𝑨𝑰-𝑴 𝒃𝒂𝒄𝒌 𝒊𝒏 𝒕𝒉𝒆 𝒋-𝑨𝑰-𝒓. 𝑾𝒆 𝒇𝒆𝒅 𝒕𝒉𝒆 𝑨𝑰 𝒎𝒂𝒄𝒉𝒊𝒏𝒆 𝒇𝒐𝒓 𝒚𝒆𝒂𝒓𝒔; 𝒕𝒉𝒆 𝒐𝒏𝒍𝒚 𝒘𝒂𝒚 𝒐𝒖𝒕 𝒊𝒔 𝒕𝒉𝒓𝒐𝒖𝒈𝒉 Big Tech is dropping billions like it's nothing. AI models are accelerating weekly ... from LLMs to AI agents to full orchestras of them running directly on our phones and desktops. Chatbots everywhere. Humanoids on the horizon. The world feels like it's spinning faster than anyone can track. Drones are no longer science fiction; they're reshaping warfare in real time, from Ukraine to the Gulf, amplifying chaos as conflicts escalate with tools we barely understand yet feel powerless to slow. Societal distrust is deepening. People fear massive job losses, bleak prospects for new graduates, and mounting risks around privacy and safety. Many believe governments are hopelessly behind and regulators simply cannot move at the speed of the technology they're supposed to govern. On this, they're not wrong. But here's the truth: AI is already everywhere ... we spread it around, ourselves. Every tap and swipe has been training it for years. Auto-correct, Grammarly, Amazon purchases, tap-to-pay, social feeds, Waze, Netflix — the list is longer than most of us care to admit. We've flooded social media with graduation photos, videos of family vacays, and parents' obituaries; freely, eagerly, in real time. We recycled passwords across hundreds of accounts and clicked "agree" without reading a word. Identity theft and privacy violations? We continue to feed this machine through digital non-hygiene akin to the plague. It's already a buffet for AI-enabled fraudsters that we've served up. Corporations built platforms we loved: convenient, free, endlessly scrolling, and we accepted the trade-off with eyes at least half open. The business model was never hidden. We just chose not to think too hard about it. We spread the J-AI-M ourselves, every tap and swipe, 7-24-365 for years. The workforce consequences are no longer hypothetical. Copywriters, paralegals, customer service agents, and new grads are feeling the ground shift. The economic upside of AI is real, but it's flowing overwhelmingly to shareholders, not displaced workers. We need retraining pipelines, and we needed them yesterday. The promise is equally real! AI is transforming healthcare, will accelerate clean energy, 10X our climate change fight, and take us to other planets. The j-AI-r is open; what's inside is not all bad. There is more real hope than ridiculous hype. Do we push for algorithmic transparency laws? Demand digital literacy in schools and workplaces, not just how to use AI, but how to think critically about it? Support liability frameworks that hold developers accountable for measurable harm? Insist that workforce transition funding be tied to the companies generating billions from automation? Yes, no, what else? We made this J-AI-M. We spread it everywhere. We must be honest enough about our own roles to navigate what comes next ... wisely. 🤔 Of interest @lexfridman @garymarcus @LuizaJarovsky?

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

• 
  Jerin Mathew (@maxjerin) reported 49 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.

• 
  N (@Celatus3) reported 50 minutes ago

  @SecDuffy I’m so infuriated with congestion pricing! It feels so violating between Waze sending you through zone when you can easily avoid it to feeling completely exploited! It’s not even worth working after having to pay all this. And I’m not taking train after incident I had!

• 
  Legs (@legsanity) reported 51 minutes ago

  anyone else having trouble with the Waze app? i open it and it freezes

• 
  AnonyMassLawyer (@anonymasslawyer) reported 53 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

• 
  David Makogon (@dmakogon) reported 55 minutes ago

  @AustyUSA Don’t forget all the people who hate on CarPlay, with snarky comments like… comparing to a coke freestyle machine. Tesla software is nowhere near perfect. Map/direction issues, non-trivial air control, small fonts & touch zones, no Waze, no proper group texts, on and on.

• 
  the3rdestate (@the3rdestate_cl) reported 59 minutes ago

  @CoasterK24 so...on our "waze" type theme park app, we can include buttons on rides for users to check if a feature is working or not...like when you check that a car is still on the side of the road like waze etc, and you can report a feature not working etc...cl

• 
  Tshepo Chiloane (@mohlakale) reported 59 minutes ago

  @jerry_peep @LimChronicle The problem is not using Waze. The problem is reckless driving