Another weather setback for robotaxis
Waymo has suspended its robotaxi service in Atlanta after one of its vehicles drove into a flooded street and became stuck during heavy rain, underscoring how difficult severe weather remains for autonomous driving systems. The company said the vehicle was unoccupied when it encountered the flooded road and stopped. Local reports cited by TechCrunch said it remained stranded for about an hour before being recovered.
The Atlanta pause follows a similar suspension in San Antonio, meaning Waymo has now halted service in two cities while it tries to address how its vehicles detect and avoid flooded roadways. The problem is not new. It was serious enough that Waymo issued a software recall last week, but the latest incident suggests the interim fix was not sufficient.
Why the previous fix did not hold
According to documents released by the National Highway Traffic Safety Administration, Waymo acknowledged that it had not yet completed a final remedy when it rolled out its recent software update. Instead, the company imposed restrictions in times and places with elevated risk of flooding on higher-speed roads. That mitigation was meant to reduce exposure while a fuller solution was developed.
The Atlanta event appears to show the limits of that approach. Waymo told TechCrunch the storm created flooding before the National Weather Service had issued a flash flood warning, watch or advisory. Those alerts are part of the larger set of signals the company uses to prepare vehicles for poor weather. In other words, one layer of Waymo’s weather-risk framework depends in part on external warning systems, and in this case the flooding developed ahead of those triggers.
That does not mean the vehicles rely only on weather alerts. But it does suggest the combined system of forecasts, warnings, operational restrictions and onboard behavior still has important gaps when road conditions change faster than the broader alert infrastructure.
A recurring pattern in autonomous vehicle deployment
The flooding issue also fits a broader pattern that has followed Waymo’s rollout. In past cases, the company has responded to problematic driving behavior with software changes, only to see similar issues continue afterward. TechCrunch noted that Waymo previously introduced a fix aimed at preventing robotaxis from illegally passing stopped school buses, yet vehicles were later still observed making unlawful maneuvers around them.
That history matters because it highlights a persistent challenge in autonomous driving: edge cases are not isolated events that disappear once identified. Real-world driving conditions are messy, variable and highly local. A patch that addresses one failure mode can reduce risk without eliminating it, especially when the system must interpret weather, infrastructure, traffic behavior and changing street conditions in real time.
Flooded roads are particularly difficult because they combine perception, prediction and operational judgment. A vehicle needs to recognize the hazard, estimate its severity, determine whether it is passable, and act conservatively enough to avoid getting trapped or creating danger. In urban storm conditions, that decision space can change block by block and minute by minute.
Regulatory pressure is building
Waymo’s weather issues are arriving alongside active federal scrutiny on other fronts. Both the NHTSA and the National Transportation Safety Board are investigating the company’s conduct around stopped school buses. On May 15, the NHTSA sent Waymo a second request for documents after concluding that the company’s earlier response required more information.
Separate investigations from the NHTSA and NTSB are also looking into a January 23 incident in Santa Monica, California, where a Waymo robotaxi struck a child after braking to around six miles per hour, according to the company’s prior account cited by TechCrunch. Those investigations are distinct from the flooding issue, but together they intensify the broader question of how quickly autonomous systems can be scaled while public authorities are still probing multiple categories of risk.
What the Atlanta pause signals
The immediate takeaway is straightforward: Waymo does not yet have a robust answer for heavy rain and sudden urban flooding, and it is choosing to suspend operations rather than continue service in conditions it cannot confidently manage. That is the prudent move from a safety perspective. It is also an admission that robotaxi reliability is still constrained by environmental complexity.
For the wider autonomous vehicle industry, the Atlanta suspension is a reminder that deployment progress is not measured only by miles driven or markets entered. It also depends on how systems perform in the hardest, least predictable conditions. Weather has long been one of the most stubborn barriers in self-driving development. This week’s incident shows that barrier remains firmly in place.
This article is based on reporting by TechCrunch. Read the original article.
Originally published on techcrunch.com
