RegistryTMR-0768
Zoox recalled software on all 105 robotaxis after one vehicle drove into an active fire scene obscured by heavy smoke in Las Vegas on June 20, 2026.
- Date of incident
- 2026-06-20
- Location
- Las Vegas, Nevada
- Sources
- 23
EscalationRecall
Established by press reporting. No regulator or court document is linked to this case yet.
How the event developed
- 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
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.
- ttnews.comAn 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.2026-07-17copy 2026-10-26tier 2
- autos.yahoo.comA 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.2026-07-17copy 2026-10-16tier 2
- autos.yahoo.comAn 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.2026-07-17copy 2026-10-19tier 2
- techbuzz.aiZoox issued a software recall after one of its robotaxis became dangerously confused when it encountered heavy smoke, prompting safety concerns and a software update.2026-07-17copy 2026-10-29tier 2
- pluang.comAmazon-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.2026-07-17copy 2026-10-13tier 2
- techcrunch.comAn 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.2026-07-17copy 2026-10-26tier 2
- cnbc.comAn 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.2026-07-17copy 2026-10-19tier 1
- gizmodo.comAn 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.2026-07-17copy 2026-10-27tier 2
- gadgetreview.comAn 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.2026-07-17copy 2026-10-19tier 2
- topgir.com.uaAn 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.2026-07-17copy 2026-10-17tier 2
- oecd.aiA 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.2026-07-17copy 2026-10-28tier 2
- bloomberg.comZoox recalls robotaxis after an incident where vehicles encountered a smoky fire scene.2026-07-17no copytier 1
- autoweek.comZoox recalls 105 robotaxis following a fire scene incident2026-07-17copy 2026-10-28tier 2
- seekingalpha.comAmazon's Zoox recalls 105 robotaxis due to a smoke detection issue.2026-07-17copy 2026-10-27tier 2
- autos.yahoo.comZoox recalls 105 robotaxis after smoke detection failure - Yahoo Autos2026-07-17copy 2026-10-23tier 3
- futurism.comAmazon's Zoox robotaxi fleet recalled after a vehicle became confused by heavy smoke.2026-07-19copy 2026-10-31tier 2
- carscoops.comAn 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.2026-07-20copy 2026-10-26tier 2
- thestar.com.myZoox recalls robotaxis after an incident where a vehicle encountered a smoky fire scene2026-07-20copy 2026-10-17tier 2
- ubergizmo.comAmazon’s Zoox Recalls Entire Robotaxi Fleet to Fix Smoke Detection Flaw - Ubergizmo2026-07-20copy 2026-10-29tier 2
- tradingview.comWeekly Recap: Amazon Q1 revenue growth and AWS leadership change - TradingView2026-07-20copy 2026-10-11tier 2
- planetizen.comAmazon's Zoox recalls robotaxis after vehicles failed to recognize an active fire scene.2026-07-21copy 2026-10-30tier 2
- aljazeera.comAmazon’s Zoox secures US federal approval for steering-wheel-free robotaxis - Al Jazeera2026-07-30copy 2026-10-23tier 2
- finance.yahoo.comAmazon'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 Finance2026-08-12copy 2026-10-13tier 3
New cases, once a week, by email
Every case added to the register in the last seven days, with its sources. Free, no account, and the register is the only sender.
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.