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 (51%)
• App Crashing (26%)
• 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
Paris	Glitches	14 hours ago
Orléans	Glitches	2 days ago
Paris	App Crashing	3 days ago
Romoos	Glitches	5 days ago
Zürich	Online Features	7 days ago
Le Mont-sur-Lausanne	Online Features	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:

• 
  AMPed UP (@DoublepPradhan) reported 3 minutes ago

  @bauminater I always have WAZE on while my phone is on the charger. and look at it to see where cops . do the same!! I ensure to slow down before about 3/4 miles prior. Problem solved

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

• 
  jdx (@jdxcode) reported 12 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

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

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

• 
  Tracy Martin (@IAmATMFirearms) reported 19 minutes ago

  @CrudeOil4Life @Waze, fix your anti-America mistake.

• 
  Texas 🤘🏽 Boy (@FlyAir4) reported 20 minutes ago

  If you following me and I slow down I'm helping you, Waze said the cops coming up! Don't get mad at me!

• 
  Chip Acker (@ChipAcker) reported 20 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.

• 
  caroline ౨ৎ (@MIN0RLYSTUCK) reported 24 minutes ago

  HEY @waze IM GOING TO CRASH MY CAR WITHOUT THE JONAS BROTHERS GIVING ME DIRECTIONS

• 
  Alive out of Spite🇿🇦 (@nhla_x21) reported 25 minutes ago

  I’m broken, the people I love are broken, we are all just a broken family rn💔 yoh waze wasiyenza joy brah💔💔💔

• 
  Glen O. (@buckeyegdo) reported 25 minutes ago

  @waze two issues. The mobile camera reporting is out of control. People are reporting Flock cameras when I feel the intent is to report the speed trap cameras. Secondly my icon inexplicably changed and despite changing it in settings, it is not changing on the map screen.

• 
  Noam Bardin (@noam) reported 25 minutes ago

  Launched a little experiment @maptoearn. User reports at Waze were always a scaling problem. Trying to fix it with incentives this time. x $M2E per report. No expectations, just a side project.

• 
  Jack (@jackcoder0) reported 26 minutes ago

  1. Waze the speed trap app that saves you $200+ in tickets per year. The 2026 CarPlay interface for Waze is cleaner than ever, offering crowd-sourced data on speed traps, potholes, and traffic jams without cluttering your digital real estate. Waze is the one CarPlay app every driver should install regardless of whether they use it for navigation. Waze is the go-to CarPlay app for drivers who regularly deal with heavy traffic. Its community-sourced reporting system alerts you to accidents, road hazards, speed traps, and police presence in real time, often before other apps catch up. Real-time alerts from other Waze drivers: police ahead. Speed trap. Red light camera. Construction. Hazard on the road. Car stopped on the shoulder. Object in the road. You're driving 72 in a 65. A Waze alert pops up: "Police reported ahead." You slow to 65. You pass the speed trap. No ticket. The driver behind you without Waze gets pulled over. One avoided speeding ticket: $150-300. One avoided red light camera ticket: $75-150. Waze is free. The math is obvious. Beyond speed traps: Waze frequently finds faster routes than Apple Maps during heavy traffic because its routing algorithm uses real-time data from millions of active drivers, not just historical traffic patterns. If a highway exit is suddenly backed up because of a fender bender reported 3 minutes ago Waze reroutes you before Apple Maps knows it happened.

• 
  TimmerMcGraw, CFI 🇺🇸🔎 (@TimmerMcGraw) reported 28 minutes ago

  @TheGreenOldDill My latest issue with Waze is it insisting I go down a closed road, and continuing to reroute me back to the closed road.

• 
  James Blackley (@Kingstonian84) reported 30 minutes ago

  @Nalolie21 @MagaSgt @waze His own words in the video saying he likes seeing minors topless… I think the problem is you are too scared to admit you support **********.

• 
  Lightheart (@IciclePrism) reported 32 minutes ago

  We’re not going to help these people by bringing in a few hundred thousand of them into our country. There is probably close to a billion of these people. Instead, we need to send people over there to train and educate as many of them as we can in Waze. They could work to fix this problem. They are extremely primitive people. They are inappropriate to be selected to live here in America. ________

• 
  Bryce Tackett (@BryceTackett4) reported 33 minutes ago

  @TinkerTYJ @OmariYeager @waze Drove about 500 miles today, app is not working correctly didn’t get a single update of anything

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

  Listen me no one force yall mofos to use waze!! If you have a issue report it but you better be respectful cause I am not short of a sym and I will definitely ignore your report !! Think it tek boy fi sit up at nights fix **** so people routes while using waze can be better???

• 
  Massi Tala (@massiTI) reported 35 minutes ago

  @congressdj @daltonbrewer Even on in car browser Waze is working

• 
  Kailash Mhetre (@KailashMhetre) reported 35 minutes ago

  @republic I think we are unnecessarily dragging the issue ,If only mumbai police wld hve properly ****** Waze he wld hve omitted the truth long back.

• 
  Chris Vaughan (@calmorit) reported 41 minutes ago

  @MagaSgt @waze What’s the issue? No doubt you know the route to McDonalds.

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

• 
  Anele Simelane (@AneleCebekulu) reported 43 minutes ago

  Still can’t believe that they water people hit an electric cable that the electricity people have to fix and we’re going on 48hrs of no power in Bryanston 😭 Yoh City of Johannesburg waze wasenza!

• 
  Addicted Pig Kent (@AddictedPigKent) reported 43 minutes ago

  @Goddessjaide03 I want to learn the error of my Waze, mummy

• 
  Faris (@farishussain) reported 45 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.

• 
  Ian Bennetts (@IanBennettsAUS) reported 45 minutes ago

  @freeloader2021 Is the problem FSD the Driver or FSD the Navigator. I think map data needs lanes selection like waze

• 
  · (@Thejacobdean) reported 45 minutes ago

  @NotATeslaApp No they should have FSD automatically slow down based off the Waze/apple/google police data though. I have 2 tickets in FSD mad max

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

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

• 
  Robert (@berge789) reported 55 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.

• 
  Dr Prakash Nayak (@SRIPRAKASH76) reported 59 minutes ago

  We had major problem following Waze directions traveling from London to Folkestone . Near or around Maidstone there was some road blocks. Waze kept sending us in circles repeatedly asking to take closed roads. It was getting dark. Stopped to download TomTom. @waze