Waymo's rapid expansion hit a significant speed bump this month as weather and infrastructure challenges forced the robotaxi operator to pause service in multiple cities, exposing the gap between autonomous driving hype and real-world operational complexity. The company recalled its entire fleet of 3,791 vehicles in April after two separate flooding incidents in San Antonio, then paused operations in six cities in May following additional weather-related failures and a reported freeway incident involving highway construction zones.

What Caused Waymo's Recent Service Pauses?

The trouble started in San Antonio on April 20, when an unoccupied Waymo was swept into Salado Creek floodwaters and wasn't recovered for four days. A second vehicle had to be pulled from high water near McCullough Avenue the same month. In response, Waymo issued an over-the-air software update to all 3,791 vehicles in its fleet, implementing geofence locks to keep cars off potentially flooded, higher-speed roads.

However, the fix proved incomplete. On May 20, during heavy rain in Atlanta, another unoccupied Waymo drove into a flooded intersection and sat stranded for about an hour, despite the geofence remedy already in place. Waymo attributed the incident to floodwaters rising faster than National Weather Service alerts could track. By May 21, Waymo paused operations in Atlanta, San Antonio, Dallas, Houston, Austin, and Nashville.

The same week brought a separate operational crisis. Waymo halted freeway rides in San Francisco, Los Angeles, Phoenix, and Miami after a reported incident on May 19 in which a Waymo allegedly drove through construction cones and swerved around trucks. The company said it was integrating "recent technical learnings into our software and expect to resume these routes soon".

San Francisco, Los Angeles, Phoenix, and Miami after a

What makes these pauses particularly significant is Waymo's own characterization of its initial fix. The company openly stated it "is developing the final remedy for this recall," meaning the geofence solution was a temporary scope constraint, not a permanent engineering solution.

How Is Waymo Managing Operations During the Pause?

Despite the operational setbacks, Waymo continued to announce expansion milestones. The company revealed it has scaled to 1,400 plus square miles across 11 cities ahead of the World Cup and surpassed 20 million paid rides. The company also launched its new Ojai vehicle, a Zeekr-built robovan designed for accessibility, in San Francisco, Phoenix, and Los Angeles.

The Ojai represents a technical refinement in Waymo's hardware approach. The vehicle features 40 percent fewer sensors than Waymo's previous generation, including 13 cameras, 6 radar sensors, and 4 LiDAR units with heated, self-cleaning housings for all-weather operation. The design includes accessibility features from the ground up, such as embedded braille, screen-reader compatibility, and seat-integrated support handles.

One notable operational challenge emerged when a passenger, Sam Schwartz, reported that his Waymo ride suddenly ended mid-trip in San Francisco, nowhere near his destination. Support staff told him to call Uber or Lyft. The incident suggests that geofence changes during active rides can trigger unexpected ride terminations, a problem that extends beyond weather-related pauses.

What Do These Incidents Reveal About Autonomous Vehicle Readiness?

The recent pauses highlight a critical distinction in autonomous vehicle development: the difference between controlled testing and real-world operations at scale. Waymo's fleet of nearly 3,800 vehicles operates continuously across multiple cities, encountering weather patterns, infrastructure changes, and edge cases that simulation and limited testing cannot fully predict.

The flooding incidents reveal a specific vulnerability. Autonomous systems trained primarily on clear-weather driving data may struggle when environmental conditions change rapidly. The fact that Waymo's initial fix was a geofence constraint rather than a fundamental improvement to the vehicle's perception or decision-making systems suggests the company is buying time to develop a more robust solution.

The freeway construction incident raises another concern: how well do autonomous systems handle dynamic infrastructure changes? Construction zones require real-time awareness of temporary lane closures, cone placement, and worker safety zones. A system that "blasted through cones" and swerved around trucks suggests the vehicle either failed to perceive the hazards or misinterpreted them as navigable obstacles.

• Fleet Size Impact: Waymo's 3,791-vehicle fleet means operational failures affect thousands of simultaneous rides, making each incident a scaling problem rather than an isolated edge case.
• Temporary vs. Permanent Fixes: Geofence locks are operational constraints, not engineering solutions; Waymo acknowledged it is still developing the final remedy for its flood-related recall.
• Real-World Complexity: Weather patterns, infrastructure changes, and passenger interactions reveal gaps that controlled testing environments cannot fully replicate.

Meanwhile, the broader robotaxi ecosystem continues to evolve. Voltera and Revel merged their businesses to create a large-scale EV charging infrastructure platform focused on autonomous vehicles, with over 1,000 charging stalls operational and under development across 11 major U.S. metro areas. Tesla, Waymo's primary competitor, is ramping up production of its Cybercab robotaxi and has filed permits for a 35,000-square-foot warehouse in Texas to dispatch, service, and repair vehicles, with space for up to 212 vehicles and 16 Supercharger stalls.

Waymo's challenges come at a moment when the robotaxi industry is racing to prove commercial viability. The company's willingness to pause operations in multiple cities suggests a commitment to safety over aggressive scaling, but it also underscores that autonomous driving at scale remains an unsolved engineering problem. The real test will be whether Waymo can develop permanent solutions to weather and infrastructure challenges before competitors close the gap.