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 (50%)
• App Crashing (25%)
• Online Features (23%)
• Sign in (2%)

Live Outage Map

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

City	Problem Type	Report Time
Le Mans	Online Features	2 days ago
Egg Harbor City	Online Features	8 days ago
Lyon	Glitches	16 days ago
Paris	Glitches	17 days ago
Orléans	Glitches	19 days ago
Paris	App Crashing	19 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:

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

• 
  DJ (@congressdj) reported 11 minutes ago

  @phibetakitten Don’t get me wrong. It will reach the closed road and detour just fine. The problem was that so many roads were closed, it kept mapping to the closed roads and then doing detours. It was almost endless at one point. Using Waze I was able to navigate it in 1/10 the time

• 
  DebtCollector (@DebtCollector15) reported 14 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.

• 
  Ian Bennetts (@IanBennettsAUS) reported 17 minutes ago

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

• 
  Mark Williams (@knowdelays) reported 19 minutes ago

  @MagaSgt @waze Boy you must be so desperate in your life to let the renaming of a lake drive you to that much trouble. How do you sleep at night?

• 
  MB (@paxangloceltae) reported 21 minutes ago

  @TomWright165389 Waze died on us within about 20 mins of leaving the M25 for the M1. Google Maps also screwed. Apple Maps remarkably seems to be working even on 1 bar of 5G - and even when the phones go onto SOS or satellite mode. Still, ridiculous that reception is so poor.

• 
  אינספקטור קלוזו (@55Yosi555) reported 21 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.

• 
  SFDelta (@SFDeltaActual) reported 22 minutes ago

  I fail to see the issue here. I use Waze so that it WILL load balance based on real time info. If an artery is crowded, spread the cars out to different paths. Net time improvement. Also, to the traffic planners in Las Vegas who create rolling red lights on purpose, **** you.

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

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

• 
  matt kalita (@mattkalita) reported 23 minutes ago

  @PatsKam Both of the mapping software that most people use Apple or Google maps even Waze, which is now Google anyways use the data from the phones so if a bunch of phones are sitting over a GPS location of a highway they’ll put that red as in stop traffic if it’s slow slowly moving from point a to point B they’ll color yellow and if it’s flowing, they’ll color it the green or blue whatever you have set It’s all based upon your phone data location And everyone else’s phone data location on the roadways

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

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

• 
  Gordon Cassie (@gordon_cassie) reported 29 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.

• 
  Liberalism is a Mental Disease (@kytnwv) reported 32 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?

• 
  Navid Besharati (@NavidBesharati) reported 36 minutes ago

  @Garnet_2203 @googlemaps @waze Google owns Waze you retard. This is exactly the reason why libtards are the problem with Canada 😔

• 
  Just call me HC 🇨🇦 (@DogzBreakfest) reported 36 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!

• 
  Robby94LS (@Robby94LS) reported 42 minutes ago

  @AnxiousHolly I stopped doing it awhile back too. Only reason I do it now is if an app IS having an issue. Or Waze… it never wants to let go of GPS signal otherwise.

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

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

• 
  The People's Party (@ESideEnt57) reported 46 minutes ago

  @hippyygoat Negative jurisdiction is in America you can sue WAZE contract for attempting to subvert jurisdiction. As jurisdiction in held were the issue took place.

• 
  Woody (@Porketh) reported 46 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.

• 
  Chinemerem (@Chineme85) reported 47 minutes ago

  @EstherUmoh10 Check waze if it is working in Nigeria

• 
  bipo 🎈 (@bipobuilt) reported 47 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 ****

• 
  Eugene M Quinn (@71ss396) reported 48 minutes ago

  @JulieBanderas @JesseBWatters @cvpayne There's your problem, you are using Waze.

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

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

• 
  Wayne Kennedy (@lilwaynekennedy) reported 51 minutes ago

  @401_da_sarpanch 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

• 
  Massi Tala (@massiTI) reported 51 minutes ago

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

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

• 
  D. Beck (@DBeck57030037) reported 55 minutes ago

  @drdrea1327 @mv010101 @GretchenVoss64 ●Broken TL. ●Pieces in John's clothing. ●Pieces at scene. ● #KarenRead statements, VMs, & texts. ●Scratches on John's arm. ●Broken bar glass. ●Techstream data. ●GPS, Apple Health, Waze. ●John's hair & DNA on back of her car. And I've probably missed a few items.

• 
  Jacob Riverson (@EU_Cybertruck) reported 57 minutes ago

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