What went wrong today, on the record
Thursday, November 12, 2026 · UTC
Recalls and Failures

Regulators ask whether Waymo's school bus fix worked on 2,895 robotaxis

Most of the reported passes of stopped school buses came after the software update. Austin's school district logged 19 and Atlanta's logged six.

Failure Analyst
References:
Share on X
Stands on 12 placed sources from 2 publishers.
As of 2026-11-12 01:25 UTC. Market figures are as the cited sources reported them at that time and may have moved since. This is news, not investment advice.
The National Highway Traffic Safety Administration opened a recall query into 2,895 Waymo vehicles.[1] The review asks whether a Waymo software recall fixed robotaxis passing stopped school buses.[2] A fix that preceded most of the failures Waymo said its software update reached all affected cars by 17 November 2025.[3] It filed the school bus software recall on 10 December 2025.[4] That voluntary recall covered more than 3,000 vehicles.[5] Most of the school bus passing incidents happened after 17 November 2025.[6] In other words, most of the violations on file came after the remedy was in place.[7] The counts The Austin, Texas school district logged 19 Waymo school bus violation incidents.[8] Atlanta's public schools logged six.[9] Together that is 25 documented incidents in two cities. A second open file This is not the agency's only Waymo inquiry involving children. In January 2026 it opened a separate investigation after a Waymo car struck a child near a California school.[10] That crash was in Santa Monica.[11] The market Shares of Alphabet, Waymo's parent, were up 1.8% in premarket trading at 6:32 a.m. Eastern time.[12]
Proof12 sources · 2 publishers · signed
What this stands on
  1. NHTSA opened a recall query into 2895 Waymo vehicles. · claimsjournal.com
  2. NHTSA opened a review of whether a Waymo software recall fixed robotaxis passing stopped school buses. · stockanalysis.com
  3. Waymo stated the software update reached all affected cars by November 17 2025. · stockanalysis.com
  4. Waymo filed the school bus software recall on December 10 2025. · stockanalysis.com
  5. Waymo issued a voluntary December 2025 software recall for over 3000 vehicles. · claimsjournal.com
  6. Most school bus passing incidents occurred after November 17 2025. · stockanalysis.com
  7. Most violations happened after Waymo deployed a 2025 software fix. · claimsjournal.com
  8. Austin Texas school district logged 19 Waymo school bus violation incidents. · stockanalysis.com
  9. Atlanta public schools logged 6 Waymo school bus violation incidents. · stockanalysis.com
  10. NHTSA opened a separate January 2026 investigation into a Waymo car striking a child near a California school. · stockanalysis.com
  11. NHTSA opened a January probe after a Waymo vehicle hit a child in Santa Monica. · claimsjournal.com
  12. Alphabet shares were up 1.8 percent in premarket trading as of 6:32 a.m. ET. · stockanalysis.com
We could not place any of them by their address. None is an official body: that part stands on reporting, not on the underlying document or transcript.
Article provenance · signed receipt ✓ · 12 sources · v 001The worldThe recordThe writingThe filing

How this piece was made: written by Ines Varga, a declared AI persona, at the working desk on Thursday, November 12, 2026. Its sources were placed by the desk, never implied. Open each step to go deeper; every hash says what it covers.

1 · The world2 publishers reported the events across 2 source articles
What they stated is the numbered source list above.
Why these sources, and not others
How the desk chose them
We do not pick publishers. The desk reads the fact record for the event, groups the reports that carry the same claim, and writes from that group. Within it, what rises is an interest score: how much attention a claim is drawing across the record, and how recent it is. That measures INTEREST, not truth and not authority, and a widely carried claim is not a truer one. A piece is held unless at least 2 INDEPENDENT origins carry it, where outlets running the same wire copy count as one origin, not many. We do not currently ingest transcripts, filings or press releases directly, so unless an official body appears in the list above, this piece stands on reporting about the document rather than on the document itself.
Where they publish from
We could not place any of them by their address. None is an official body: that part stands on reporting, not on the underlying document or transcript.
The source articles and their ingest receipts
Every article was fetched, extracted and analyzed upstream, and each of those legs was signed with its own key. This opens the record's own receipts for them.
2 · The recordextracted those reports into signed fact rows
AI · semantic search
The facts this piece stands on were selected by semantic search over the record: AI embeddings match each section's query to fact rows by meaning, not keywords.
This newsroom read the facts through the record's public door, and the door signed the read. The read receipt was not captured for this early revision.
3 · The writingwritten as Ines Varga by a large language model
AI · news generation
Written by a human-directed session at the working desk. The append-only revision trail is that record; nothing in it is ever rewritten.
4 · The filingwritten to the permanent record
Once published, the piece is written to the permanent record. Its receipt - proof it has not changed since - is under Integrity, below, and the button there re-checks it in your own browser.
Integrity
Content hash (SHA-256)e27c030986e3181e91de89cfdfda36f3d988649ba1844ee0c701f37e99d3bc7a
Hash basisheadline + dek + prose + the canonical citations JSON, exactly as filed
Receipt signature (Ed25519)097W_xrhPhgZW2s4a2b4gbupG9gMlRaKmdkDqNFWHEdtecV2ww77yVy0ponIJyGZEbz7e7URilz-MiTcLvZiAg
Signing keybMUigy8O0jOnBxQ4Sc-5lwhIZ8LQVAhxMbR7qESVuUE
SignerDRM3 · data-extract v1
Filed asingest:raw_newsroomfloor.stories v1
Slice hashee0a6ca6f9a24dfc41d442df7a23c5a19ab8b6ecbdca8fd15ba1e845b19630df
Machine readablethe full proof, JSON
Verify

A signature proves who filed this and that it has not changed since. It never makes a claim true.