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
Bordeaux	Glitches	2 days ago
Nancy	Glitches	5 days ago
Paris	Online Features	5 days ago
Angers	Online Features	6 days ago
Nîmes	Glitches	6 days ago
Lyon	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:

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

• 
  AMPed UP (@DoublepPradhan) reported 1 minute ago

  @bauminater I always have WAZE on while my phone is on the charger. and look at it to see where cops . do the same!! I ensure to slow down before about 3/4 miles prior. Problem solved

• 
  jdx (@jdxcode) reported 2 minutes ago

  @TheLaluka @waze @gouvernementFR I suspect if you were asking in the US they'd want nothing to do with it for liability reasons, no idea if there would be similar issues in France

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

• 
  Rahul Sood 🏴‍☠️ (@rahulsood) reported 10 minutes ago

  @wholemars I've got two tickets on FSD.. it's annoying.. Tesla should build in radar detector/waze style police awareness and slow down.

• 
  Sef Kombo (@SefKombo) reported 12 minutes ago

  .@Waze please add option for a broken down vehicle

• 
  Mashiya'Mahle 🇿🇦🇿🇦🇨🇩🇵🇸 (@Manqoba22Ngcobo) reported 12 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?

• 
  crazy people out there (@ron_doingstuff) reported 13 minutes ago

  @congressdj @Spencer10438140 I was trying to get waze working, so at least it would alert me. I was having issues with waze bluetooth talking over the tesla audio. I could not hear both at the same time. Grok said there was some browser version of tesla waze. Too busy to figure this out so far :)

• 
  Jason Wallace (@TragedyCalls) reported 14 minutes ago

  @nursedanakay Surely it cannot be beyond the wit of man to map where they are. Certainly telematics should be telling the car something's not right in the same place every day. I have a similar issue on my route and @waze. 9 speed humps which variously appear and disappear .

• 
  Cyberwild (@Cyberwildx) reported 14 minutes ago

  @Ademola_Alesh Use Waze..advanced warning just slow down when needed..all other times foot down

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

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

• 
  Lodeci 로데시 🏁 (@Lodeci_) reported 15 minutes ago

  Had Waze for almost 10 years it feels like , I had absolutely no problem deleting that bullshit.

• 
  Monty Simmons (@simmo71084) reported 22 minutes ago

  @TheEXECUTlONER_ I do this at times when I suspect the police are just ahead (the bear box is growling or Waze shows a cop). I have seen this 1000s of times. It is as if the driver is afraid you are going to block him behind the car he is following. Just know that the driver of the truck following the vehicle in the slow lane is watching you. You can stay back for 30 minutes, and that driver will not pull into the fast lane. But the moment you get close enough to pass the vehicles in the slow lane, the truck (or whatever) will pull out into the fast lane. One way to prevent it is to know the truck driver is watching and, when you get close enough, speed up and hope the Driver is not paying attention so that you close the gap too fast. Be ready to hit your brakes just in case the driver is paying attention and pulls out anyway.

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

• 
  Craig Jones (@CraigJones62051) reported 24 minutes ago

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

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

• 
  Narr Trek (@narrtrek) reported 30 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.

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

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

• 
  —𝙺𝚊𝙼𝚊𝚕𝚞𝚕𝚎𝚔𝚊🌸 (@Sizi_phiwe) reported 34 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

• 
  Madu (@madureports) reported 35 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.

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

• 
  Robert (@berge789) reported 42 minutes ago

  @AVGirl4Life 🇺🇸🇺🇸🇺🇸. If you assimilate to our Waze, we have no problem, but when you want to put your ideals in place, this is a problem. My country is full of capitalist not monarch.

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

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

• 
  Massi Tala (@massiTI) reported 46 minutes ago

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

• 
  Lauran™ (@lauranruddy) reported 50 minutes ago

  @NYSDOTHV Any update on when this will reopen? Also, are you going to fix the signs stating that it's closed? And maybe alert @waze that it's still closed? They routed me there the other day and wah wah, still closed. Thanks.

• 
  Big Belly (@_ImJustTy) reported 50 minutes ago

  The @waze app has become a PAIN in my *** over these past few months. At first I thought it may have been a CarPlay issue or due to my data, but it’s not! It doesn’t update in a timely fashion like it used to and I end up having to bust a u turn because I’ve gone the wrong way

• 
  Vic Romano (@GenoakPod) reported 55 minutes ago

  @Cappo1Capponi @Biffdon That’s what I never could get with on Waze. How can I document these things like cars broken down, police etc when I am driving.

• 
  🇩🇲 🍉 She Who Resembles God🪞 (@TiPassie) reported 58 minutes ago

  If I say I don't use Waze because it's Israeli made then I'm pretentious/too woke/ doing too much. If I say I prefer a different app then it's no problem. I am so tired of the apathy of the world and it being a social sin to give a damn