Technology

Waymo Pauses San Francisco Robotaxis After Flooded Streets

Martin HollowayPublished just now3 min readBased on 1 source
Reading level
Waymo Pauses San Francisco Robotaxis After Flooded Streets
Photo by Mliu92 / CC BY-SA 3.0

Waymo has temporarily paused its robotaxi service in San Francisco because of flooding on some streets. Engadget reported the pause on 18 November 2026.

The rider app tells San Francisco customers "we're paused for now due to weather," and says service will resume "when road conditions improve and the forecast looks clear." The message frames the suspension as weather-driven and conditional, with no fixed restart time.

The pause follows reports that Waymo robotaxis were blocking intersections in San Francisco because the vehicles would not drive through standing water. A vehicle that declines to enter a flooded lane is a different failure from one that enters it, but both leave the vehicle immobile in a live traffic environment. Both push the problem onto other road users and the city's emergency response.

The weather pause came a day after the California DMV restricted Waymo from operating on the state's freeways. Waymo responded by pulling its robotaxis off freeways in all of its markets. The two actions are separate regulatory and operational events, but they landed within days of each other, and both concern the limits of the service's driving envelope, meaning the range of roads and conditions the system has been validated to handle.

San Francisco is not the first city where Waymo has halted service over a fault in its operating domain. In December 2025, the company paused service in San Francisco after a power outage left its self-driving cars stranded at intersections. That incident involved infrastructure failure rather than the vehicles' own judgment, and it was resolved on that basis.

Flooding has been a recurring thread. In May, Waymo recalled nearly 4,000 vehicles and paused service after a robotaxi drove into a flooded road in San Antonio. Waymo then issued a software update covering flooded-road driving. The company later paused service in Atlanta after a Waymo again drove into a flooded street. The sequence shows the same class of event producing opposite behaviors in different cities: entering water in one case, refusing it in another. Both point to the same gap, which is how the vehicle classifies standing water, its depth, and whether a road surface it cannot fully see is drivable.

The broader context here is fleet-level policy. A single car making a conservative call is a local problem. Dozens of cars making the same call across a dense urban grid during a storm become a traffic problem, and the operator must decide whether to stop dispatching, geofence affected zones, or accept lower utilization. The 18 November pause is a blunt instrument, and the rider message makes clear that Waymo is treating weather as a gating condition for the service rather than a per-trip decision.

In my view, the more useful question for the industry is whether the remedy is a better water-detection model, a more explicit operational rule for flooded roads, or a combination of the two with human-in-the-loop escalation. The software update after the San Antonio recall addressed flooded-road driving, yet the Atlanta incident suggests a software change alone did not settle the behavior across markets. Whatever the mechanism, evaluation has to cover standing water at varying depths, partially submerged signage, and the transition between dry and flooded pavement, since those are the cases behind the reported incidents.

The optimistic reading is also available. A robotaxi that stops when conditions exceed its validated envelope is doing what a safety-case design is meant to do, and a service that pauses and states a restart condition is easier for riders to understand than one that fails silently. The harder work is widening that envelope so the next storm does not require a pause at all. Autonomous fleets have to earn that capability one weather event at a time.