Incident · Regulatory action
SF Supervisor Bilal Mahmood launches inquiry into Waymo's July 4 traffic meltdown
On July 7, 2026, San Francisco Supervisor Bilal Mahmood announced a letter of inquiry to the city's Department of Emergency Management, Fire Department, and Municipal Transportation Agency, seeking information on how Waymo robotaxis contributed to massive gridlock following the July 4 Golden Gate Bridge fireworks show. More than 30 Waymo robotaxis became stuck in the Presidio parking area, some running out of charge and requiring towing. Mahmood stated it is 'not acceptable that disruption of service, first responders and our public transit system is a side effect of autonomous vehicles' and requested city departments respond within two weeks. The inquiry follows repeated Waymo run-ins with first responders documented by TechCrunch and a July 8 NHTSA directive demanding AV companies stop interfering with emergency operations.
Occurred 2026-07-07 · Waymo
How to read this record
Incident records on DEPLOY are compiled from public sources (regulatory filings, news reports, and operator disclosures) and reflect what has been reported and tracked to date. They are not legal findings, determinations of fault, or safety ratings, and may be updated as new information is verified. See the sources below for the underlying references.Machine-readable surfaces
- Markdown mirror: /incidents/waymo-sf-mahmood-inquiry-2026-07-07.md
- JSON-LD: embedded in this page’s head
- REST API: /v1/incidents/7912e9ad-b28a-4621-b652-cf40ff03f337
- Data documentation: /data
- Query this programmatically: Deploy MCP
Sources (2)
Common questions
- What happened in SF Supervisor Bilal Mahmood launches inquiry into Waymo's July 4 traffic meltdown?
- On July 7, 2026, San Francisco Supervisor Bilal Mahmood announced a letter of inquiry to the city's Department of Emergency Management, Fire Department, and Municipal Transportation Agency, seeking information on how Waymo robotaxis contributed to massive gridlock following the July 4 Golden Gate Bridge fireworks show. More than 30 Waymo robotaxis became stuck in the Presidio parking area, some running out of charge and requiring towing. Mahmood stated it is 'not acceptable that disruption of service, first responders and our public transit system is a side effect of autonomous vehicles' and requested city departments respond within two weeks. The inquiry follows repeated Waymo run-ins with first responders documented by TechCrunch and a July 8 NHTSA directive demanding AV companies stop interfering with emergency operations.
- When did this incident occur?
- The incident is recorded as occurring on July 7, 2026 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.
- Who was involved in SF Supervisor Bilal Mahmood launches inquiry into Waymo's July 4 traffic meltdown?
- The incident is recorded as involving Waymo on the DEPLOY registry. No specific robot model is linked to this incident in the registry.
- Has anyone responded to SF Supervisor Bilal Mahmood launches inquiry into Waymo's July 4 traffic meltdown?
- No responses to this incident are recorded on the DEPLOY registry. Operators, manufacturers, or affected parties can submit responses to the editorial team; absence is not a guarantee no response was issued.
- What is the current status of SF Supervisor Bilal Mahmood launches inquiry into Waymo's July 4 traffic meltdown?
- This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.
Methodology: Verified · 2 sources (no primary) · last reviewed 2026-07-14
Verification posture
Verified
Low confidence
Review state
Stable
Last reviewed 2026-07-14
Sources by quality tier
- 1
- unclassified
- Unclassified source
- 1
- secondary-industry-publication
- Industry publication
The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.
Methodology surface for SF Supervisor Bilal Mahmood launches inquiry into Waymo's July 4 traffic meltdown.Deploy Watch
Track this incident.
We notify you when the regulator updates the record, the remedy status changes, or a related incident surfaces.
Canonical ID 7912e9ad-b28a-4621-b652-cf40ff03f337