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 (48%)
• App Crashing (27%)
• Online Features (21%)
• Sign in (4%)

Live Outage Map

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

City	Problem Type	Report Time
Montauban	Glitches	3 days ago
Bordeaux	Glitches	3 days ago
Paris	App Crashing	3 days ago
São Paulo	App Crashing	4 days ago
Paris	Glitches	6 days ago
Sandillon	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:

• 
  Ian Bennetts (@IanBennettsAUS) reported 22 seconds ago

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

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

• 
  Craig Jones (@CraigJones62051) reported 6 minutes ago

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

• 
  Among the Wildflowers (@deaflibertarian) reported 7 minutes ago

  Waze has not worked well for me the last two days. I had to uninstalled then reinstalled for it to work. Then on top of that the steering wheel felt weird. Vibrations. I was worried that the vehicle was about to start having issues. Today I realized what the vibrating sensation was. My audio is always on Vol Max. I had forgotten to turn the sound off on Waze. It's been talking to a deaf woman who has been worried that she was going to have to call a toll truck.

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

• 
  Bonf1re¹ (@bon_macharia) reported 15 minutes ago

  @Kimuzi_ @xysist @indiiazi Hadi huku nowadays ata google imenishida kutumia it's too slow and very inaccurate compared to waze

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

• 
  Bobby Boulders (@ItsBig_Earl) reported 15 minutes ago

  @SnooCompliments You guys seem to put a lot of faith into John’s Waze app and a correlation of time done by a guy who has been pursuing a 4 year degree for 18+ years…What exactly is the issue here? Trust the data right? Except when it implicates the house defendants….then it’s obviously just wrong.

• 
  Sunny Spirit ❤ 🌻 (@SunnySpirit1919) reported 18 minutes ago

  I see the problem. You don't understand the data+are unable 2 synthesize info. SUV running clock SYNCED 2 REAL-WORLD TIME. John’s WAZE history CONFIRMS route= 💥WHEN+WHERE they were 💥Corroborated WHAT MAKES IT BULLETPROOF w/other OBJECTIVE DATA=Karen Read Techstream+Infotainment

• 
  KRISTIN KAY (@benchslappedtv) reported 18 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!

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

• 
  Bundle (@jhbundle) reported 20 minutes ago

  @waze fix up

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

• 
  The Pixi (@nachitopixi) reported 26 minutes ago

  @waze @MarkKennedyQW Bunch of us hare having the same problem

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

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

• 
  usoma (@usomaahah) reported 33 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

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

• 
  matt kalita (@mattkalita) reported 35 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

• 
  N (@Celatus3) reported 37 minutes ago

  @SecDuffy I’m so infuriated with congestion pricing! It feels so violating between Waze sending you through zone when you can easily avoid it to feeling completely exploited! It’s not even worth working after having to pay all this. And I’m not taking train after incident I had!

• 
  Drew Hayden Taylor (@TheDHTaylor) reported 39 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 ….

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

• 
  Matt Osborn (@themattosborn) reported 43 minutes ago

  @FSDyinzer @TheAccuracyPoli @Teslarati 💯 That is exactly what I was talking about. It is quite frustrating. There are plenty of navigation systems out there that they could model from. Why is it still an issue? And their map data is pretty old as well. A peer managed mapping system similar to Waze would be awesome.

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

• 
  B52Returns (@B52Returns) reported 47 minutes ago

  @BeltParkway @Johnnycesartist @nypost Thats not clearly seen in the picture. But Waze can help with that. In fact when I am forced to slow down too much, I start marking police locations in waze as a F U to the speed trap cops.

• 
  —𝙺𝚊𝙼𝚊𝚕𝚞𝚕𝚎𝚔𝚊🌸 (@Sizi_phiwe) reported 53 minutes ago

  @bongyluaziey Hmmm waze wayibeka mina ngyakuzwa however we cant control what people do because they might have tried to fix their skin but still face problems

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

• 
  DuVious🔜 ASC? (@DewVious) reported 57 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

• 
  Dmitry Lyalin (@LyalinDotCom) reported 59 minutes ago

  Just sent a detailed bug report to a director in Waze on a very odd map issue here in Florida. He was extremely excited to dive into this with me. People like this make all the difference in a big company.

• 
  Sef Kombo (@SefKombo) reported 60 minutes ago

  .@Waze please add option for a broken down vehicle