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 (51%)
• App Crashing (28%)
• Online Features (20%)
• Sign in (1%)

Live Outage Map

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

City	Problem Type	Report Time
Le Mont-sur-Lausanne	Online Features	2 days ago
Bordeaux	Glitches	6 days ago
Nancy	Glitches	9 days ago
Paris	Online Features	9 days ago
Angers	Online Features	10 days ago
Nîmes	Glitches	11 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:

• 
  Jacob Riverson (@EU_Cybertruck) reported 1 minute ago

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

• 
  ? 𖦹𝔩𝔦𝔱𝔱𝔩𝔢 ⚄ 𝔩𝔦𝔟𝔯𝔞⓼ ✮ (@_S0URCANDY) reported 2 minutes ago

  Turned my hazards on, reported the crash on Waze, then went around when the coast was clear.

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

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

• 
  Kool Aid Man (@koolaidman60833) reported 7 minutes ago

  @OnlyInBOS Problem isn’t Waze doesn’t differentiate vehicle size so the Lemmings follow it blindly

• 
  Tugg Speedman (@Tuggernutz87) reported 8 minutes ago

  @teslaloosa It’s more so a route planner issue. It would make FSD infinitely better if they use something like google or waze for routing.

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

• 
  Tony Velasco (@Tesla_PNW) reported 17 minutes ago

  @PhasedGravField @mikepat711 It's a big revenue earner here, along with excessive speed on hwy 500, where FSD has no probable going 15 or more over in Standard, Hurry, or Mad Max. The cops absolutely camp almost every morning along hwy 500 in se eral hidden locations in an area where traffic regularly goes ten to fifteen over and just rack up car after car. I have Waze running, so know when they are setup in those hidden spots, and make sure to drop to chill at least a mile before I get to that area when they are there to give FSD time to slow down, since it is often a sluggard about slowing down to new speeds when you change profiles. It will do it, but not always quickly.

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

• 
  waze (@waze) reported 18 minutes ago

  @PURE_IGNORANCE 1/2Hey Jean Paul, I understand you're having routing issues. That can be frustrating. Waze navigation is crowd-sourced in real time, so reports depend on input from other drivers. If you see a report that isn't accurate, tap Not there to

• 
  Lightheart (@IciclePrism) reported 19 minutes ago

  We’re not going to help these people by bringing in a few hundred thousand of them into our country. There is probably close to a billion of these people. Instead, we need to send people over there to train and educate as many of them as we can in Waze. They could work to fix this problem. They are extremely primitive people. They are inappropriate to be selected to live here in America. ________

• 
  Mashiya'Mahle 🇿🇦🇿🇦🇨🇩🇵🇸 (@Manqoba22Ngcobo) reported 23 minutes ago

  @LeviKriel @T_Tremaine10 @JacintaNgobese Waze wa dramatic nawe, who said anything about spilling blood? When has demanding what's rightfully ours become a problem? illegal can never be legal, how many more kids have to die, who's child has to be trafficked for you to wake up?

• 
  Bobby Boulders (@ItsBig_Earl) reported 23 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.

• 
  Skylarbear (@Skylarbear10) reported 24 minutes ago

  @congressdj Just buy Waze. Problem solved.

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

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

• 
  Texas Oil Man 🛢️ (@KentGra88631041) reported 30 minutes ago

  @JimHendley4NC Just purchased a new vehicle and it most certainly has the option to load and run “CarPlay” both wired and wirelessly. I use Waze via CarPlay without issue. I listen to X spaces wirelessly without issue. This thing even has a wireless charger, though it’s difficult to get alignment with a Gorilla Case on the IPhone!

• 
  Craig Jones (@CraigJones62051) reported 30 minutes ago

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

• 
  Nope nope noping (@TomWright165389) reported 31 minutes ago

  @paxangloceltae I gave up using waze because it didn’t like the patchy signal and Googlemaps seemed more resilient . I wonder if they ever fixed that issue

• 
  Madu (@madureports) reported 32 minutes ago

  Part 1: 21 one year old Jason Landry disappeared while driving home from college in December 2020. Jason was a student at Texas State University in San Marcos. On the night of December 13th, he left his apartment shortly before 11 p.m. and began driving toward Missouri City, where his parents lived. He was planning to spend time with friends during the Christmas break. His family wasn’t expecting him that night. Phone data showed Jason traveling south through Luling. At around 11:26 p.m., his phone stopped connecting to the Waze navigation app near the intersection of Magnolia Avenue and Austin Street. Investigators believe he continued straight instead of following the main road and entered Salt Flat Road, an isolate gravel road outside town. Jason apparently lost control of his Nissan Altima and crashed through a fence before striking trees. Authorities concluded that it was a single-car accident and found no evidence that another vehicle caused the crash. At 12:31 a.m. on December 14th, a volunteer firefighter discovered the wrecked car. Its headlights were still on and the keys remained in the ignition. Jason was nowhere nearby. His phone was later found wedged between the driver’s seat and the centre console. The initial response created problems for the investigation. A state trooper inspected the scene, arranged for the car to be towed and removed ********* from Jason’s backpack. However, Jason’s clothing and several belongings were left along the road, and no immediate search for a missing driver was launched. Jason’s father, Kent Landry, learned about the crash and reached the area around dawn. After finding Jason’s phone inside the impounded car, Kent returned to Salt Flat Road. Roughly 900 feet from the crash, he found his son’s shirt, shorts, underwear, socks, shoes and watch scattered along the roadway. A small blood smear was found on the clothing, but investigators said it did not suggest a serious injury. There was no blood inside the car. They believe Jason may have received a minor cut while climbing out through the damaged fence or surrounding vegetation.

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

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

• 
  Blessed sibanda (@blessedbanele) reported 41 minutes ago

  @SengezoTsh17075 Ndoda waze asithengisa libalele nje do you even think about what you doing and I think ndebele people we should work up we can fix this by other means like ke this tshabangu guy should pay for what he did and what he's doing

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

• 
  Matsobane ke lebitšo laka fela (@MatsobaneKgomo) reported 43 minutes ago

  Waze has been absolutely useless these days!!! @waze fix your nonsense

• 
  404prophet (@lightscaner) reported 46 minutes ago

  @thsottiaux Reverse engineering the USB protocol between lightburn/ezcad to a 100W fiber laser I have that I've avoided using because the software is so meh. Maybe if I build a programatic interface I'll actually use it. Launch an app I've been working on for months thats like super waze ; connects to radar detectors and shares the pings with other users. Spend a good evening reviewing new tools/skills and workflow stuff.

• 
  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.

• 
  Jizas MacStina (@Tshepo_McStina1) reported 50 minutes ago

  @KayMatthews_10 @LimChronicle Problem is some see cops and assume waze will automatically know

• 
  michal c🇮🇱🎗 (@michalys) reported 51 minutes ago

  @HenMazzig Did they give up their amart phone, the nevigator they use, The clean water they drink, the face time ups, their medical advanced service, technology, their stens.. their waze... oh wait, its ALL Israel' inventions! Who is working now on a stunning hypcricy magic heal capsulate? Their way to the psycho is open...no one can save these idiots from their selves

• 
  Mark Phillips (@iMarkPhillips) reported 54 minutes ago

  @waze You're suggesting that as only some the messages are spoken and others not that its a 'cache' problem????

• 
  Weave (@diaper) reported 58 minutes ago

  @ChuckCook It's aggravating to me because it's obvious mapmate or whatever mapping program they use has such bad speed limit data in it, and the car acts on that. Why couldn't they just use Waze for speed limits? If there's a problem with a speed limit in Waze, just hit the report button and a local editor fixes it within a day or so. Source: I've been a local Waze editor for 12 years.