Waymo Robotaxi Recall: Why Nearly 3,900 Self-Driving Cars Got Pulled

If you’ve ridden in a Waymo lately, you probably trusted it to handle one basic thing: not drive you into a construction site. Most of the time, that’s exactly what happens. But Waymo just filed a recall covering nearly 3,900 of its robotaxis after a handful of them did the opposite, rolling into active freeway work zones when they should’ve steered clear. The Waymo robotaxi recall isn’t huge in numbers, but it touches a nerve, because the whole pitch of a driverless car is that it pays attention so you don’t have to.

What actually triggered the Waymo robotaxi recall

The recall was filed voluntarily with the National Highway Traffic Safety Administration, and it traces back to 13 known incidents. Six happened in Phoenix back in April, and seven more showed up around the San Francisco Bay Area on a single day, May 18. In each case, a Waymo car’s software didn’t correctly read certain construction-related road closures on the freeway. That meant the vehicle could keep moving through a work zone at highway speed. That’s the kind of mistake that makes people uneasy, and honestly, it should.

It’s the fifth-generation software, not the whole fleet

Context matters here. The recall applies to cars running Waymo’s fifth-generation automated driving system. Waymo says it’s already building a fix and has pulled back on how much its robotaxis use freeways until that update ships. So this isn’t every Waymo everywhere grinding to a halt. It’s a targeted software patch for one specific failure mode, and the company caught it through its own incident reporting rather than waiting for something worse.

Two recalls in a month is the part worth watching

This is Waymo’s second recall in just over a month. Back in May, the company pulled around 3,800 cars after a software issue could let them drive into flooded roads and standing water. Two software recalls inside of five weeks is a pattern, and for a lot of riders it raises an obvious question: how solid is this tech, really? That’s a fair thing to ask, especially as these cars rack up more miles in cities where the rest of us are just trying to get to work.

Why a robotaxi recall isn’t your typical car recall

When a regular car gets recalled, you usually book a service appointment and someone swaps out a part. A robotaxi recall is mostly a software update pushed to the fleet, closer to your phone getting a patch than your car going into the shop. That’s faster and a lot cheaper. The catch is that the fix is only as good as the code behind it, and these problems keep surfacing in messy, real-world edge cases that are genuinely hard to test for ahead of time. A closed freeway lane in Phoenix doesn’t look like a closed lane in San Francisco, and the software has to nail both.

What it means for the driverless rollout

Waymo is still the clear leader in driverless rides, running paid trips across several US cities, and none of this looks likely to slow that down. But it lands at a moment when AI is being trusted with more and more real-world decisions, and every recall chips away at the public’s patience a little. Regulators are watching, riders are watching, and competitors chasing the same market are watching closely too.

So, should you still hop in one?

Self-driving cars are still, statistically, holding up fine next to the daily chaos of human drivers. And a recall like this is arguably the system working the way it’s supposed to: incidents get logged, the regulator gets notified, and a fix goes out to the whole fleet at once. The uncomfortable truth is that this is what progress looks like for autonomous tech right now, a steady drip of edge cases getting caught and patched out in the open. If you’re climbing into a Waymo this week, freeway behavior is the exact thing the company is reworking. As of June 2026, the numbers here (about 3,900 cars, 13 incidents) come straight from Waymo’s NHTSA filing, and they could shift as more details come out.