Incident · Malfunction
Waymo suspended Atlanta robotaxi service after a robotaxi was stuck amid flooding (May 2026)
In May 2026, Waymo suspended robotaxi operations in Atlanta after at least one robotaxi was reported stuck in the city amid flooding conditions. The suspension was part of a broader effort to address Waymo robotaxis driving into flooded areas, which also affected San Antonio. The company had been working on software to help its fleet avoid flooded areas.
Occurred 2026-05-21 · Waymo Driver 6th-gen at Atlanta · Waymo
Machine-readable surfaces
- Markdown mirror: /incidents/waymo-atlanta-flood-suspension-2026-05.md
- JSON-LD: embedded in this page’s head
- REST API: /v1/incidents/f9afb254-7856-45b9-b570-f0d1333eeaa8
- Data documentation: /data
- Query this programmatically: Deploy MCP
Outcomes (1)
- no outcomeinferred
Revision history (1)
- 2026-06-05 · outcome_class
Outcome rows carry verification_posture independently. Revision events carry basis (verified_court_filing, verified_insurance, reported_press, estimate, undisclosed). The framework records outcomes only when verifiable; absence is honest absence, not a claim of no-impact.
Sources (5)
- TechCrunch — Waymo pauses Atlanta service as robotaxis keep driving into floods · https://techcrunch.com/2026/05/21/waymo-pauses-atlanta-service-as-its-robotaxis-keep-driving-into-floods/ · 2026-05-21
- TechCrunch — Atlanta suspension referenced in freeway-suspension coverage · https://techcrunch.com/2026/05/21/waymo-halts-freeway-rides-after-robotaxis-struggle-in-construction-zones/ · 2026-05-21
- https://www.ajc.com/business/2026/05/waymo-atlanta-operations-paused-after-robotaxis-got-stuck-in-flash-floods/ · 2026-05-22
- https://www.atlantanewsfirst.com/2026/05/28/theyre-back-waymos-return-atlanta-streets-after-pause-due-flood-hazard/ · 2026-05-28
- https://www.11alive.com/article/news/local/a-journalist-in-waymo-gets-stuck-in-the-atlanta-flood/85-463f9e42-6c60-46e6-b090-55334a544fe6
Response (1)
Waymo · operator · 2026-05-21
As reported by TechCrunch (May 21, 2026): Waymo suspended Atlanta operations to address flooding-related performance issues, following its earlier San Antonio pause and recall.
Common questions
- What happened in Waymo suspended Atlanta robotaxi service after a robotaxi was stuck amid flooding (May 2026)?
- In May 2026, Waymo suspended robotaxi operations in Atlanta after at least one robotaxi was reported stuck in the city amid flooding conditions. The suspension was part of a broader effort to address Waymo robotaxis driving into flooded areas, which also affected San Antonio. The company had been working on software to help its fleet avoid flooded areas.
- When did this incident occur?
- The incident is recorded as occurring on May 21, 2026 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.
- What robot was involved in Waymo suspended Atlanta robotaxi service after a robotaxi was stuck amid flooding (May 2026)?
- Waymo Driver 6th-gen by Waymo is the recorded robot involved in this incident at Atlanta.
- Has anyone responded to Waymo suspended Atlanta robotaxi service after a robotaxi was stuck amid flooding (May 2026)?
- 1 response is recorded on the DEPLOY registry, from Waymo. Each response is append-only with structured provenance.
- What is the current status of Waymo suspended Atlanta robotaxi service after a robotaxi was stuck amid flooding (May 2026)?
- This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.
Methodology: Verified · 5 sources (no primary) · last reviewed 2026-06-24
Verification posture
Verified
Low confidence
Review state
Stable
Last reviewed 2026-06-24
Sources by quality tier
- 3
- unclassified
- Unclassified source
- 2
- secondary-industry-publication
- Industry publication
The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.
Methodology surface for Waymo suspended Atlanta robotaxi service after a robotaxi was stuck amid flooding (May 2026).Deploy Watch
Track this incident.
We notify you when the regulator updates the record, the remedy status changes, or a related incident surfaces.
Canonical ID f9afb254-7856-45b9-b570-f0d1333eeaa8