Waymo's July 4 stall was an EV idling problem, not a software failure.
Waymo's robotaxis stalled in San Francisco after the Golden Gate fireworks. The cause was not software: an idling EV keeps draining its battery, with no driver to notice.
Waymo's robotaxis stalled in San Francisco after the Golden Gate fireworks. The cause was not software: an idling EV keeps draining its battery, with no driver to notice.
Waymo's robotaxis stalled across San Francisco on the night of July 4, 2026, after the Golden Gate Bridge fireworks show. Stranded vehicles sat in gridlock near the Presidio until their batteries ran out and they had to be towed, according to Waymo spokesperson Chris Bonelli via Business Insider.
That was not a software failure. It was an idling-EV problem, and because robotaxis have no human driver to spot the dropping gauge, the failure mode travels with the fleet as Waymo expands into new cities.
The mechanism has nothing to do with autonomous driving. An idling electric car still draws power: climate control, compute, sensors, network radios. In a human-driven car, a driver watches the gauge drop and decides to shut systems off, pull over, or reroute. A robotaxi has no such fallback. The vehicle keeps the cabin comfortable for the next rider and keeps its perception stack warm while waiting for traffic to move. If gridlock lasts long enough, the battery depletes before the road clears — and because every vehicle in the same traffic jam is running the same climate and compute load at the same time, the failure can cascade through a concentrated fleet.
"Our team is always evaluating ways to strengthen Waymo's resilience in major traffic disruptions," Waymo told Business Insider. That phrasing fits a known operational constraint, because the company is openly working around it rather than treating the incident as a closed glitch.
The story first surfaced through a Yahoo Autos re-report that framed the incident as cars "running out of power." That headline overstates what Waymo said. The company told Business Insider that some vehicles idled and depleted while others "escaped" once congestion cleared, and it does not describe the event as a malfunction. Eyewitness video from the Presidio, a separate clip from inside a stalled vehicle, and a third post estimating a 3-4 hour tow queue corroborate the basic picture: many cars, stuck, getting towed. Gutierrez called it a "citywide Waymo malfunction." Waymo disputes the framing.
Waymo's San Francisco service area is densest around the neighborhoods that draw the biggest crowds on event nights: the Marina, the Presidio, the Embarcadero. A fireworks show pulls hundreds of robotaxis into the same small area at the same moment, every one of them idling in the same jam, every one burning charge at the same rate, with no human driver in any of them to make the call to abandon the route or kill the climate system.
Waymo's pitch to new cities is that autonomous fleets scale where human ride-hail cannot, because the marginal cost of an extra vehicle falls as the fleet grows. That math depends on robotaxis behaving predictably in the same urban conditions that stress every other vehicle on the road. A fleet that can be stranded by an idle-drain failure during a holiday traffic spike shares the same physics as a Toyota Prius in gridlock. The software advantage is real on the open road, while in a parking lot full of stalled cars it shrinks sharply.
Waymo has not disclosed how many cars were affected or what share of the San Francisco fleet that represented. The next disclosures worth reading are idle time per stranded vehicle and whether the dispatcher knew it was happening in real time.