Tech
Waymo has stopped its robotaxis from driving on the freeway—here’s why
Publication: Ars Technica
Author: Jonathan M. Gitlin
Source published: 18/11/2026, 16:24:34 UTC
Briefing created: 18/11/2026, 17:28:38 UTC
Based on a feed excerpt; full article content has not been acquired. Source evidence retrieved 18/11/2026, 16:43:23 UTC.
Briefings
Waymo restricted its robotaxi fleet to surface streets in California following incidents where software drove into construction zones, prompting the state DMV to order an immediate halt until safety concerns were addressed. The company recalled nearly 3,800 vehicles in June and updated software to prioritize construction zones, but resumed highway operations in early July after the DMV approved the changes. This incident occurred after Waymo previously failed to recognize ramp closures in Phoenix, Arizona, and had similar issues in California.
Key points
- Waymo robotaxis were ordered to stop driving on California highways immediately after the state DMV determined their driving behavior posed an imminent hazard to public safety.
- Waymo recalled nearly 3,800 robotaxis capable of highway driving in June following incidents where the software drove into active construction zones.
Context
Waymo's robotaxis previously failed to recognize ramp closure signs in Phoenix, Arizona, and had similar issues in California. The state DMV ordered Waymo to stop driving on Californian highways immediately and until it can convince the DMV that its cars no longer pose an imminent hazard to public safety.
Limitations
Evidence covers incidents from April to early July 2026. Software updates were announced in early July but highway operations resumed in early July, creating a gap between announcement and full implementation. Specific failure rates for Arizona ramp closures and California construction entries are not quantified in the source.
Generated by Bittrees-hosted qwen35-2b sha256:aaf42c8b7c3c on 18/11/2026, 17:28:38 UTC. Based on publisher-provided feed evidence; may not cover the full original article. Check the source for details.
View archived briefing on IPFS
bafybeidvtxc7oecdg4s374xweikqauaobyhgrpeulpior7rtq72wdeghia