Waymo to recall software after robotaxis passed school buses

Waymo said it will file a voluntary software recall with the NHTSA after robotaxi incidents in Atlanta and Austin in which vehicles passed stopped school buses and students; while no injuries have been reported, NHTSA warned the agency is concerned about elevated crash risk given Waymo’s scale (about 2 million miles logged per week). Waymo attributes the behavior to software that momentarily slows or stops near buses then resumes, issued an update on Nov. 17, and is now responding to NHTSA’s request for detailed safety information and vehicle data by Jan. 20, 2026; Austin officials have asked Waymo to suspend service and the company faces potential civil penalties of up to $27,874 per violation per day (up to ~$139.4m) if it fails to comply, increasing regulatory, operational and reputational risk for Alphabet’s autonomous-vehicle unit despite its safety performance claims.

Analysis

Waymo is preparing a voluntary software recall with NHTSA after an Atlanta robotaxi on Sept. 22 passed a stopped school bus with its red lights and stop arm deployed and after Austin school officials reported at least 20 similar passings since August 2025; Waymo says no injuries were reported and issued a software update on Nov. 17 but acknowledged the vehicles can initially slow or stop near buses then resume. The company’s Chief Safety Officer framed the recall as a corrective safety action, but the NHTSA—citing Waymo’s fleet logging roughly 2 million miles per week—has expressed concern that the frequency of use raises the likelihood of similar prior incidents and has requested detailed safety documentation by Jan. 20, 2026. Failure to comply could expose Waymo (Alphabet) to civil penalties up to $27,874 per violation per day and a statutory maximum near $139.36 million, while Austin’s request to halt service (which Waymo denied) and public footage amplify reputational and operational risk. Waymo’s claim of lower injury-crash rates versus human drivers provides some mitigation, but repeated violations after earlier software claims indicate execution risk; investors should watch evidence of fix effectiveness, regulatory responses, and any localized service suspensions that could affect partner operations (Uber) and broader public acceptance.

Key Decisions for Investors

• Monitor NHTSA correspondence and the Jan. 20, 2026 deadline closely and consider reducing near-term net exposure to GOOGL/GOOG if the company fails to demonstrate a timely, verifiable fix or faces escalating enforcement,
• Require independent validation of Waymo’s corrective software (third-party audits, incident-rate metrics, or cleared NHTSA review) before increasing long-term Alphabet exposure,
• Assess short-term operational risk to partners and local service footprints (notably Uber in Austin and Atlanta) and consider hedging sector exposure ahead of further negative headlines or service suspensions,
• Use option-based hedges or position size limits rather than binary trading around this news, and re-evaluate once NHTSA’s probe outcomes and incident recurrence data are public