Business & Industry

Waymo Lost the Freeway in California, Then Lost San Francisco to Rain

California's regulator pulled driverless freeway driving after two construction-zone incidents, and Waymo went further than the order required. A day later, rain stopped the cars in San Francisco.

Daniel HarrisDaniel Harris
Heat: 1,150
Rain over converging freeway lanes with a striped barrier across the near lane

Dek: California's regulator pulled driverless freeway driving after two construction-zone incidents, and Waymo went further than the order required. A day later, rain stopped the cars in San Francisco.

What the California DMV order does to Waymo freeway driving

The California DMV issued an order on 11 November that became public on 17 November, and it removes Waymo's permission to run driverless cars on state freeways. The agency called the operation an imminent hazard to public safety.

That phrase is the strongest language a state DMV uses short of a suspension, and it lands on the part of Waymo's business that made airport runs and cross-city trips competitive with Uber and Lyft.

The restriction holds until Waymo shows the DMV that it has effective corrective actions in place. No date, no deadline, no automatic expiry.

The two November incidents behind the Waymo freeway stop

Two events in two days set this off, and both involve construction and road crews rather than speed or traffic.

Two failures, two causes.

Neither one was a crash.

On 5 November, three Waymo vehicles entered an active construction closure on U.S. Route 101 near Burlingame. On 6 November, another Waymo tried to get around California Highway Patrol vehicles that were running a traffic break on Interstate 280 in San Francisco.

Waymo says neither encounter produced an injury or a collision, and no regulator has reported one. The complaint is about where the cars went, not what they hit.

What makes it worse for Waymo is the history. The DMV says similar incursions happened on 18 May 2026 and that corrective actions were required after them. Less than six months later, the same failure mode reappeared on a different freeway.

Why the pause reaches every market, not just California

Waymo didn't stop at the state line. The company temporarily restricted freeway operations in all of its operating markets, not only California, and said it's working with the DMV and state officials to bring freeway service back.

That's a company decision, and it's the more interesting one, because nothing in the order forced it. A narrow reading would have kept freeway rides running in Phoenix and Austin with a California-shaped hole in the map.

Waymo continues normal service on surface streets, including in the Bay Area and Los Angeles. The cars still drive. They just don't get on the highway. Reporting from Engadget also notes that Waymo can keep testing freeways outside California with a human safety driver behind the wheel, which is a different activity from carrying passengers.

What riders lose when Waymo freeway routes disappear

Freeway access arrived in November 2025, and it changed what a Waymo ride was good for. An airport run on surface streets is a different product: slower, more exposed to traffic lights, and often pricier once the meter keeps running through a dozen intersections.

Riders in San Francisco will feel it first on trips to SFO and on any route that used to skip the 101 or the 280. So what does the extra time actually cost you? On a bad afternoon, enough that a human driver looks reasonable again.

Waymo hasn't published how much of its ride volume used freeways, and I wouldn't guess. The company also hasn't said whether pricing changes while the restriction lasts.

Why Waymo San Francisco paused on 18 November

The second setback has nothing to do with regulators. On 18 November, Waymo paused robotaxi service across Waymo San Francisco because of heavy rain and flooding, with an in-app message telling riders service was paused for weather until road conditions improved.

Before the pause, videos posted on X showed a Waymo stopped in a flooded crosswalk, and another idling in the middle of a road with a rider still inside. District 5 Supervisor Bilal Mahmood also reported the pause on X.

That's a very different failure from the freeway one. Construction closures are a mapping and planning problem. Standing water is a perception problem, and it gets worse in exactly the conditions where a rider most wants a car.

The flooding record behind the Waymo safety questions

Waymo has now paused for weather more than once, and the pattern is what makes riders nervous.

In December 2025, the company paused San Francisco service during a power outage. In May 2026 it recalled nearly 4,000 vehicles after a robotaxi drove into a flooded road in San Antonio, then paused service in Atlanta for the same flooding problem.

Meanwhile the freeway timeline reads like a cycle of its own. Waymo began freeway rides in November 2025, paused them voluntarily in May 2026, recalled about 3,800 vehicles in June, and resumed in July.

Software patch, new edge case, another patch. The long tail here is water and roadworks, not highway speed, which is the opposite of what most people assumed would slow robotaxis down.

What to watch next for robotaxi riders in California

Three things decide how long this lasts, and none of them are in Waymo's hands alone.

First, whether the California DMV accepts Waymo's corrective plan, and how specific the company is willing to be about what changed. A one-line statement about "improved construction zone handling" won't move a regulator that has already been burned twice.

Second, whether freeway service returns before the holiday quarter, when airport trips are the busiest and most lucrative part of the year.

Third, and least visible, whether surface-street-only routing shows up as longer wait times or higher prices. If it does, riders will notice before any regulator does.

For now the practical advice is dull. Check the app before an airport run, expect a slower route, and if it's raining hard in San Francisco, have a backup. The cars are still on the road. They're just not the ones you planned on.

Share This Story

Sources

Related AI News

A falling candlestick chart with a magnifying glass over ledger lines below it
Business & Industry

Nvidia Lost $900 Billion in a Week and the SEC Is Now Reading the Books

The stock fell about 14% on Friday and has now dropped for seven straight weeks. The SEC examination reported the same day is about the books, not about the founder.

Heat: 1,950
A globe grid with data center blocks and a toll barrier drawn across one route
Business & Industry

Trump Wants a Tax on Data Centers Abroad. Nobody Has Written One Yet.

The president told reporters on Friday that companies building AI capacity overseas would face a "tremendous tax." No rate, no bill and no agency has been named to collect it, which turns the announcement into a story about intent.

Heat: 1,880
Five boardroom chairs with the middle one empty and a chip on the table in front of them
Business & Industry

Nvidia Ran a Week Without Jensen Huang and the Numbers Didn't Notice

Nvidia lost its founder, refused to take him back, and then shipped the fastest product ramp in its history inside seven days. The interesting question isn't whether the quarter was good. It's who decides what happens next.

Heat: 1,830
Three satellites with solar arrays above a planet horizon, linked by a docking rail
Business & Industry

Google's Orbital Data Centers Have a Rocket Now. The Economics Are Still Missing.

Google has a rocket for its plan to put AI hardware in orbit. What it doesn't have yet is a launch price, a named satellite builder, or a way around the physics that makes space a hard place to run a server.

Heat: 1,240