Drivers sat in traffic for two hours while bystanders shouted at the stranded robotaxis blocking intersections. It's the second documented San Francisco area Waymo stranding in under a year.
Dave Guingona sat for two hours in his car on the night of July 4th, watching bystanders climb out of their vehicles to shout at stranded, driverless Waymo robotaxies blocking intersections around the Presidio. He told NBC Bay Area the cars were being flat-towed from the roadway while ordinary holiday traffic sat at a standstill.
The scene was a structural failure mode made visible. These were not mechanical stalls or perception bugs in the usual sense. The proximate cause, per NBC Bay Area's reporting, was battery drain: hours of stop-and-go traffic around the waterfront fireworks show, layered with coastal fog and slow transit, sapped the cars' traction packs before the corridor cleared. The public reporting does not break out how much of the drain came from HVAC, sensor compute, or idle creep. The cars' batteries ran out before traffic did.
That is the mechanism worth naming. A human driver stuck in a slow crawl can manage the vehicle: shift into neutral, idle the engine, ease forward when the lane opens. A driverless robotaxi with no human inside has no such fallback. When its pack sags in a low-speed crawl, the car sits where it dies until a flatbed arrives.
The Presidio and Marina corridor, heading away from the waterfront show, is the same stretch Waymo has run paid driverless service on since 2022 and 2023. The cars were not in a fringe testing zone; they were in the city's busiest holiday pedestrian artery, the SF Standard noted.
Rider Rose Peterson told ABC7 News her Waymo drove over lit fireworks debris in a crosswalk during the same stretch of traffic, a detail she described as a gap in the cars' training data.
The pattern is the second documented mass-fleet Waymo stranding in the San Francisco area in under a year, following the local blackout incident earlier in 2026 that left Waymos stuck across neighborhood streets. The July 4th version is not a software bug or a perception failure in the conventional sense. It is a power-and-occupancy problem: the kind of failure a human driver can limp through and a robotaxi cannot.
Scale language across the public reporting remains soft, with outlets describing the incident as involving several cars or a number of Waymos without a specific count or share of the active SF fleet. Across NBC Bay Area, the SF Chronicle, the SF Standard, CBS Bay Area, and ABC7, the public reporting converges on the same facts: empty robotaxies, dead batteries, bystanders shouting, flatbed tow-outs, and a holiday corridor at a standstill.
What comes next is what Waymo does with the pattern. The company had not issued a public statement on the July 4th incident as of July 6, and the specific mechanism, battery sag in low-speed crawl with no in-vehicle mitigation, is not one a remote operator can patch from a console. It lives in the vehicle's behavior when its own pack is dying.