Cases › operational mistake › LR-2026-0473
Baidu Apollo Go robotaxi outage in Wuhan, China, leaves passengers stranded and traffic stalled
Preliminary Why: 1 report: WIRED · subject to change · 1 independent report
Status: no action reported
No source states: loss or records, agent tool, could do, deployer, industry.
Severity moderate: Third-party vehicles were damaged in collisions, but the number affected and the scope are not stated as bounded in the sources, so the tier is moderate rather than major.
A fleet of Baidu robotaxis run under its Apollo Go service in Wuhan, China, was the subject of this incident. An unknown technical problem caused a number of the cars to freeze on Tuesday in the middle of traffic, trapping some passengers for more than an hour. Local police said the situation was likely caused by a system malfunction and that the incident is still under investigation. Passengers reported that the in-car phone line did not connect and the SOS button was unavailable. Photos and posts showed at least two other collisions on the same day involving the stopped vehicles. No one was injured, according to police. Baidu did not immediately respond to a request for comment.
What happened
No source tells the story step by step yet.
What was done
No source states an action or fix.
Risks
Primary43 incidents
Also63 incidents
Rising: 5 vs 2.2 a week
Sorted by rule from the case's fields; not yet read from the sources.
Controls
Not yet read for controls. Controls that mitigate the primary risk:
Harness ApplicationPhysical safety interlocks · Human approval for high-impact actions · Live behaviour monitoring · Adversarial testing before deployment
Similar incidents
Evidence
No source states: a step-by-step account, when it happened, when it was found, how many records were exposed, the direct loss, a count of the other parties affected, any court case, the cause, what set it off, what was done.
Show the full account: 5 items from the primary sources
What happened, in order
Not dated in the sources:
- Several Baidu robotaxis froze in traffic on Tuesday.
- About 30 minutes passed before a passenger reached a Baidu customer representative by phone.
- Baidu did not immediately respond to a request for comment.
- Local police issued a statement around midnight saying the situation was likely caused by a system malfunction and remained under investigation.
- At least two other collisions occurred the same day, according to photos and videos.
Show every field, with its source and grade
The AI system
What happened
Impact
Context
Notes on gaps
No remediation by Baidu is reported. Baidu did not respond to comment requests, so its own account is absent.
LR-2026-0473 · version 1 · published 2026-11-01 after automatic checks; not yet checked field by field by a person · JSON