DEPLOYDatabase

Incident · Recall

Waymo recalls 3,871 robotaxis after vehicles entered closed freeway construction zones in Phoenix and San Francisco Bay Area

Waymo filed a voluntary recall (NHTSA Campaign 26E035) on June 17, 2026 covering 3,871 vehicles with its 5th Generation ADS after more than a dozen incidents since early April in Arizona and California where robotaxis failed to recognize and drove past ramp closure signs into pre-planned freeway construction zones. On May 18, seven Waymo AVs entered active freeway construction lanes in the San Francisco Bay Area by driving between cones.

No collisions or injuries were reported. Waymo restricted and then suspended freeway operations while developing a software fix.

Occurred 2026-04-11 · Waymo · Investigated by NHTSA

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.
Track Waymo recalls 3,871 robotaxis after vehicles entered closed freeway construction zones in Phoenix and San Francisco Bay Area

Machine-readable surfaces

Sources (2)

  1. NHTSA · https://static.nhtsa.gov/odi/rcl/2026/RCLRPT-26E035-7637.pdf · 2026-06-17
  2. Reuters · https://www.reuters.com/legal/litigation/waymo-recall-over-3800-robotaxis-over-risk-entering-closed-construction-zones-2026-06-18/ · 2026-06-18

Status history

  • Active · 2026-07-23 · agent:recon

Common questions

What happened in Waymo recalls 3,871 robotaxis after vehicles entered closed freeway construction zones in Phoenix and San Francisco Bay Area?
Waymo filed a voluntary recall (NHTSA Campaign 26E035) on June 17, 2026 covering 3,871 vehicles with its 5th Generation ADS after more than a dozen incidents since early April in Arizona and California where robotaxis failed to recognize and drove past ramp closure signs into pre-planned freeway construction zones. On May 18, seven Waymo AVs entered active freeway construction lanes in the San Francisco Bay Area by driving between cones. No collisions or injuries were reported. Waymo restricted and then suspended freeway operations while developing a software fix.
When did this incident occur?
The incident is recorded as occurring on April 11, 2026 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.
Who was involved in Waymo recalls 3,871 robotaxis after vehicles entered closed freeway construction zones in Phoenix and San Francisco Bay Area?
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 Waymo recalls 3,871 robotaxis after vehicles entered closed freeway construction zones in Phoenix and San Francisco Bay Area?
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 Waymo recalls 3,871 robotaxis after vehicles entered closed freeway construction zones in Phoenix and San Francisco Bay Area?
This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.
Methodology: Verified · 2 sources (1 primary) · last reviewed 2026-08-09

Verification posture

Verified

High confidence

Review state

Stable

Last reviewed 2026-08-09

Sources by quality tier

1
primary-regulatory-filing
Regulatory filing
1
secondary-established-publication
Established publication

The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.

Methodology surface for Waymo recalls 3,871 robotaxis after vehicles entered closed freeway construction zones in Phoenix and San Francisco Bay Area.

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 b7564a08-ddcf-4ca3-a9c2-523007876bf5