Why did Waymo suspend robotaxi service after floods?

Waymo paused robotaxi service across multiple cities after vehicles drove into flooded or rain-impacted roads, and the company said a software update wasn’t able to handle the conditions.

In one incident, Waymo suspended service in Atlanta after videos showed robotaxis stopped on swamped streets. In subsequent updates, the company extended pauses to additional locations as it worked on fixes, including conditions involving heavy rain, construction zones, and flooded roadways.

The key operational takeaway is that the problem appears environment-specific and tied to real-world edge cases: heavy water on roadways can reduce visibility, alter road markings, and change how obstacles and lane boundaries appear to the system. Waymo’s response—pause service and push software improvements—shows a safety-first approach when the fleet-wide patch doesn’t perform reliably.

Waymo’s pauses also highlight a tension in deployment: even when autonomous driving stacks work well in normal conditions, “low-frequency, high-impact” scenarios like flooding can produce failures that require time to diagnose and patch. The company’s rollout strategy involves updating the fleet and then verifying that the change improves performance across varied city infrastructure.

Net impact: for cities and regulators, pauses act as a signal that safety checks must account for weather and temporary road changes. For operators and users, it means service availability can change quickly as software gets updated and validated.