DEPLOYDatabase

Revision history

Cruise revision history

Every change to this record is dated, sourced, and independently verified where marked. Nothing is edited silently.

Tracked since
Nov 1, 2021
Recorded events
16
Independently verified
3
Last verified change
Jun 11, 2026

Company

Back to Cruise

Activity

June 2026

  1. MediaJun 11, 2026

    105 Minutes of Cruise Fully Autonomous Driving in San Francisco

May 2026

  1. CreatedMay 26, 2026

    Added to the verified registry

November 2024

  1. IncidentNov 14, 2024

    Cruise admits a false report to a federal investigation; $500K DOJ deferred-prosecution...

September 2024

  1. IncidentSep 30, 2024

    NHTSA fines Cruise $1.5M for failing to fully report the Oct 2023 pedestrian-dragging...

August 2024

  1. IncidentAug 22, 2024

    Cruise recalls its entire 1,194-vehicle fleet over unexpected hard braking

  2. IncidentAug 9, 2024

    Software May Cause Unexpected Braking

November 2023

  1. IncidentNov 7, 2023

    Cruise recalls 950 ADS units (NHTSA 23E-086) over post-crash pullover behavior

  2. IncidentNov 7, 2023

    ADS Software May Improperly Respond After a Crash

October 2023

  1. IncidentOct 24, 2023

    California DMV suspends Cruise's driverless deployment and testing permits as not safe...

  2. IncidentOct 2, 2023

    Cruise driverless robotaxi dragged a pedestrian ~20 feet in San Francisco

August 2023

  1. IncidentAug 17, 2023

    Cruise robotaxi collided with an SF fire truck responding to an emergency; one passenger...

April 2023

  1. IncidentApr 3, 2023

    Cruise recalls 300 ADS units (NHTSA 23E-029) over articulated-vehicle misprediction

  2. IncidentApr 3, 2023

    ADS Software Error May Cause Crash

August 2022

  1. IncidentAug 29, 2022

    Cruise recalls 80 ADS units (NHTSA 22E-072) over unprotected-left hard-braking software

June 2022

  1. DeploymentJun 1, 2022

    Cruise Origin at San Francisco, California, USA

November 2021

  1. DeploymentNov 1, 2021

    Cruise AV (Chevrolet Bolt) at San Francisco

How this log works

This timeline aggregates every dated signal on the record (creation, deployments across the company's models, verified media, incidents, and Arc G field changes), newest first. A verified event is independently confirmed; an unverified one is recorded but not yet field-verified. The Arc G field-change log is forward-only: it accrues from Arc G adoption (2026-06-04) and records material changes as they flow through the updateEntityField chokepoint. Nothing is edited silently.

Machine-readable: /companies/cruise/history.md + REST /v1/companies/ce8ff680-3fe7-4398-b31b-f85dc3073f3a/history.