The MachineRecord
RegistryTMR-0123

Zoox issues software recall for 270 robotaxis following a collision in Las Vegas

No harmrecallotherZoox
Date of incident
2025-05-06
Location
Las Vegas, Nevada, USA
Sources
4
EscalationRecall

Established by press reporting. No regulator or court document is linked to this case yet.

Timeline

How the event developed

  1. 2025-05-06Recall

    Zoox issues software recall for 270 robotaxis following a collision in Las Vegas

    engadget.com
  2. 2025-05-06Recall

    A Zoox robotaxi collided with a passenger vehicle in Las Vegas after the autonomous software incorrectly predicted the other vehicle's trajectory, prompting a software recall of all 270 operational Zoox robotaxis in Nevada.

    techtimes.com
  3. 2025-05-07Recall

    A Zoox unoccupied robotaxi collided with a passenger vehicle that had stopped in a shoulder lane after exiting a commercial driveway in Las Vegas, causing minor damage to both vehicles and no injuries.

    mexicobusiness.news
  4. 2025-05-09Follow-up

    An unoccupied Zoox robotaxi collided with a passenger vehicle in Las Vegas on April 8, 2025, causing minor damage to both vehicles and no injuries, prompting a software recall affecting 270 vehicles and a temporary pause of all Zoox driverless operations.

    lasvegassun.com
Sources

Every claim above traces to one of these

Links are never hidden behind a paywall of ours. Where a copy of the page exists it is linked beside the source with the date it was taken, because news links rot and a dead link next to a saved copy is still evidence. Some copies predate this register: they were made by the Internet Archive before we existed, and the date shown is the date of that copy, not of our visit.

Right of reply

Named in this case?

Any company named here can submit a response. We publish it in the case unedited, and a request makes the pipeline re-check the case against its own sources within a day. Target turnaround for our reply is five working days.