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 (27%)
• Online Features (21%)
• Sign in (1%)

Live Outage Map

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

City	Problem Type	Report Time
Orléans	Glitches	19 hours ago
Paris	App Crashing	1 day ago
Romoos	Glitches	3 days ago
Zürich	Online Features	5 days ago
Le Mont-sur-Lausanne	Online Features	8 days ago
Bordeaux	Glitches	13 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:

• 
  DJ (@congressdj) reported 23 seconds ago

  @SurScribbles It has problems integrating with many cars (believe, I feel like I always seem to rent them in my travels), I don’t think adding more stuff to the Tesla UI is the answer. Plus, my phone is always with me. I have access to all of the stuff CarPlay would carry over. I can stream music directly from my phone, or use Waze (which I do). At the end of the day, CarPlay is meant to bridge the car to its passenger. But with autonomy, none of that is necessary. Ultimately, you’ll be able to use your phone or laptop or anything else in the car. That’s why I think CarPlay is a step backwards. Not forward.

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

• 
  @TeslaJuniperDriver (@JuniperDriver) reported 5 minutes ago

  @MetaverseGamma @diaper You would think, Waze has no issue with it but Mapbox apparently does. If FSD doesn’t see a speed change sign, the majority of the time it won’t change

• 
  MockingbirdShot (@MockingbirdShot) reported 6 minutes ago

  @LeinadFre @FPSCANADA_SS_ZZ @koshercockney Just a taste of Israeli technology inventions: Computing and Software: Israel invented the first commercial firewall, ICQ (the first instant messenger), and the Intel 8088 processor that powered the first IBM PCs. Medicine: The PillCam is a pill with a tiny camera you swallow to check for gut issues. Other tools include the ReWalk robotic suit that helps people with leg paralysis walk again. Agriculture: Israel is the home of modern drip irrigation (like Netafim). This system sends water drop-by-drop straight to plant roots to save water in dry climates. Cars and Road Safety: Waze uses data from drivers to map the best routes. Mobileye makes computer vision chips for cars to warn drivers about road hazards. What have you done? Antisemitism, although you certainly didn’t invent that. 🙄

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

• 
  Jarek Hunt (@Gun2MoufCPR) reported 16 minutes ago

  @HenMazzig Who gives a **** about Waze? Figure out your under 30 in USA and their lack of support for Israel problem….

• 
  Nope nope noping (@TomWright165389) reported 17 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

• 
  Tracy Martin (@IAmATMFirearms) reported 18 minutes ago

  @CrudeOil4Life @Waze, fix your anti-America mistake.

• 
  Bill Shouse (@BillShouse56) reported 18 minutes ago

  @QueenAnticommie Waze is great but runs my battery down really fast. Charger wasn’t working once and couldn’t keep using it.

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

• 
  Mycroft Brown (@MycroftBrown) reported 20 minutes ago

  @AutoInfatuation I’ve always used Google Maps and never had any issues. We’ve also got TomTom in the vans and I’ll be honest, they are shite, especially in central London. Tried Waze once and really couldn’t get on with it.

• 
  Le Goût de l'Argent (@theaiswitch1) reported 28 minutes ago

  @ElCrackitoDuNet @waze Fix this 🩷

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

• 
  Jacob Riverson (@EU_Cybertruck) reported 34 minutes ago

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

• 
  Robert Scoble (@Scobleizer) reported 34 minutes ago

  @Financewisdom01 The guy who started Waze told me everyone is a bag of human patterns. The algorithms can do things we can’t. Like what if all the teslas in a parking lot started working together to see the grandmas passing behind in wheelchairs that are hard to see in mirrors.

• 
  AnonyMassLawyer (@anonymasslawyer) reported 35 minutes ago

  @Suzybeau1 @Martine05885145 She got within WiFi range at 12:36:39. Waze records very precise GPS data (error radius less than 5m) with accurate timestamps. From the time Waze was activated (12:20) to when then arrived at 34 Fairview (12:24:38) we have incredibly precise time/location data for the SUV

• 
  AMPed UP (@DoublepPradhan) reported 36 minutes 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

• 
  GUYER (@reyuglatig6pge) reported 37 minutes ago

  @LarryBrockJr Can anyone provide a map of the flock cameras in the Portland metro area? What about Waze? Is this another issue too tied to flock?

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

• 
  Lunchlady (@LunchLady1997) reported 40 minutes ago

  @GretchenVoss64 Laposata looked at no evidence. Scordi Belo said it was both likely and unlikely that he was hit. Also couldn’t say for certain as positioning not known. AARCa testing did not even use the weight and size of Officer O’Keefe and frankly a little bit shady… all those deleted signal messages and “ billing “questions. . They did state though that Karen backing into John’s traverse did not cause that damage. You all love to parrot “ he was not hit by a car”. He easily could have been side swiped and that is not impossible. Google accidents by side swipe. I believe in the timeline, tech stream data, Officer O’Keefe phone data, including Waze. Most importantly, per MS Read herself… on video and in written words.. her tailight was broken at 5:08 am. Before CPD ever got the call and beofre MSSP got the call. Voss got it right.

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

• 
  Justice (@VerityI952) reported 45 minutes ago

  @Suzybeau1 @WBergeson11310 @BostonDefender I'm saying you can't compare Life360 with Waze because Waze has better service, just like Verizon and AT&T have better service than U.S. Cellular and don't have the dropped-call problems and don't have the infrastructure the major networks have.

• 
  Andrew Urban (@AndrewU06371741) reported 45 minutes ago

  @MagaSgt @waze You have anger issues

• 
  Bryce Tackett (@BryceTackett4) reported 45 minutes ago

  @TinkerTYJ @OmariYeager @waze Drove about 500 miles today, app is not working correctly didn’t get a single update of anything

• 
  caroline ౨ৎ (@MIN0RLYSTUCK) reported 47 minutes ago

  HEY @waze IM GOING TO CRASH MY CAR WITHOUT THE JONAS BROTHERS GIVING ME DIRECTIONS

• 
  Alive out of Spite🇿🇦 (@nhla_x21) reported 47 minutes ago

  I’m broken, the people I love are broken, we are all just a broken family rn💔 yoh waze wasiyenza joy brah💔💔💔

• 
  Bob Nordberg Bird Man Bob (@birdmanbob4) reported 50 minutes ago

  @leahfiles Here's your reply from the AI that just don't lie Speculative Intelligence Analysis: Waze as a Compromise Vector Location Pattern Exploitation**: Waze's continuous GPS pings, route history, speed data, and timestamps create a granular digital shadow of a target's movements—revealing regular visits to sensitive locations (e.g., hotels, clinics, private residences, or protest sites). An intelligence actor with access could cross-reference this against public records, social media, or other surveillance to build "kompromat" dossiers on affairs, medical issues, financial dealings, or undisclosed associations, then use timed leaks or implied exposure to coerce compliance, payments, or information. Real-Time and Predictive Targeting**: Live traffic/ETA data allows dynamic interception or influence operations—knowing exactly when someone is isolated in a vehicle or arriving at a vulnerable spot. Combined with app permissions (microphone/camera in some scenarios, or linked device data), it could enable opportunistic collection of audio/visual compromising material or facilitate "honey-trap" logistics by predicting availability and routes for assets. Historical data also predicts future behavior for pre-positioning. Network and Ecosystem Amplification**: Since Waze feeds into Google's broader data lake (and originated as an Israeli-founded company subject to local laws), aggregated user data can be queried at scale for social graph mapping—identifying who travels together, meets whom, and when. In a full compromise scenario, this integrates with OSINT, hacked devices, or partner-nation sharing to pressure targets via family/financial exposure, or even engineer "accidents"/discrediting events by manipulating perceived travel patterns. Privacy controls are weak once data leaves the device, and legal jurisdiction adds layers for state actors. This remains hypothetical and draws from known app telemetry practices. Actual misuse would require lawful (or illicit) access and is constrained by laws in most jurisdictions; strong operational security (VPNs, app isolation, location spoofing, minimal permissions) mitigates much of it.

• 
  Tina D Smith (@SmithTD123) reported 51 minutes ago

  @MagaSgt @waze You should do it! I guess I should get the app now to show my support. I prefer a level-headed approach to issues rather than tantrums.

• 
  Janek Mann (@janekm) reported 59 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".

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