When did this incident occur?

The incident is recorded as occurring on April 8, 2025 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.

Incident · Recall

Zoox recalled ~270 robotaxis after a Las Vegas collision with a passenger car

On April 8, 2025, an unoccupied Zoox purpose-built robotaxi collided with a passenger car in Las Vegas. No injuries occurred and damage to both vehicles was minor. Zoox paused all driverless operations for over a week, then issued a voluntary software recall covering approximately 270 vehicles, after determining its automated driving system could inaccurately predict another vehicle's movement and increase crash risk. Zoox resumed operations after deploying the software update fleet-wide. This was Zoox's second recall of 2025 (the first, ~258 vehicles in March 2025, addressed unexpected hard braking).

Occurred 2025-04-08 · Zoox Robotaxi · Zoox

Track Zoox recalled ~270 robotaxis after a Las Vegas collision with a passenger car

Machine-readable surfaces

Markdown mirror: /incidents/zoox-las-vegas-collision-recall-2025-04-08.md
JSON-LD: embedded in this page’s head
REST API: /v1/incidents/248bdaf3-8333-459f-bd27-b6c7912ff9c6
Data documentation: /data
Query this programmatically: Deploy MCP

Outcomes (2)

regulatory actionverified
property damageverified

Revision history (2)

2026-06-05 · outcome_class
2026-06-05 · outcome_class

Outcome rows carry verification_posture independently. Revision events carry basis (verified_court_filing, verified_insurance, reported_press, estimate, undisclosed). The framework records outcomes only when verifiable; absence is honest absence, not a claim of no-impact.

Sources (5)

Zoox 270-vehicle recall after April 8 Las Vegas crash; ADS movement-prediction defect · https://www.cnbc.com/2025/05/06/amazon-zoox-recall.html · 2025-05-06
Second 2025 recall; March recall was 258 vehicles for hard braking · https://techcrunch.com/2025/05/06/amazon-owned-zoox-issues-recall-following-robotaxi-crash/ · 2025-05-06
https://www.foxbusiness.com/technology/amazons-zoox-recalls-robotaxi-software-update-after-las-vegas-crash · 2025-05-06
https://www.reviewjournal.com/local/traffic/robotaxi-crash-in-las-vegas-led-to-zoox-recall-pause-in-autonomous-vehicle-testing-3368708/
https://www.autonomousvehicleinternational.com/news/safety/zoox-issues-software-recall-following-las-vegas-incident.html

Common questions

What happened in Zoox recalled ~270 robotaxis after a Las Vegas collision with a passenger car?: On April 8, 2025, an unoccupied Zoox purpose-built robotaxi collided with a passenger car in Las Vegas. No injuries occurred and damage to both vehicles was minor. Zoox paused all driverless operations for over a week, then issued a voluntary software recall covering approximately 270 vehicles, after determining its automated driving system could inaccurately predict another vehicle's movement and increase crash risk. Zoox resumed operations after deploying the software update fleet-wide. This was Zoox's second recall of 2025 (the first, ~258 vehicles in March 2025, addressed unexpected hard braking).
When did this incident occur?: The incident is recorded as occurring on April 8, 2025 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.
What robot was involved in Zoox recalled ~270 robotaxis after a Las Vegas collision with a passenger car?: Zoox Robotaxi by Zoox is the recorded robot involved in this incident.
Has anyone responded to Zoox recalled ~270 robotaxis after a Las Vegas collision with a passenger car?: 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 Zoox recalled ~270 robotaxis after a Las Vegas collision with a passenger car?: This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.

Methodology: Verified · 5 sources (no primary) · last reviewed 2026-06-24

Verification posture

Verified

Medium confidence

Review state

Stable

Last reviewed 2026-06-24

Sources by quality tier

3: unclassified; Unclassified source
1: secondary-established-publication; Established publication
1: secondary-industry-publication; Industry publication

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

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 248bdaf3-8333-459f-bd27-b6c7912ff9c6