Baseten: GCP is reporting elevated packet loss in us-central1
Google Cloud outage, Aug 6, 2025 · 12 vendors, 12 incidents
Baseten’s incident blames Google Cloud as the cause. (hop 1, posted +1 h 18 min vs the first vendor naming Google Cloud)
“…GCP is reporting elevated packet loss in us-central1 This incident has been resolved.…”
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["Google Cloud<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>4 vendors, 2 blamed Google Cloud<br/>Temporal Cloud, Confluent, Grafana Cloud, JFrog"]:::blames
root --> h1
h4["1 to 4 hours later<br/>1 vendor, 1 blamed Google Cloud<br/>Baseten"]:::blames
root --> h4
p0["Twilio<br/>posted +42 min, did not name Google Cloud"]:::timing
root -.-> p0
k0["Brex, Close<br/>+2 h 3 min to +5 h 16 min"]:::hop2
p0 -->|"blamed Twilio"| k0
me["Baseten (this incident)<br/>posted +1 h 18 min"]:::me
h4 --- meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Timeline of updates
- resolved
This incident has been resolved.
From Baseten’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.baseten.co (opens in new tab).