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	4 days ago
Manaus	App Crashing	6 days ago
Paris	App Crashing	7 days ago
Guimarães	Glitches	8 days ago
Paris	App Crashing	9 days ago
Paris	Glitches	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:

• 
  J (@Junxid_) reported 2 minutes ago

  Waze needs to fix up

• 
  Michael Sibley (@michael_sibley) reported 2 minutes ago

  @MarkKennedyQW @waze Having the same problem, but will be back to Google Maps before Apple 😬

• 
  Orvill Samanta (@orvilldesign) reported 2 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 (@Mark25418098) reported 5 minutes ago

  @canttreadonmi @gilarutrina @TruthFairy131 You are so correct. For a moment, I felt bad for the victim. But now I see the error of my Waze and I’ll go whip myself and apologize for my absence of pigmentation. Yes.

• 
  Nozi (@nozi03) reported 16 minutes ago

  We have a brand new problem in South Africa....Ntsiki Mazwai! Waze wasilaya uThemba @euphonik, we are subjected to her nonsensical tweets day in and day out for Elon's coins so he can pay him.

• 
  Ken (@GeauxTiger66) reported 22 minutes ago

  @TuesdayGazette Waze was a slow speed, less than 20 mph, at times like 5mph

• 
  Narr Trek (@narrtrek) reported 22 minutes ago

  @JackLinFLL Just to check if it was working I used @waze to remind me if my attaché case was in the back seat.

• 
  Amy Corrigan (@AmyCorriga28306) reported 22 minutes ago

  @waze your app isn't working on Android all day today

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

• 
  KRISTIN KAY (@benchslappedtv) reported 24 minutes ago

  @Dan_Donovan_17 @HoldenMaur50368 Nobody is arguing that the GPS became more refined after Waze was opened. That’s normal. The issue is that you are treating the data interpretation as absolute and undisputed when it wasn’t. A more accurate GPS signal does not automatically prove the CW timeline or interpretation of events. Green’s point was about how the timestamps and various phone artifacts aligned with each other not whether GPS accuracy improved from 20m to 5m.

• 
  uMARAZOR (@zizithebadgal) reported 24 minutes ago

  uMpilo waze wavelelwa… how is she responsible of fixing her parents marriage??? Putting that responsibility on a child to fix problems he caused?? K’qala wathi makazale manje uthi makalungise izinto zabantu abadala?? Oh he hates uMpilo!! #UthandoNesithembu #Uthandonesthembu

• 
  (((Aaron Walker))) (@AaronWorthing) reported 30 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

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

• 
  Bundle (@jhbundle) reported 33 minutes ago

  @waze fix up

• 
  Nthambe (@Nthambemasera) reported 34 minutes ago

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

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

• 
  NOMERCY (@NOMERCY4UTODAY) reported 39 minutes ago

  @HumanityChad If this was NY, they would have put two orange cones around it all summer, then decide to fix on Monday at 8am so Waze can reroute you because the street is now closed because of road work.

• 
  Weave (@diaper) reported 39 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.

• 
  coco the pailot (@pailot_the_coco) reported 42 minutes ago

  @waze if you do not fix apple car … Hello @TomTom

• 
  tanny.sol 🔻 (@iLoveSpectra) reported 43 minutes ago

  this is a ******** in the face to we useful idiots who spent insane money deploying hotspots, working on HIPs, subDAOs governance. they just keep selling off the vital organs of the ecosystem and are giving nothing to the builders. were like Waze mappers who got nothing on IPO.

• 
  ck (@OptimusUpRyan69) reported 47 minutes ago

  @vad3rt3sla they just need to ingest that data from waze and google maps to slow down. and then export that data out too (if they want to share)

• 
  The Sentient Dog Group (@e_considine) reported 50 minutes ago

  @The_Suburbanist I would say the obvious problem with your original idea is coordination. How do you coordinate 'paying people' not to drive into an area to limit specific traffic jams? If Waze offered that I suspect some people would try to make money by driving into rush hour traffic.

• 
  Sunny Spirit ❤ 🌻 (@SunnySpirit1919) reported 51 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

• 
  Jerin Mathew (@maxjerin) reported 52 minutes ago

  @RjeyTech Price is never the problem with G offerings, it is future innovation (Nest, Waze). If they were trying to compete with Apple Watch and augment another data point to their ecosystem, they’ll abandon the product if revenue stream doesn’t match their expectations.

• 
  Njoroge (@Joe_AlexN) reported 54 minutes ago

  @NdemoKelvin I agree, the problem is that those clowns are always on the move. It's like they're also using Waze bana. You report them, they move afew kilometers ahead.

• 
  Wayne Kennedy (@lilwaynekennedy) reported 55 minutes ago

  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

• 
  Dan Gingerich (@dangitman50) reported 56 minutes ago

  @DLCampanile That's why I use Waze. I've never been done wrong by Waze, and twice screwed myself over when I didn't get off a highway when Waze told me to. (Both cases, there was a crash ahead I didn't know about, and Waze had a way around it.)

• 
  N (@Celatus3) reported 60 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!

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

• 
  Legs (@legsanity) reported 1 hour ago

  anyone else having trouble with the Waze app? i open it and it freezes