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

Live Outage Map

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

City	Problem Type	Report Time
Pierre-Bénite	Online Features	1 day ago
Manaus	App Crashing	4 days ago
Paris	App Crashing	4 days ago
Guimarães	Glitches	5 days ago
Paris	App Crashing	6 days ago
Paris	Glitches	6 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:

• 
  Jonathan Mills (@ICommunityNote) reported 8 minutes ago

  @DillonLoomis @butala_aryan Can they just partner with Waze and fix everything overnight? That would be good.

• 
  Nthambe (@Nthambemasera) reported 8 minutes ago

  @msiziworld Waze has no problem thre settings by the user are a problm

• 
  KRISTIN KAY (@benchslappedtv) reported 9 minutes ago

  @Dan_Donovan_17 @HoldenMaur50368 I never said Waze had its own GPS satellites. Everyone knows Waze uses the iPhone’s GPS/location services. That was never the issue. What Green was talking about was the timestamps and how different phone artifacts and app data lined up against each other. That is a normal digital forensics issue. Different apps and datasets can have different timing offsets and logging behaviors. That is what he was referring to!

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

• 
  Zlatan Gomez (@zan_diva) reported 14 minutes ago

  Can I vent ??? As a person from the townships who moved to the suburbs.. I'm struggling with Police visibility.. my brain associates cops with trouble.. I'd only see cops when they are WORKING.. here they just around, nje.. Just parked nje. Waze shows 9 cops.. nje just present

• 
  Salvador Chavarria (@schavarriaTexas) reported 14 minutes ago

  @htsfhickey Fred - real life example…google maps is actually now really bad at optimizing routes. Really bad…switched to waze which is also owned by google as you know but still seems to be working fine

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

• 
  Greg Prescott (@prescott_greg) reported 20 minutes ago

  @TheSuzieHunter Is your Waze not working??

• 
  Robert G. Schaffrath 🥑🌵🌶️🌻 (@whobeu) reported 22 minutes ago

  @ironcanary @TaraBull I went 6s Plus to 13 Pro. Too many important apps stopped working to keep using it. But I still use it for Waze.

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

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

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

• 
  Janek Mann (@janekm) reported 32 minutes ago

  @emollick And I'm convinced that Waze does the opposite... Always prefer the slow route through a residential neighbourhood so the users feels like they're taking a "shortcut".

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

• 
  Weave (@diaper) reported 38 minutes ago

  @NevrEnoughX @billykyle @grok Which is why I wish Tesla used Waze maps for navigation. If there's an issue, click report button in app and someone local will be fixing it in a day or so. For example, when Virginia opened up 20 miles of new Express lanes on I-66, the day it opened Waze maps were already updated and routing people on it correctly.

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

• 
  Mark (@1zSolace) reported 41 minutes ago

  @waze why does every intersection I pass, Waze thinks I am turning at? Every time the map turns thinking I turned when I never even touched the wheel. Can you fix that?

• 
  Johanna (@JohannaMordecai) reported 41 minutes ago

  @Proctor4Gov @TeamFUKR Car on at 00.12.36 1162.1 at 10mins 57, that’s at 00.23.33 3 problems Whiffin says turn complete at 00.23.58 Burgess says 00.23.58 was before 3pt And they used the Waze clock which isn’t a clock but a counter, which is unreliable per Whiffin, & is ahead by 3mins 1sec

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

• 
  Property and Cars kings (@CarandProperty) reported 44 minutes ago

  @Julius_S_Malema @NgizweMchunnu Working for you is real colonisation. Imagine wasting all the time for your lawyer just for and apology? Chief use your resources very waze. How does and apologise benefit the ground flow of Eff? Yeah @FloydShivambu really was running the retail store for you.

• 
  Irksome (@Irksome73) reported 44 minutes ago

  @ListerLawrence It's a @waze problem - they need to add the option for highway agency or whatever its called this week.

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

• 
  the3rdestate (@the3rdestate_cl) reported 45 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

• 
  Dogsrgreat : pass the A1🤔 (@Dogsrgreat2) reported 47 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.

• 
  zeerusli (@zeerusli) reported 49 minutes ago

  @waze Wait your quick action to fix this. Most of users experiencing the same. So it should be general issue now. No need to be hassled submiting here and there.

• 
  BasedSouthAsian (@BasedSouthAsian) reported 51 minutes ago

  @CP24 Maybe she's too retarded to drive, the rates are well posted, there is a toll calculator online, even Waze calculates the toll for you... so if with all that you're still 'surprised', then that's a you problem.

• 
  AJJS (@AJJCDA) reported 52 minutes ago

  @JayGenXer When using Waze on the 410, it actually comes up on the screen that the area has a high crash history. I hate driving anywhere near Brampton & try to avoid it.

• 
  Isisí (?) (@luisuxanz) reported 52 minutes ago

  @BowTiedPassport Trusting the Waze ETA is the ultimate error in CDMX

• 
  (((Aaron Walker))) (@AaronWorthing) reported 53 minutes ago

  What the hell, @waze and @googlemaps I was trying to see a friend in the hospital and first I used Waze. I told the system not to put me on any toll roads and I knew from previous travel it was possible to get there without going on a toll road. Yet your system kept trying to put me on a toll road So I switched to Google Maps, and you guys were doing the same thing. I told you not to put me on toll roads and you kept trying to put me on a toll road. FIX THIS

• 
  Sicario (@Mpizozo2020) reported 1 hour ago

  Waze wakwata uRatha am sure no gal @LindA_MniSii uyagowa. Problem with this judge is that he hates these accused, and I doubt it is because of Senzo Meyiwa's murder. This old hag is ***** @OCJ_RSA this is not a judge but a criminal representing justice sysytem #SenzoMeyiwaTrial

• 
  Avni (@FawkOffAhole) reported 1 hour 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