Incident 253: Cruise's Self-Driving Cars Allegedly Lost Connection to Their Server, Causing Traffic Blockages in San Francisco
Entities
View all entitiesIncident Stats
GMF Taxonomy Classifications
Taxonomy DetailsKnown AI Goal
Autonomous Driving
Potential AI Technology
Image Segmentation, Geolocation Data
Potential AI Technical Failure
Software Bug, Hardware Failure, Backup Failure
Incident Reports
Reports Timeline
- View the original report at its source
- View the report at the Internet Archive
A very San Francisco Saturday night. A pack of 3 driverless @Cruise cars got confused and stopped and blocked two lanes of Masonic. The robots will win just by blocking traffic.
- View the original report at its source
- View the report at the Internet Archive
Cruise’s driverless cars experienced serious issues Tuesday night with as many as 20 of its vehicles standing motionless for about two hours at the corner of Gough and Fulton streets, according to an eyewitness. The incident was only resolv…
- View the original report at its source
- View the report at the Internet Archive
GM Cruise snafus have blocked SF streets with suddenly immobilized self-driving cars at least three times in the last two months, with one incident where almost 60 vehicles stopped, and another where Cruise “lost touch with its entire fleet…
- View the original report at its source
- View the report at the Internet Archive
Around midnight on June 28, Calvin Hu was driving with his girlfriend near San Francisco’s Golden Gate Park when he pulled up at an intersection behind two white and orange autonomous Chevrolet Bolts operated by Cruise, a subsidiary of Gene…