California DMV Bans Waymo From Freeways, Citing 'Imminent Hazard'
California's DMV banned Waymo from freeways on November 11, calling its highway driving an "imminent hazard to public safety." Waymo has paused highway driving across all 15 of its markets.

Why it matters
- California DMV banned Waymo freeway operations on November 11, citing an "imminent hazard to public safety."
- Waymo has paused highway driving in all of its markets; surface-street service continues in 15 metros.
- The ban followed two incidents: three Waymos entering a Route 101 construction closure and a viral video of a Waymo interfering with CHP traffic break enforcement.
- In June, Waymo recalled software after NHTSA found it failed to recognize highway construction zones.
- NHTSA is examining whether Waymo's December recall fix resolved robotaxis driving past stopped school buses.
California's DMV banned Waymo's self-driving taxis from state freeways on November 11, after determining the company's highway driving poses "an imminent hazard to public safety." Waymo has responded by pausing highway driving in every one of its markets, not just California's.
The shutdown is national in scope. Waymo vehicles will continue operating on surface streets in the 15 metros where the company offers taxi service, including portions of Los Angeles, San Diego, and the San Francisco Bay Area. The company may also keep testing on non-California highways, but only with safety operators behind the wheels.
For a company that has positioned itself as the most mature robotaxi operator in the US, a regulator using the phrase "imminent hazard" is a serious blow. It's also the second time Waymo has publicly restricted freeway operations since it began transporting passengers on highways last year.
What triggered the ban?
The California DMV pointed to two recent incidents, described in a statement by DMV spokesperson Jonathan Groveman.
In the first, three Waymo vehicles entered an active highway construction closure on Route 101 on the San Francisco Peninsula. In the second, a viral video captured a Waymo vehicle interfering with California Highway Patrol cars on a San Francisco highway. The CHP units were trying to enforce a "traffic break" — slowing traffic so workers could clear debris from a crash — and the robotaxi got in their way.
Neither incident involved a collision, according to the source material. But the pattern mattered more than the outcome: a driverless car that cannot read a construction closure or yield to police directing traffic fails at two of the most basic expectations of road use.
The takeaway: the ban came from specific, observable failures, not an abstract worry about autonomy.
When can Waymo go back on the freeway?
Not soon, and not on Waymo's own timetable. Groveman said the California ban will remain in place until Waymo has proved it has "taken effective corrective actions to address the deficiencies" that led to the incidents. It's unclear how long that process will take.
Waymo, for its part, is striking a cooperative tone. In a written statement to WIRED, spokesperson Dana Gallagher said the company is "working with the California DMV and other state officials diligently and responsibly to resume freeway operations."
That puts the burden of proof on Waymo. The company has to demonstrate, to a regulator's satisfaction, that its software now handles the situations it failed — construction closures and police-orchestrated traffic breaks — before its cars return to California freeways.
The takeaway: this is an open-ended suspension, and the clock is controlled by the DMV, not by Waymo.
This isn't Waymo's first construction-zone problem
The November ban fits a longer pattern. In June, Waymo recalled its software after federal regulators found that its system failed to recognize highway construction zones. Regulators at the National Highway Traffic Safety Administration (NHTSA) cited several incidents in April and May in which Waymo cars drove past ramp closure signs and into active lane closures. Those events did not lead to collisions or injuries.
NHTSA did not immediately respond to a request for comment on the current situation.
The agency also has an open question about a different Waymo fix. Last week, NHTSA said it was examining whether another Waymo recall software update had actually solved its robotaxis' safety issues. That recall, which occurred last December, was tied to incidents in which Waymo cars repeatedly drove past stopped school buses with their lights on and/or stop arms extended — behavior that human drivers are legally required to stop for.
The picture that emerges is a regulator catching the same category of failure more than once. Construction zones in the spring and summer, school buses in December, and now construction closures plus a police traffic break in November. Each fix prompts a recall or a review; each review seems to surface a new edge case.
The takeaway: NHTSA is now auditing whether Waymo's past fixes actually work, while the DMV has forced a fresh nationwide highway pause.
Why construction zones are so hard for self-driving cars
Self-driving cars have struggled with construction zones for at least a decade, and the reasons are structural rather than temporary. Construction zones can look and be arranged differently depending on what sort of work is being done, and where it's happening.
Humans can easily understand bollards, placards, and blinking arrows, because we read intent and context. But the lack of hard-and-fast rules in work zones has proven difficult to reliably program into driving software. There is no single sign or signal that always means "closed" — there are improvisations: cones, barrels, hand signals, temporary barriers, a worker waving cars through.
The problem is most dangerous at freeway speeds, where workers stand alongside fast-moving traffic. A software misread at 25 mph on a city street is a near-miss; the same misread at 65 mph next to a work crew is a potential fatality. That speed differential is precisely why the DMV acted on highway operations while letting surface-street service continue.
The takeaway: work zones are an unsolved edge case for the whole industry, and they're most dangerous exactly where Waymo has now been banned.
What does this mean for Waymo and the robotaxi market?
The immediate commercial damage is contained. Waymo's passengers can still hail rides across the 15 metros where it operates, including the Los Angeles, San Diego, and San Francisco Bay Area service areas — they just won't ride on highways. Surface streets remain open for business.
The regulatory damage is harder to contain. A state DMV declaring a company's driving an "imminent hazard to public safety" gives ammunition to every jurisdiction weighing whether to admit robotaxis, and to every federal investigator deciding how hard to press. With NHTSA already probing whether Waymo's December recall actually fixed the school-bus problem, and the June construction-zone recall still recent history, the company now faces scrutiny on two fronts at once.
The path back runs through proof, not promises. Until Waymo demonstrates "effective corrective actions" — the DMV's own words — its cars stay off California freeways, and by its own choice, off highways everywhere. How quickly the company can certify that its software finally understands cones, closures, and cops will say a lot about how soon highway robotaxi rides return, in California or anywhere else.
Source: wired.com
More from Sophie Lindqvist
Show full bio
Staff writer covering regulation, policy and their impact on artificial intelligence and machine learning at AI In Context.
749 articles
Related articles
- California DMV suspends Waymo freeway rides after construction zone incursions
- California Bans Waymo From Every State Freeway Over Construction-Zone Incursions
- California DMV Bars Waymo From Freeways After Construction-Zone Incursions
- Waymo Loses California Highway Access Over Construction-Zone Incidents
- Waymo's Parking Tickets Expose the Gap in AI Judgment