AV Vendor Risk: Waymo Recall & 3PL Audit Checklist

In the two-week window spanning May 11–28, 2026, three separate events converged into an immediate vendor risk trigger for any Texas Triangle logistics operator with autonomous vehicle capacity in their plans. First, Waymo filed a voluntary software recall covering 3,791 autonomous vehicles — its 5th and 6th generation models — after a robotaxi drove through a flooded roadway in San Antonio. Second, according to Business Insider, Waymo temporarily suspended rider service in six cities — including San Antonio, Dallas, Houston, and Austin — and halted highway rides across all operating regions during concurrent late-May weather events. Third, Texas Senate Bill 2807 (89R) — establishing a mandatory authorization framework for commercial AV operations on Texas roads — became enforceable on May 28, 2026.

None of these events would be disqualifying on its own. Together, they change the vendor qualification calculus for any 3PL treating autonomous fleet capacity as a near-term operational resource.

What Is Confirmed and What Is Not

Confirmed:

The NHTSA recall was filed May 11, 2026. NBC DFW confirmed it through an NHTSA letter obtained by NBC Chicago. The filing covers vehicles whose software may have allowed navigation into flooded roads.
Service suspensions across six cities are confirmed by Business Insider, with Texas Triangle markets including San Antonio, Dallas, Houston, and Austin among those affected.
Texas SB 2807 is confirmed through TxDMV.gov, the administering agency.
As of late May 2026, Waymo had nearly 600 autonomous vehicles registered in Texas — more than any competitor — according to TechCrunch citing TxDMV data. Named competitors in the Texas registry include Avride, Nuro, Tesla, and Zoox.

Not confirmed:

The specific software mechanism that failed to detect flooded road conditions has not been technically described in any public filing or company statement.
Whether Waymo's service suspensions were caused solely by the flooding incident or involved additional contributing factors is not independently confirmed.
The full geographic scope and duration of the highway ride suspension are not corroborated beyond Business Insider.
Whether NHTSA opened a formal investigation beyond receiving the recall filing is unknown.
No Waymo official statement has been included in available sourcing.

The Dependency This Exposes for Texas 3PLs

Most 3PLs evaluating autonomous fleet partnerships are treating AV capacity the way they treat any new carrier: verify rates, run a pilot, confirm insurance, and move forward. That model misses two failure modes this incident makes visible.

Failure Mode 1: Weather-triggered full-fleet suspension. A traditional carrier hit by bad weather loses some trucks and some drivers. An AV fleet can go offline at the platform level. When Waymo suspended highway rides across all operating regions — not just in affected storm areas — it created a total-capacity gap for any shipper or logistics operator relying on that network. The recall covered 3,791 vehicles simultaneously. That is not a localized disruption.

Failure Mode 2: Regulatory compliance disruption mid-contract. Under Texas SB 2807, commercial AV operators must hold active state authorization to operate on Texas roads. If a software recall triggers a compliance review — or if a vendor's authorization is contingent on software versions currently under recall — a logistics operator holding a capacity agreement with that vendor could find their contracted fleet legally sidelined while remediation is pending.

Texas averages dozens of flash-flood events annually across the Triangle metros. San Antonio, Houston, and the Austin corridor rank among the highest-frequency flash-flood areas in the continental United States. Weather-triggered service interruptions are not edge cases in Texas — they are seasonal operating conditions.

The New Texas AV Law Changes the Vendor Qualification Standard

Prior to May 28, 2026, Texas had no centralized mandatory authorization framework for commercial AV operations. Operators navigated a patchwork of local permissions and NHTSA voluntary frameworks. SB 2807 ended that.

The Texas DMV launched a public-facing AV tracker tool as part of the new law. Any 3PL evaluating an AV vendor can now verify that vendor's registration status directly through TxDMV.gov. This is a contract risk gate, not an administrative formality.

Before signing any autonomous fleet capacity agreement in Texas, a 3PL needs answers to three questions:

Does this vendor hold active authorization under SB 2807?
Is that authorization current and not contingent on software remediation still under development?
What happens to the vendor's operating authorization if a recall triggers a regulatory review?

If those answers are not in the contract or vendor disclosure documents, the 3PL is absorbing compliance risk that belongs on the vendor side.

What This Means for TMS, EDI, and Fallback Capacity Planning

Most regional 3PLs integrate carrier capacity through a Transportation Management System (TMS) and exchange shipment data via EDI or API. AV fleet vendors are increasingly offering similar integration paths. The operational risk is not the technology integration itself — it is what your TMS does when that carrier feed goes dark.

If a contracted AV fleet suspends service and your TMS has no fallback carrier logic for that lane, shipments stop moving until a human resolves the exception. In flash-flood conditions affecting multiple lanes simultaneously, that exception queue grows fast.

Three integration dependencies to audit:

TMS fallback carrier logic: Does your system automatically reroute to backup carriers when an AV vendor shows unavailable, or does it queue an exception and wait?
EDI/API service status feeds: Does your AV vendor push real-time availability updates to your systems, or do you discover the suspension after a delivery failure?
SLA and force majeure language: Does your current or proposed agreement define weather-triggered suspension as a force majeure event — releasing the vendor from SLA penalties? If so, who carries SLA liability with your customers?

Waymo's multi-city Texas suspension in May 2026 demonstrated exactly this failure pattern in a live operating environment.

What to Audit Before Your Next AV Capacity Commitment

If your operation has existing AV vendor agreements or is evaluating one, run this checklist before the next contract signature or renewal:

Authorization status: Confirm the vendor holds active authorization under Texas SB 2807 via the TxDMV AV tracker. Do not rely on verbal confirmation.
Recall disclosure: Ask whether the vendor has any open NHTSA recall filings, and whether current operating authorization is contingent on unfinished software remediation.
Weather suspension scope: Determine what triggers a service suspension — localized (one city, one route) or platform-wide (all vehicles, all regions).
Notice and fallback protocol: What is the vendor's contractual obligation to notify you of a suspension, and within what timeframe? What is your fallback carrier for each AV-served lane?
SLA force majeure carve-outs: Map every clause that releases the AV vendor from delivery SLA obligations. Confirm those carve-outs do not automatically flow through to your customer contracts.
EDI/API status integration: Verify that vendor availability status reaches your TMS in real time — not after a missed delivery trigger.

What to Watch Next

As of late May 2026, Waymo leads all registered Texas AV operators with nearly 600 vehicles, followed by Avride, Nuro, Tesla, and Zoox — though competitor fleet sizes lack independent corroboration beyond TxDMV registry data.

Three signals worth tracking over the next 90 days:

1. Waymo's corrective action disclosure. The software fix, its validation method, and the timeline for returning suspended vehicles to service have not been publicly confirmed. That disclosure will clarify whether the weather-detection gap was a narrow edge case or a broader architectural limitation.
2. NHTSA's response. A formal investigation beyond receiving the recall filing has not been confirmed. If one opens, it adds regulatory uncertainty for any vendor operating under an open filing.
3. TxDMV authorization updates. Monitor the public AV tracker for authorization status changes among competitors, particularly operators whose authorization may be conditioned on software versions currently under review.

The question of whether AVs will eventually handle Texas weather reliably is not the right question for a logistics operator today. The right question is whether the current operational reliability of available AV vendors is sufficient to carry contractual delivery commitments across a Texas Triangle summer storm season. The May 2026 record says that answer is still being written.