California regulators ordered the immediate halt of autonomous highway travel following traffic incidents that posed an imminent public safety hazard. Waymo responded by temporarily suspending its driverless freeway operations across the entire country while it conducts an internal performance review. Although the company operates in 15 U.S. cities, its high-speed freeway rides were only active in a select few markets, including Los Angeles and San Francisco.
Key points
Regulatory safety interventions in California prompted a complete nationwide pause of hig…: Regulatory safety interventions in California prompted a complete nationwide pause of high-speed autonomous operations.
The company will keep freeway operations offline while it evaluates safety data and vehic…: The company will keep freeway operations offline while it evaluates safety data and vehicle performance.
Broader municipal services across 15 cities remain separate from the select freeway offer…: Broader municipal services across 15 cities remain separate from the select freeway offerings that were suspended.
Sources checked by our analysis pipeline: 1
Waymo has temporarily suspended driverless rides on US freeways after California banned the service over safety concerns.
California's Department of Motor Vehicles said a series of traffic incidents, including robotaxis entering active construction zones, posed an imminent risk to public safety. Waymo has now restricted freeway operations in all other US markets while it reviews the performance of its vehicles.
Waymo currently operates in 15 US cities, though only offered driverless freeway rides in a handful of cities, including San Francisco and Los Angeles.
The programming language's maintenance strategy has been updated to deliver both security patches and select backported bug resolutions going forward. Because of this expanded focus on stability, the development team has officially rebranded the support period as the legacy maintenance phase. This ongoing support remains fully guaranteed through the previously established timeline ending in March 2027.
The core language maintainers have delivered critical maintenance updates addressing identified security vulnerabilities and routine software flaws. Published by k0kubun, this distribution arrives alongside coordinated maintenance releases across multiple supported release lines to ensure ecosystem stability. Developers relying on these platforms can now access updated packages through standard project distribution channels.
Maintainers have delivered vital security patches and general bugfixes through community contributions from numerous developers and testers. This deployment addresses ongoing stability concerns for systems running modern branches of the language. It arrived as part of a synchronized maintenance cycle impacting several supported release lines on the same day.