Why did Waymo pause robotaxi service in floods?

Waymo paused robotaxi service after a failed software fix

Waymo temporarily suspended robotaxi operations across multiple US cities after its cars continued to struggle in heavy rain and flooded roads, even after an earlier software patch was rolled out to the full fleet.

In Atlanta, the change followed a patch that Waymo had pushed to its entire fleet less than two weeks earlier; the patch did not prevent cars from getting stuck when conditions worsened. As a result, Waymo shut down service in five cities and later expanded pauses further, including a move to halt service on freeways as robotaxis encountered difficulty in construction zones.

The pattern across the reports is consistent: Waymo detected that the deployed software changes were not adequately handling real-world flood and congestion scenarios, so it pulled service to limit safety risk and investigate.

What this means for driverless rollout

• Software updates aren’t enough on edge cases: flood conditions and rapidly changing road layouts appear to be difficult to cover with a single fleet-wide update.
• City-by-city pauses reduce exposure while debugging: Waymo’s approach suggests it is using localized shutdowns to control risk while improving perception and routing behavior.
• Construction and weather interact: the freeway-related suspension points to scenarios where road work and complex traffic patterns may compound the challenge.

For riders, these pauses translate into interrupted service. For the broader industry, the episode is a reminder that autonomy deployments depend on continuous validation under harsh and variable conditions—not just improvements in controlled testing.