Waze 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:

• 
  Ray, Babysitter of Chaos রশ্মি (@TheRealStanRay) reported 2 minutes ago

  Wow you’re slow. It’s based on Spiderman sightings. People input it like reporting a road block or car on the side of the road on Waze.

• 
  Monty Simmons (@simmo71084) reported 4 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.

• 
  Edgars Zīverts (@edziverts) reported 6 minutes ago

  @ChinaEV_Eng_Lif Try coming to Eastern Europe; Tesla cannot fix its maps for 2+ years. Waze really is the gold standard; too bad there is no native app.

• 
  The Joker 🇿🇦 (@Sir_The_Joker) reported 7 minutes ago

  @MbalulaFikile Waze wawu msoonooh Mbalula. I mean you act as if you don't live in South Africa and you are not part of the big problem! We have a big illegal immigrants problem that you contributed to while you were a minister of police. You did fokol... Uyanyanyisa bra!!!

• 
  Lunchlady (@LunchLady1997) reported 14 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.

• 
  · (@Thejacobdean) reported 21 minutes ago

  @NotATeslaApp No they should have FSD automatically slow down based off the Waze/apple/google police data though. I have 2 tickets in FSD mad max

• 
  Norman **** - Founder @ Lead Oracle AI (@NormanWangTech) reported 24 minutes ago

  🚨 99% of local SEO advice is noise, and most people focus on the wrong things. Agencies sell you on content calendars, blog posts, backlink packages, and social media management. None of it moves the needle for a local business. Here's what actually does: 1. Google Business Profile This is where local search is won or lost. When someone searches "plumber near me" or "dentist near me," they are not going to your website first. They are looking at the Maps pack — and the Maps pack is powered entirely by your GBP. The businesses that rank there have: → Every service listed as a category → Professional photos (updated regularly) → 100+ reviews with a 4.7 or higher rating → Posts going up weekly → NAP (name, address, phone number) data that matches everywhere on the web Most local businesses have a half-filled profile from 2019 and wonder why they can't rank. 2. Website structure Not blogs. Not word count. Structure. Google needs to understand what you do, where you do it, and who you serve. That means: → A dedicated page for each service (not one "Services" page that lists everything) → City and neighborhood signals embedded in the right places → Fast load times and mobile-first design → Schema markup so search engines can read your data correctly Your website is not a brochure. It's a signal to Google that your business is exactly what someone in your area is searching for. 3. Citations Citations are every place your business name, address, and phone number appear online — Google, Yelp, Apple Maps, Bing, Alexa, Waze, Yelp, Facebook, and 40+ other directories. When those listings are consistent and accurate, Google trusts you more. When they're inconsistent or missing, your rankings suffer — and customers can't find you on voice assistants, GPS, or AI search. Most local businesses have never touched their citations. Half of them have wrong information sitting on directories they don't even know exist. That's the entire playbook. GBP → you show up. Website structure → Google understands you. Citations → Google trusts you. Everything else local agencies sell you is secondary to getting these three right. Fix the fundamentals. The rankings follow. Don't overcomplicate it.

• 
  MB (@paxangloceltae) reported 26 minutes ago

  @TomWright165389 Waze died on us within about 20 mins of leaving the M25 for the M1. Google Maps also screwed. Apple Maps remarkably seems to be working even on 1 bar of 5G - and even when the phones go onto SOS or satellite mode. Still, ridiculous that reception is so poor.

• 
  DJ (@congressdj) reported 28 minutes ago

  @phibetakitten Don’t get me wrong. It will reach the closed road and detour just fine. The problem was that so many roads were closed, it kept mapping to the closed roads and then doing detours. It was almost endless at one point. Using Waze I was able to navigate it in 1/10 the time

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

• 
  Washington State Ferries (@wsferries) reported 34 minutes ago

  @SQZA55 @KIRO7Seattle Not when the boarding pass is activated. We have been working with GPS apps, but so far only Waze has changed their routing.

• 
  Watanabe (@EzidLee) reported 35 minutes ago

  @DevinOlsenn I have no problem with mine. Waze? WTF is that.

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

• 
  Chaos Theory (@Samwyri) reported 40 minutes ago

  You people don’t rate Waze. Any day, anytime. Only problem is tech by genocidaires and spawns of Satan. Active collaboration.