Safety & Security

Waymo pauses San Francisco robotaxis after flooding traps vehicles

Waymo paused San Francisco robotaxis around 11 a.m. after flooding stalled vehicles, downtown rain measured about 2.11 inches, and a prior flood incident prompted a nearly 4,000-vehicle recall.

Waymo pauses service in San Francisco after robotaxis get stuck on flooded streets
Waymo pauses service in San Francisco after robotaxis get stuck on flooded streetsPexels / pixabay
By Marcus Bennett5 min read

By Marcus Bennett

Waymo paused its San Francisco robotaxi service around 11 a.m. local time on November 18, 2026, according to James Reichert's X post, after about 2.11 inches of downtown rain and incidents involving blocked, flooded intersections.

Reichert wrote: "Waymo paused its Bay Area robotaxi service around 11 AM local time, saying it will return when roads improve." His post also listed about 2.11 inches of rain for downtown San Francisco.

Mahmood separately announced the pause in an X post. District 5 Supervisor Bilal Mahmood's post described flooding as the reason for the interruption. Engadget described the disruption as affecting San Francisco only, although Reichert's wording referred to Bay Area service.

The Waymo app gave riders the reason for the interruption and the threshold for ending it. It said: "we're paused for now due to weather." Service would resume "when road conditions improve and the forecast looks clear."

What happened on flooded streets?

Engadget cited videos posted on X that showed how the robotaxis affected traffic before the pause:

  • One robotaxi stopped in the middle of a flooded crosswalk. Cars had to drive around the stationary vehicle.
  • A second robotaxi idled in the middle of a road. The vehicle instructed its rider to stay inside.

Those scenes established the immediate problem behind the shutdown. The robotaxis, autonomous ride-hailing vehicles, remained in travel lanes or intersections while water covered parts of the roadway. The videos did not establish why each vehicle stopped. The report said they were "seemingly unable (or unwilling) to drive through water."

The cited videos turned a weather hazard into a traffic-management problem. A vehicle that remains in a crosswalk or travel lane removes usable road space even when it does not enter deeper water. In both recordings, other drivers had to route around a stationary robotaxi.

Engadget reported that San Francisco was dealing with heavy rain and flooding as the region headed into what forecasters expected could be a record El Niño winter. Reichert's accompanying post described the conditions as an atmospheric river, a storm system carrying concentrated moisture.

Engadget said it had asked Waymo to comment on the stalled robotaxis and its response to San Francisco's weather. Waymo had not responded before publication, leaving the app notice, Mahmood's post and the videos as the available account.

How has Waymo handled flooding before?

Before the San Francisco weather pause, Waymo's recent operating history included a power-related shutdown, a recall of nearly 4,000 vehicles and two flood-related service pauses.

  • In December 2025, Waymo temporarily paused San Francisco service after a power outage. Engadget reported similar instances of robotaxis blocking city streets during that shutdown.
  • In May, the company 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 to address that flooding issue.
  • The company later paused service in Atlanta after another robotaxi drove into a flooded street.

The chronology matters because the same type of weather hazard has produced different operating failures. San Antonio and Atlanta involved vehicles entering flooded roads. San Francisco involved vehicles remaining in intersections and forcing cars around them. In each city, a service pause followed the incident.

Engadget wrote: "The fact that the company is dealing with these issues in San Francisco suggests solving this problem might be more complicated than it appears." The May software update addressed one flooding episode, but the later Atlanta incident showed that flood-related failures remained possible after that correction.

That sequence spans three responses to separate problems: a vehicle-level software correction, city service pauses and a market-wide freeway withdrawal. The San Francisco stop now tests the first layer again under a different failure: blockage rather than entry into water.

For Waymo, the San Francisco recordings show that detecting water is only one part of the operating problem. A robotaxi must also decide whether to cross it, where to stop and how to avoid obstructing traffic when road conditions deteriorate. Remaining in place can affect riders and other drivers even without a collision.

What does the freeway restriction change?

The flooding pause affected San Francisco only. One day earlier, the California DMV (Department of Motor Vehicles) restricted Waymo from the state's freeways. Waymo then pulled its robotaxis off freeways in all of its markets, not only California.

The actions occurred within 24 hours but addressed separate operating constraints. The DMV restriction removed freeway access. The weather pause removed service from one city while flooding blocked streets. Restoring San Francisco pickups would not restore the company's freeway operations.

That sequence gives the flooding pause broader regulatory and operational significance. Waymo was already narrowing where its vehicles could operate after a state agency restricted freeway access. The rain forced another contraction in its service footprint, this time in San Francisco.

The immediate stakes are operational reliability. According to the report, riders encountered stopped vehicles in lanes and intersections and an app message directing them to wait. Within the same 24-hour period, Waymo also reduced its broader operating footprint through the freeway withdrawal.

When will service return, and what gets tested?

Waymo set conditions for restarting, not a firm restart time. Its app ties the return to improving roads and a clear forecast. Reichert's 11 AM post likewise said the pause would end when roads improve.

The next test will be whether the robotaxis avoid standing water and clear intersections once conditions improve. Engadget had not reported a further software change, a revised driving rule or a specific restart hour before publication. The May update and the later Atlanta shutdown leave that test unresolved.

For riders, the Waymo app provides a weather threshold but no stated restart estimate. That leaves the restart dependent on local road conditions and the forecast rather than a company timetable, with the app serving as the rider's status channel.

The near-term benchmark is San Francisco: whether another rain event can leave vehicles blocking intersections rather than stopping clear of traffic lanes. The broader benchmark is consistency across cities. December 2025 offers a separate warning, because a power outage produced blocked streets and another temporary San Francisco shutdown.

Service will resume when San Francisco road conditions and the forecast meet Waymo's stated threshold. The next restart will test whether the company can apply one operating rule across San Antonio, Atlanta and San Francisco rather than treating floodwater as a city-specific problem.

Source: engadget.com

Share this article:

More from Marcus Bennett

Marcus Bennett

Show full bio

Senior reporter covering companies, deals and strategy in artificial intelligence and machine learning at AI In Context.

745 articles

Related articles

  1. California DMV Bans Waymo From Freeways, Citing 'Imminent Hazard'
  2. California DMV suspends Waymo freeway rides after construction zone incursions
  3. California Bans Waymo From Every State Freeway Over Construction-Zone Incursions
  4. Mercedes tests point-to-point assist on San Francisco streets
  5. Tesla expands robotaxi service to San Antonio at 5 a.m.

« Previous articleNext article »