The MachineRecord
RegistryTMR-0055

An unoccupied Zoox driverless robotaxi struggled to navigate heavy smoke at a fire scene on June 20, 2026, braking hard and coming to a stop, prompting a software recall across all 105 of the company's public-road vehicles.

No harmrecallotherZoox
Date of incident
2026-06-20
Location
United States
Sources
22
EscalationRecall

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

Timeline

How the event developed

  1. 2026-07-17Recall

    An unoccupied Zoox driverless robotaxi struggled to navigate heavy smoke at a fire scene on June 20, 2026, braking hard and coming to a stop, prompting a software recall across all 105 of the company's public-road vehicles.

    ttnews.com
  2. 2026-07-17Recall

    A Zoox robotaxi entered heavy smoke from an active fire scene in a traffic lane in Las Vegas, braked hard while attempting to steer away, and came to a stop before reversing under remote operator guidance, prompting a software recall of 105 vehicles.

    autos.yahoo.com
  3. 2026-07-17Recall

    An unoccupied Zoox robotaxi drove into smoke from an active fire scene in Las Vegas before the area was fully secured, braked and attempted to steer away, then reversed under remote operator guidance, leading to a software recall of 105 vehicles.

    autos.yahoo.com
  4. 2026-07-17Recall

    Zoox issued a software recall after one of its robotaxis became dangerously confused when it encountered heavy smoke, prompting safety concerns and a software update.

    techbuzz.ai
  5. 2026-07-17Recall

    Amazon-owned Zoox recalled 105 autonomous robotaxis after a software flaw caused one unoccupied vehicle to fail to detect heavy smoke and drive into an active emergency fire scene in Las Vegas, with no injuries reported.

    pluang.com
  6. 2026-07-17Recall

    An unoccupied Zoox robotaxi encountered heavy smoke obscuring an active emergency fire scene, braked hard while attempting to steer away, and came to a stop before a teleoperator reversed it clear, prompting a software recall of 105 vehicles.

    techcrunch.com
  7. 2026-07-17Recall

    An unoccupied Zoox robotaxi drove into an active emergency fire scene in Las Vegas that was obscured by heavy smoke, braked hard while attempting to steer away, and was reversed by a teleguidance employee, prompting a software recall of 105 vehicles.

    cnbc.com
  8. 2026-07-17Recall

    An unoccupied Zoox robotaxi drove into an active fire scene obscured by heavy smoke, hard-braked and attempted to steer away before stopping, and required remote operator intervention to reverse out of the scene.

    gizmodo.com
  9. 2026-07-17Recall

    An unoccupied Zoox robotaxi entered a smoke-filled active fire scene with no cones or barriers present, hard-braked and attempted to steer away, and required a remote human operator to guide it out in reverse.

    gadgetreview.com
  10. 2026-07-17Report

    An unoccupied Zoox robotaxi encountered thick smoke concealing an active fire scene, entered the zone before braking sharply, and was reversed out under remote operator guidance, prompting a software recall of all 105 Zoox robotaxis operating with software installed between April 23 and July 15, 2026.

    topgir.com.ua
  11. 2026-07-17Recall

    A Zoox autonomous robotaxi failed to detect heavy smoke at an emergency fire scene, impeding first responders, prompting the company to recall its fleet of 105 autonomous vehicles in the US for a software update to improve smoke detection.

    oecd.ai
  12. 2026-07-17Follow-up

    Zoox recalls robotaxis after an incident where vehicles encountered a smoky fire scene.

    bloomberg.com
  13. 2026-07-17Recall

    Zoox recalls 105 robotaxis following a fire scene incident

    autoweek.com
  14. 2026-07-17Recall

    Amazon's Zoox recalls 105 robotaxis due to a smoke detection issue.

    seekingalpha.com
  15. 2026-07-17Report

    Amazon’s Zoox recalls 105 robotaxis over smoke detection issue (ZOOX:Private) - Seeking Alpha

    seekingalpha.com
  16. 2026-07-17Report

    Amazon's Zoox issues software recall after robotaxi drove into heavy smoke - CNBC

    cnbc.com
  17. 2026-07-17Report

    Zoox Recall Affects 105 Robotaxis After Fire Scene Incident - autoweek.com

    autoweek.com
  18. 2026-07-19Recall

    Amazon's Zoox robotaxi fleet recalled after a vehicle became confused by heavy smoke.

    futurism.com
  19. 2026-07-19Report

    Amazon's Robotaxi Company Recalls Its Fleet After One of its Cars Got Confused by Heavy Smoke - Futurism

    futurism.com
  20. 2026-07-19Report

    Amazon's Robotaxi Company Recalls Its Fleet After One of its Cars Got Confused by Heavy Smoke - Futurism

    futurism.com
  21. 2026-07-20Follow-up

    An unoccupied Zoox robotaxi entered an active fire scene obscured by heavy smoke, braked hard while attempting to steer away, and was reversed out under remote operator guidance, with no injuries reported.

    carscoops.com
  22. 2026-07-20Recall

    Zoox recalls robotaxis after an incident where a vehicle encountered a smoky fire scene

    thestar.com.my
  23. 2026-07-20Report

    Amazon’s Zoox Recalls Entire Robotaxi Fleet to Fix Smoke Detection Flaw - Ubergizmo

    ubergizmo.com
  24. 2026-07-20Report

    Weekly Recap: Amazon Q1 revenue growth and AWS leadership change - TradingView

    tradingview.com
  25. 2026-07-21Recall

    Amazon's Zoox recalls robotaxis after vehicles failed to recognize an active fire scene.

    planetizen.com
  26. 2026-07-21Report

    Amazon's Zoox recalls robotaxis after failure to recognize active fire scene - planetizen.com

    planetizen.com
  27. 2026-07-30Report

    Amazon’s Zoox secures US federal approval for steering-wheel-free robotaxis - Al Jazeera

    aljazeera.com
  28. 2026-08-12Report

    Amazon's Zoox Launches Paid Robotaxi Service In Las Vegas and Says 'We Need To Be Regulated'— The Smoke Incident That Prompted a Recall Explains Why - Yahoo Finance

    finance.yahoo.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.