DEPLOYDatabase

Retracted · 2026-11-01

Duplicate record of the same event; see /incidents/nhtsa-waymo-recall-26e035000.

Incident · Recall · Retracted

Waymo recalls 3,871 robotaxis over software causing vehicles to enter closed freeway construction zones

Original claim shown above is no longer asserted. See the retraction notice for context.

Waymo recalled 3,871 robotaxis in the U.S. (NHTSA recall 26E035000) after more than a dozen incidents in California and Arizona where autonomous vehicles failed to recognize ramp-closure signs and drove into freeway construction zones at speed. The software issue involved inappropriately prioritizing avoidance of other freeway hazards over recognizing construction zones. This was Waymo's second recall in two months.

Occurred 2026-06-18 · Waymo Jaguar I-PACE robotaxi fleet · Waymo · Robotaxis

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

Sources (2)

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

Status history

  • Retracted · 2026-11-01 · editor:waymo-incident-dupes-2026-11-01

    Duplicate record of the same event; see /incidents/nhtsa-waymo-recall-26e035000.

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

Common questions

What happened in Waymo recalls 3,871 robotaxis over software causing vehicles to enter closed freeway construction zones?
Waymo recalled 3,871 robotaxis in the U.S. (NHTSA recall 26E035000) after more than a dozen incidents in California and Arizona where autonomous vehicles failed to recognize ramp-closure signs and drove into freeway construction zones at speed. The software issue involved inappropriately prioritizing avoidance of other freeway hazards over recognizing construction zones. This was Waymo's second recall in two months. This incident was later retracted; see the retraction banner at the top of the page for the correction.
When did this incident occur?
The incident is recorded as occurring on June 18, 2026 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.
What robot was involved in Waymo recalls 3,871 robotaxis over software causing vehicles to enter closed freeway construction zones?
Waymo Jaguar I-PACE robotaxi fleet by Waymo is the recorded robot involved in this incident.
Has anyone responded to Waymo recalls 3,871 robotaxis over software causing vehicles to enter closed freeway construction zones?
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 over software causing vehicles to enter closed freeway construction zones?
This incident is retracted on the DEPLOY registry. The page remains so the correction reaches readers, but the incident is suppressed from aggregate counts (company / model / location) so it no longer counts against anyone.
Methodology: Verified · 2 sources (1 primary) · last reviewed 2026-11-01

Verification posture

Verified

High confidence

Review state

Stable

Last reviewed 2026-11-01

Sources by quality tier

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

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

Methodology surface for Waymo recalls 3,871 robotaxis over software causing vehicles to enter closed freeway construction zones.

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 af5ec781-012f-4e9f-a4ad-8fae40bfefee