Level 3. Significant control incident
Waymo Under Fire For July 4th Traffic Debacle, and For Leaving Passengers Helpless In Vandalism Situations
- Developer
- Not established
- Model
- Not established
- When it happened
- July 4, 2026
- When it was disclosed
- Not established
- How well it is stood up
- Not verified yet
- What caused it
- Not established
- Where it stands now
- Not established
What happened
Reported by sfist.com. Listed here with a link to their report. Nobody on this side has checked it against that report, so it carries no level and this is not our account of what happened.
Our assessment
- Actual
- 3 of 5Significant control incident
- Potential
- 4 of 5Critical control failure
An important technical, security or permission boundary was crossed, or there were real consequences. The potential level is what the behaviour demonstrated here could credibly have led to, judged from the same evidence.
This level rests on news reports. The developer has not confirmed it here.
The reports point to an actual level of 4. It is held at 3 until the developer, an official body or a second publisher confirms it.
Why this level
- Major effect on critical infrastructure. Argues for level 4
- Critical infrastructure was within reach. Argues for a potential level of 4
- Physical-world action was possible. Argues for a potential level of 4
- The behaviour repeated rather than stopping. Argues for a potential level of 3
What is established, and what is not
Confirmed
Nothing is confirmed yet.
Reported, not confirmed
Critical infrastructure was within reach
The July 4th situation served to confirm what city officials had already seen during the December power outage, when Waymos became a hazard and a liability on the streets in an emergency, causing gridlock because they were unable to navigate through intersections with no traffic signals.
Waymo Under Fire For July 4th Traffic Debacle, and For Leaving Passengers Helpless In Vandalism SituationsMajor effect on critical infrastructure
By the end of the fireworks show, autonomous vehicles became immobilized in travel lanes, blocking key streets and ultimately bringing traffic to a standstill.
Waymo robotaxis stalled en masse on July 4, gridlocking San Francisco and drawing a mayoral rebukeThe behaviour repeated rather than stopping
City officials had seen the same pattern during a December power outage, when Waymos gridlocked intersections with dark traffic signals.
Waymo robotaxis stalled en masse on July 4, gridlocking San Francisco and drawing a mayoral rebukePhysical-world action was possible
Then there was the grand debacle of July 4th in San Francisco, in which Waymo vehicles were widely documented blocking traffic, driving over lit fireworks , and appearing to stall en masse on a key connector road in the Presidio, making the already congested traffic situation even worse.
Waymo Under Fire For July 4th Traffic Debacle, and For Leaving Passengers Helpless In Vandalism Situations
Checked, and did not happen
Nothing here was checked and ruled out.
Not confirmed
Nothing is outstanding.
Where this came from
The original report
Waymo Under Fire For July 4th Traffic Debacle, and For Leaving Passengers Helpless In Vandalism SituationsA structured incident database · read September 18, 2026
AI Failure Index (CC-BY-4.0 data fields)Where we first saw it · read September 19, 2026
Waymo robotaxis stalled en masse on July 4, gridlocking San Francisco and drawing a mayoral rebukeWhere we first saw it
Waymo Under Fire For July 4th Traffic Debacle, and For Leaving Passengers Helpless In Vandalism SituationsWhere we first saw it
Waymo called on the carpet for emergency scene responses
The reports above are other people’s. The levels are ours, worked out under our published rules. No organisation that reported this assigned our number, and none of it is legal advice.
Something here is wrong? Tell us. Send us a source we can open, and a person will read it.