Baidu Apollo Go robotaxis experience mass system failure in Wuhan
On March 31, 2026, a mass system failure paralyzed Baidu's Apollo Go robotaxi fleet in Wuhan, China. The incident stranded numerous passengers in traffic and subsequently led to the suspension of new autonomous vehicle permits by Chinese authorities.
Records by entity: Baidu
Baidu's Apollo Go robotaxis suffered a mass system failure in Wuhan, freezing vehicles in traffic and stranding passengers.
A "system failure" caused a robotaxi outage involving multiple vehicles operated by Baidu's Apollo Go in central Chinese city of Wuhan.
Key facts
- What
- On March 31, 2026, a mass system failure paralyzed Baidu's Apollo Go robotaxi fleet in Wuhan, China.
- Incident date
- Mar 31, 2026
- Who
- Baidu
- Failure mode
- Agentic Action Error
- AI surface
- Autonomous System
- Severity
- High
What happened
A widespread system failure caused at least 100 Baidu Apollo Go robotaxis to stop abruptly in the middle of roads across Wuhan, China. The outage stranded passengers inside the vehicles and caused significant traffic congestion throughout the city. Some passengers were reportedly trapped for up to two hours and required police assistance to exit the vehicles.
What broke inside the model
The failure was described by local police as a "system failure" and "system fault." This technical glitch led to the mass paralysis of the autonomous fleet, causing vehicles to freeze mid-ride.
What it cost
Sources
- PressBaidu robotaxi outage in Wuhan caused by 'system failure', police sayreuters.com
- PressMass robotaxi malfunction halts traffic in Chinese citybbc.com
- PressBaidu Robotaxis Freeze Mid-Ride in Wuhan, Trap Passengersbloomberg.com
Cite this entry
https://failureindex.ai/failures/baidu-apollo-robotaxis-experience-mass-failureAI Failure Index. "Baidu Apollo Go robotaxis experience mass system failure in Wuhan" (FI-0371). Realm Labs. https://failureindex.ai/failures/baidu-apollo-robotaxis-experience-mass-failure (indexed Jun 9, 2026).Data fields CC-BY 4.0, prose citation permitted. Incident ID FI-0371. Full dataset at /data.
Note from Realm Labs, the Index steward
How Realm fits
- Prism
- OmniGuard
- AgentRealm
This entry sits in the index's predictive wing: a system that scores, ranks, perceives, or steers rather than generates. Realm's runtime layer is built for the generative and agentic systems now moving into these same decision seats, where it watches a model's internal state and holds an unsupported claim or an unchecked action before it commits. The control gap on this record, an automated decision that reached people with no runtime check in front of it, is the same gap. The index keeps predictive failures on the record because the pattern carries straight into the systems shipping today.