QWE AI Academy You opened Uber in Atlanta yesterday, toggled on the Waymo preference like usual, and got a regular driver. Did you do something wrong? No – Waymo paused Atlanta service on May 21, 2026, after one of its robotaxis drove into a flooded street and sat there for about an hour. TechCrunch reported it first; the car was empty, recovered without incident, but service is offline until Waymo ships another fix.
This is the rider side of that situation. How to tell if Waymo is actually paused, how to keep your fallback working, and how to read the recall language well enough to judge whether the service is genuinely fixed when it comes back.
The scenario this article solves
You’re a Buckhead resident who’s been using Waymo on Uber for a few months. No awkward small talk, clean car, price matches a normal UberX. Then this week the matches stop. Headlines say something about flooding. You want to know: is it me, the weather, or a citywide pause? And what do you do right now if you need to reach Midtown in 20 minutes?
That’s the question. Here’s what you need.
What just happened – and the part news coverage skips
Short version: a Waymo robotaxi drove through a flooded Atlanta street, got stuck for about an hour, was recovered, and Waymo paused Atlanta service – the same call it had already made in San Antonio after a separate flooding incident there.
The interesting part: the interim patch wasn’t enough. Back in late April, a flooding incident in San Antonio prompted a voluntary software recall filed April 30, covering 3,791 vehicles on Waymo’s fifth- and sixth-generation Automated Driving Systems. Per the NHTSA letter, the software “may allow the vehicle to slow and then drive into standing water on higher speed roadways.” Waymo pushed an interim update but is still developing the final fix. Atlanta happened anyway. So the pause isn’t a separate problem – it’s proof the interim patch has limits.
And here’s a detail worth sitting with: the Atlanta street in the video didn’t look like a “higher-speed roadway” by any normal reading. The recall language is tight around one failure mode. The real-world failure surface appears wider. That gap matters when you’re deciding whether to ride again after the service resumes.
How to check if Waymo is running in your city
Atlanta riders hit a specific snag: Waymo in Atlanta is only available through the Uber app (as of May 2026), not the Waymo standalone app. In direct-service cities like San Francisco, Waymo’s own app surfaces a notification – “Service temporarily paused due to National Weather Service flash flood warning” – right on the home screen. Atlanta riders never see that.
So the checklist looks different here:
- Open Uber and request an eligible ride from inside the service area (Downtown to Buckhead to Capitol View – 65 square miles total, per the Uber Atlanta blog).
- Go to Account → Settings → Ride Preferences → Autonomous Vehicles and confirm Waymo is toggled on.
- Request an UberX, Uber Comfort, or Uber Comfort Electric – those are the eligible tiers.
- If you get human-driver matches for 3-4 attempts in good coverage areas during off-peak hours, service is likely paused.
- Cross-check with a quick news search for “Waymo Atlanta” – pauses get reported within hours.
One useful filter: Waymo rides aren’t available to or from Hartsfield-Jackson International Airport, pause or no pause. Don’t use an airport trip as a status test – it’ll never match a Waymo regardless.
What to do during a pause
Leave the Waymo preference toggled on. Request your ride normally. Uber falls back to a human driver without any action on your part, and you won’t lose anything for having the preference active.
Watch out: toggling the Waymo preference off during a pause seems like housekeeping, but it’s how people miss the return window. When service resumes – usually within days to a few weeks – you want to already be in the matching pool. Toggle off, forget to toggle back, and you’re manually opting back in whenever you remember.
Pricing and payment stay identical to a normal Uber. The only thing a pause costs you is the autonomous option – and if you liked the all-electric vehicle and the quiet, that’s a real difference, not a minor one.
Reading the recall language
This is the part worth learning if you plan to ride any robotaxi service in the next year. Recall language is engineered to be narrow. The NHTSA wording for this recall:
"The software may allow the vehicle to slow
and then drive into standing water on higher
speed roadways."Three things to notice. “May allow” – not “causes.” “Higher speed roadways” – not all roads. “Standing water” – not flowing water, not flash floods, not partially flooded intersections. Every qualifier shrinks the scope.
Now compare that to Atlanta: a non-highway intersection, during a storm that – turns out – flooded faster than the National Weather Service could issue any warning, watch, or advisory. Waymo told TechCrunch the flooding started before NWS alerts went out, and NWS timing is one of the signals Waymo uses to prepare its fleet for bad weather. The mismatch is specific: the recall addresses one failure mode on high-speed roads; the Atlanta failure happened on a normal street, faster than the warning system could respond.
What does “fixed” actually mean for software that failed in a scenario the recall didn’t explicitly cover? That’s not a rhetorical question. When service comes back online, it’s worth asking whether the new patch addresses the Atlanta-style failure – storm outpacing official alerts on a regular street – or only the San Antonio-style failure the recall was written around.
Honest limitations right now
Five things to know before your next ride (as of May 2026):
| Limitation | What it means for you |
|---|---|
| Weather pauses can be sudden | A trip you requested may switch to a human driver mid-queue if conditions shift |
| 7-minute boarding window | The car leaves if you’re slow – less forgiving than a human driver waiting at the curb |
| Freeway rides paused separately | Waymo also paused freeway operations this week due to construction-zone struggles; trips routing via highway may fall back to surface streets or not match at all |
| Service area is fixed | Both pickup and dropoff must be inside the 65-square-mile zone |
| NWS-dependent weather logic | If a storm outpaces the official warning system, the fleet may not know to avoid it – the Atlanta incident showed this gap in practice |
Waymo confirmed the Atlanta vehicle was unoccupied and was recovered without incident. The risk surface is real but specific to weather-edge scenarios. For normal Atlanta conditions, the case for riding hasn’t changed – the service operates 24 hours a day and the fleet has logged millions of miles. What changed is that you now know one exact condition where the safety logic can lag.
Your next move
Open Uber. Account → Settings → Ride Preferences → Autonomous Vehicles. Make sure Waymo is toggled on and leave it there.
Bookmark the NHTSA recalls portal – when Waymo files the final remedy (the April 30 recall still lists it as pending as of this writing), it’ll appear there before most news outlets pick it up. That’s your clearest signal that the fix is actually complete, not just interim.
Atlanta service will return. The pattern from other pauses is days to a few weeks. When it does, you’ll be in the match pool from minute one – and you’ll know exactly what was and wasn’t fixed.
FAQ
How long will the Atlanta pause last?
Waymo hasn’t said. San Antonio’s pause has already stretched into weeks. Plan for at least that.
Can I still take Waymo somewhere else right now?
Yes – only Atlanta, San Antonio, and freeway routes are affected as of May 21, 2026. Phoenix, San Francisco, Los Angeles, and other direct-service cities are running on the Waymo app. Those cities show in-app pause notifications tied to National Weather Service flash flood warnings, which is a much cleaner status signal than what Atlanta riders have. In Atlanta, you’re inferring from match behavior, not a push notification – which is why the checklist in this guide matters.
Is it actually less safe to ride a Waymo right now?
The Atlanta car was empty when it got stuck, and Waymo confirmed it was recovered without incident. The flooding risk is specific: storms that outpace NWS alert timing, on roads outside the recall’s “higher-speed roadway” scope. That’s a real gap in the current software. For ordinary Atlanta weather – no active flash flood conditions – the safety picture is unchanged from before this week. The service is paused precisely because Waymo is treating the gap seriously, not because the whole system is broken.