Waymo pauses four cities as floods expose gaps in robotaxi edge-case fixes

Waymo confirmed the Atlanta pause to TechCrunch, which reported it on 21 May 2026, along with a halt in San Antonio, Texas. Late on Thursday the company added Dallas and Houston, citing forecast severe weather across Texas.

Bloomberg News had the Dallas and Houston expansion first. The Atlanta vehicle was unoccupied. It encountered a flooded road and stopped, the company said in a statement: "Safety is Waymo's top priority, both for our riders and everyone we share the road with. During a period of intense rain yesterday in Atlanta, an unoccupied Waymo vehicle encountered a flooded road and stopped." Local news reports spotted the car driving through the flooded street before it stalled, and Waymo told TechCrunch the vehicle was recovered and removed.

The timeline makes this more than a weather story. Waymo issued a software recall for flooded-road behavior the previous week. In documents released by the National Highway Traffic Safety Administration, the company said it had not finished a "final remedy" and instead pushed an update placing "restrictions at times and in locations where there is an elevated risk of encountering a flooded, higher-speed roadway."

A warning gap the company flagged itself

Waymo told TechCrunch the Atlanta storm dropped so much rain that flooding was under way before the National Weather Service had issued any flash flood warning, watch or advisory. Those alerts, the company said, are part of a wider set of signals its vehicles use to prepare for bad weather.

NHTSA said it was aware of the incident and in communication with Waymo: "NHTSA is aware of this incident, is in communication with Waymo, and will take appropriate action if necessary." A pattern predates the rain. When the public noticed Waymo robotaxis illegally passing stopped school buses last year, the company shipped a fix. The fleet kept making the same maneuvers anyway. That behavior now sits at the center of one of two active investigation sets into Waymo, run by NHTSA and the National Transportation Safety Board.

Documents are already moving. Waymo produced a batch for NHTSA, all of it redacted to the public, and on 15 May the regulator sent a second request because the first response "necessitates that [NHTSA] receive further data and information." The other investigation set covers a 23 January incident in Santa Monica, California, where a Waymo robotaxi struck a child. Waymo has said the car braked to around six miles per hour before impact and that the child suffered minor injuries.

Why the fixes keep arriving late

The underlying problem is not unique to Waymo. Robotaxi software has to handle rare, messy scenarios, and the industry is shifting from rules-based driving toward reinforcement learning that feeds on real-world mileage. As Uber's chief technology officer Praveen Neppalli Naga put it to TechCrunch in January, when the company launched its AV Labs data division, the companies that want driving data most are the ones already collecting a lot of it.

Waymo says its vehicles have driven more than 170 million miles autonomously and claims a 13x reduction in serious-injury-or-worse crashes compared with human drivers. It is also expanding hard, with plans to launch in more than 20 cities this year including London and Tokyo. High mileage and aggressive expansion are exactly the conditions that surface the edge cases a recall is meant to close.

Flooded roads are one. Closed highway construction zones are another. On 18 June, Waymo recalled nearly 4,000 robotaxis to keep them off freeways after at least 13 instances of vehicles entering highway sections closed for construction: six in Phoenix in April, seven in San Francisco in May. The company pulled its cars from all highways on 19 May, and a fix was "currently under development," per its NHTSA filings. That recall, the sixth Waymo has issued, followed the flooded-road recall in May and a December action over school-bus behavior.