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 (49%)
• App Crashing (29%)
• Online Features (20%)
• Sign in (2%)

Live Outage Map

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

City	Problem Type	Report Time
Lyon	App Crashing	2 days ago
Nantes	Glitches	7 days ago
Aldershot	Online Features	7 days ago
Weiler-Simmerberg	Glitches	7 days ago
Givors	Glitches	7 days ago
Lyon	Glitches	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:

• 
  David Keyes (@DavidMKeyes) reported 1 minute ago

  Before working with us, Ahmadinejad kept insisting that there are no gays in Israel. I told him it's pronounced "Waze," and we invented it.

• 
  InOneScoop (@InOneScoop) reported 2 minutes ago

  Shouldn’t Tesla fix its navigation issues instead of terrafab first? I know many like my fam that paused FSD subscription due to continuous navigation intervention. I man even Mapquest is more accurate. Hear me out: solution? Terra Giga Map Fab. A 335 football field long factory that will be the platinum (not gold) standard of all mapping. Compute won’t be a problem for this either because the terrafab 1 will then be joined by terrafab 2 which will be 10x larger for colossal compute power. I know I know you are asking “but why not just license and integrate Fkn Waze?” Well, for that we have to wait for Elons master plan 18 due in 2029

• 
  Monty Simmons (@simmo71084) reported 3 minutes ago

  @TheEXECUTlONER_ I do this at times when I suspect the police are just ahead (the bear box is growling or Waze shows a cop). I have seen this 1000s of times. It is as if the driver is afraid you are going to block him behind the car he is following. Just know that the driver of the truck following the vehicle in the slow lane is watching you. You can stay back for 30 minutes, and that driver will not pull into the fast lane. But the moment you get close enough to pass the vehicles in the slow lane, the truck (or whatever) will pull out into the fast lane. One way to prevent it is to know the truck driver is watching and, when you get close enough, speed up and hope the Driver is not paying attention so that you close the gap too fast. Be ready to hit your brakes just in case the driver is paying attention and pulls out anyway.

• 
  SchumaModelY (@SchumaModel3) reported 6 minutes ago

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

• 
  AI_4_Healthcare (@AI_4_Healthcare) reported 7 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?

• 
  Rolando Freitas (@rolfre27) reported 13 minutes ago

  @waze @Lean78 Hi Dani, Sorry that the link you shared has no content to continue/explain/report the issue. Just a couple of known issues with any 'next' or 'continue' button! It is a waste of time. It looks like you need clearer internal procedures to handle this.

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

• 
  Sara Higdon (@SaraHigdon) reported 17 minutes ago

  @wholemars @DevinOlsenn It could be, if able to change the speed limit control on the screen. This could actually fix two major issues, current speed limits being wrong as the entire neuro-net could be updated in real time, like in Waze, and the system can properly adjust to user preferences as it would know what said preferences are

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

• 
  Anele Simelane (@AneleCebekulu) reported 22 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!

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

• 
  Ahmedkhan (@Ahmed___khaan) reported 25 minutes ago

  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.

• 
  AmericanPowerUpgrade (@UpgradeAmerican) reported 27 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.

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

• 
  usoma (@usomaahah) reported 30 minutes ago

  @EyrahClyne @XavierNaxa I use it a lot. Due to navigation is easy to understand. But a lot of bugs still need to be reported and fix, need more users to use and reports. Even GMap or Waze still has bugs with large user base. Sometimes Apple Maps has newer update that them

• 
  Drew Hayden Taylor (@TheDHTaylor) reported 30 minutes ago

  We’ve been trying to use WAZE to get home but there’s a problem. It keeps telling us Curve Lake has moved! I know we were once a migratory people but really ….

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

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

• 
  Avni (@FawkOffAhole) reported 43 minutes ago

  @apple the latest beta up date seems to have some glitches! Uploads are slow ! And Waze has issues too I have to unconnect from the infotainment system to get the screen on it otherwise it stays frozen

• 
  EmperorX (@Caesar_DX) reported 46 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.

• 
  Bobby Boulders (@ItsBig_Earl) reported 46 minutes ago

  @Proctor4Gov @Maggie725496820 Slowed down in speed for 0.6 seconds but didn’t record any collisions? If she hit John on the road moving in the opposite direction of the flagpole…how ******** did he end up over by the flagpole? If Higgins jeep was parked at the mailbox how come she didn’t crash right into it? You see how other details matter when you’re trying to claim this ridiculous collision? If the TL collided with his arm how’s he get the cut on the eyelid and nose and such bruised knuckles but zero bruising on the arm where he was supposedly hit? The marks on the arm (32) caused by only 9 little holes…no tearing, no leftover pieces in the sleeve…again, **** your janky Waze correlation and address the injuries.

• 
  AMPed UP (@DoublepPradhan) reported 46 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

• 
  Craig Jones (@CraigJones62051) reported 52 minutes ago

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

• 
  Skylarbear (@Skylarbear10) reported 52 minutes ago

  @congressdj Just buy Waze. Problem solved.

• 
  Liberalism is a Mental Disease (@kytnwv) reported 53 minutes ago

  @Brand0n @Tesla_AI Have they programmed it to slow down when cops have been seen on the side of the road? Basically, is Waze built in and is it automated?

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

• 
  Gordon Cassie (@gordon_cassie) reported 56 minutes ago

  @ZachAbramowitz It's heavily context dependent. For some use cases, the downside is equivalent to getting lost from Waze. In others, it's more like a car crash.

• 
  DeweyCheatemandHowe (@Obiewann) reported 57 minutes ago

  Verizon Cell Services still not working for Google Waze in Central Va. I81

• 
  Jackson (@phillygeordie) reported 57 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?

• 
  bappingjump D. Oden❤️💙 (@bappingjump) reported 57 minutes ago

  @Lean78 @waze No me too since an update. Waiting for a fix

• 
  The Ringer (@Blunty) reported 58 minutes ago

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