San Francisco's fireworks night gridlock emptied batteries in several Waymos and stretched their flatbed recoveries past three hours, exposing a recovery gap that autonomous fleet permits haven't yet planned for.
Waymo's own explanation for why a fleet of its robotaxis ran out of power and stranded passengers during San Francisco's July 4 fireworks gridlock points to a more fragile operating model than the company has publicly acknowledged.
That night, the company said in statements to local outlets, severe traffic and unannounced road closures overwhelmed the routing logic in multiple Jaguar I-Pace Waymos on the northern edge of the city near the Golden Gate Bridge fireworks show. NBC Bay Area reporters on the scene captured multiple Waymo vehicles stopped for hours after the show ended, with remote support unable to clear them quickly. The San Francisco Standard documented the wider gridlock across the city, with autonomous vehicles part of the snarl. Business Insider tracked how some Waymos had to be flatbeded out.
Several Waymo vehicles fully depleted their high-voltage battery packs while idling in place, according to local reporting compiled in Yahoo Autos' pickup of the NBC Bay Area scene reporting. Battery depletion in gridlock is operationally narrow: it is what happens when prolonged idling meets a vehicle with no driver to take over. Once the high-voltage pack drops below operating threshold, the car cannot safely drive itself to a charger. That step converts a routing failure into a tow-truck problem.
Local residents reported individual vehicle recoveries took three to four hours to coordinate, according to the NBC Bay Area reporting from the scene. That figure is what stretched gridlock past midnight. While a single disabled robotaxi is a traffic nuisance, a queue of them becomes an effective roadblock. Three-to-four-hour recoveries at the moment when recovery infrastructure was least available are what turned gridlock into a stand-still.
Per NBC Bay Area's reporting from the scene, the sensor stack on the stranded Waymos included 29 cameras, 5 lidars, and 6 radars per vehicle. The hardware list does not change the operating story. The July 4 night was not a perception failure. The cars could see. They had nowhere legal and unblocked to go, and no human to push through.
A separate incident that night, an unoccupied Waymo vehicle that caught fire per San Francisco Chronicle reporting, was a distinct event from the gridlock strandings. The Chronicle's coverage tied that fire to illegally discharged street fireworks near the vehicle, not to congestion. The two should stay separate.
Waymo's reported position attributes the failures to environmental conditions outside its control. Environmental conditions include severe traffic spikes that recur on holidays, at major events, and during weather events. The next spike will look different; the lack of a recovery plan will not. An active federal recall report tied to Waymo's prior operational issues, RCLRPT-26E026, and NHTSA's Standing General Order on crash reporting, which covers robotaxis and Level 2 driver-assist features (adaptive cruise and lane keeping, where a human is still expected to be in charge), together establish the federal lane where these failures will eventually be counted.
The unanswered question is where robotaxi permits are now being decided: at peak holiday traffic, how fast a fleet of dead robotaxis gets cleared, and by whom.