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

Live Outage Map

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

City	Problem Type	Report Time
Bordeaux	Glitches	2 days ago
Nancy	Glitches	4 days ago
Paris	Online Features	4 days ago
Angers	Online Features	5 days ago
Nîmes	Glitches	6 days ago
Lyon	App Crashing	9 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:

• 
  Eze Adnαh 👑 (@ezeadnah) reported 52 seconds ago

  @baba_Omoloro Someone has to first tell Waze that a car is broken down before Waze tells others though. It's not instant.

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

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

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

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

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

• 
  Skullaz-san🇯🇲 (@xSkullaz) reported 11 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???

• 
  Courtney Nicholson (@courtsmegan00) reported 11 minutes ago

  @Lean78 @waze Us and others are having the same issue

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

• 
  David Makogon (@dmakogon) reported 18 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.

• 
  Ahmedkhan (@Ahmed___khaan) reported 24 minutes ago

  @elormkdaniel 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.

• 
  Jacob Riverson (@EU_Cybertruck) reported 30 minutes ago

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

• 
  EmperorX (@Caesar_DX) reported 31 minutes ago

  @leahfiles Switch to OSMand. Offline opensourced navigation. No tracking and no internet required. Works in the most remote places where Waze or Maps fail and stop working. More features and options than Waze and Maps combined. Take ownership of your privacy.

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

• 
  אינספקטור קלוזו (@55Yosi555) reported 32 minutes ago

  @AbdulElSayed You won't be able to use Israeli technology. You'll have to buy it at a price 100 times higher than the "artificial intelligence" or cyber-aid. Sherry Watergen Drips ReWalk Copaxone Pill Cam Mobileye Waze ICQ USB Disk-on-Key If you have any problems, contact Muhammad to help you.

• 
  nycwest45th (@westforties) reported 33 minutes ago

  @realericmoutsos @leahfiles who is ever going to have a problem with an app like WAZE that you would need to go to their home office?!

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

• 
  Brusimm.com (@Brusimm) reported 36 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.

• 
  Skullaz-san🇯🇲 (@xSkullaz) reported 37 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

• 
  Watanabe (@EzidLee) reported 43 minutes ago

  @DevinOlsenn I have no problem with mine. Waze? WTF is that.

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

• 
  Mark Phillips (@iMarkPhillips) reported 45 minutes ago

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

• 
  blair’s beeper (@blairsbeeper) reported 46 minutes ago

  WHY ******** ARE YOU WORKING WITH ISRAEL YOU ******* SELLOUT FAKE *** AMERICAN COMPANY @waze ******* GET THOSE DEMONS OFF YOUR ******* CONTRACT NOW

• 
  Dr Prakash Nayak (@SRIPRAKASH76) reported 47 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

• 
  Just4usewith_thisapp (@just4usewith) reported 48 minutes 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.

• 
  DuVious🔜 ASC? (@DewVious) reported 49 minutes ago

  @KetoOrkyy If you feel like you're awake but you're in a numb state, pull over and get some rest immediately. Highway Hypnosis is REAL and will **** you up. Move your head, move your eyes, park in a nice/reputable town somewhere during daytime and take a little 15 minute walk. If you don't need to be at a place at a specific amount of time, take it slow. NEVER go more than 10 (15 is okay if there's a backlog of people behind you) over when you're on the 10. Drink fluids, don't do too many energy based drinks. They'll give you a good boost but then you'll crash. NO DRIVING FOR MORE THAN 8 HOURS IN A DAY; also limit the amount of time you're driving if you've been up for 12 hours beforehand. Bit of an iffy one, but I never pick up hitch-hikers unless they look like they're on the brink of heat-stroke. Use Waze or Google Maps to know where police are, or if there's an accident ahead, etc. Bring items that you can use to repair your vehicle, duct tape, fix-a-flat, along with what Alexander Dross said in the replies. i think thats all i can think of rn

• 
  Vic Romano (@GenoakPod) reported 49 minutes ago

  @Cappo1Capponi @Biffdon That’s what I never could get with on Waze. How can I document these things like cars broken down, police etc when I am driving.

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

• 
  The Ringer (@Blunty) reported 51 minutes ago

  @vad3rt3sla CarPlay is garbage, it’s slow buggy and ugly. I would like Waze support though.

• 
  Nigel Poncewattle (@poncewattle) reported 57 minutes ago

  @oi8achevy @diaper @TeslaKing420 Wrong speed limit data can be fixed easily in Waze by submitting a map report. A local editor can fix it. Those fixes usually flow through to Google eventually. I've contacted the local editor group about getting this road fixed.

• 
  Lunchlady (@LunchLady1997) reported 59 minutes ago

  @GretchenVoss64 Laposata looked at no evidence. Scordi Belo said it was both likely and unlikely that he was hit. Also couldn’t say for certain as positioning not known. AARCa testing did not even use the weight and size of Officer O’Keefe and frankly a little bit shady… all those deleted signal messages and “ billing “questions. . They did state though that Karen backing into John’s traverse did not cause that damage. You all love to parrot “ he was not hit by a car”. He easily could have been side swiped and that is not impossible. Google accidents by side swipe. I believe in the timeline, tech stream data, Officer O’Keefe phone data, including Waze. Most importantly, per MS Read herself… on video and in written words.. her tailight was broken at 5:08 am. Before CPD ever got the call and beofre MSSP got the call. Voss got it right.