RewindexOutage eventsAug 6, 2025
Google Cloud outage, Aug 6, 2025
12 vendors posted 12 incidents between 03:00 and 09:00 UTC, against about 10 incidents from 8 vendors in the same hours on an ordinary week. 5 vendors named Google Cloud in 5 incidents (3 of them blamed it). Vendors reported a Google Cloud outage; Google Cloud’s own incident for this date is not in the archive.
Observed, not verified. A line means a vendor’s incident named another vendor, or started in the same window. It is not a proven cause.
Times are UTC; lags are from when the first vendor named Google Cloud.
- first vendor named Google Cloud 03:00
How it spread
Vendors that named Google Cloud, grouped by when they posted, and vendors that blamed one of the vendors Google Cloud took down. Solid lines: the vendor named the other. Dashed: same window, not named.
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"| k0Vendors that named Google Cloud
In their own words. “Blames” means a causal phrase sits next to the name (“due to”, “upstream provider”…).
Within an hour
4 vendors
- Minor incident
+0 min
Names Google Cloud
Temporal CloudCustomers in GCP us-central1 may experience elevated API latencies
…Customers in GCP us-central1 may experience elevated API latencies This incident has been resolved.…
- Critical incident
+11 min
Names Google Cloud
ConfluentPerformance degradation for resources in GCP us-central1-a
…Performance degradation for resources in GCP us-central1-a This incident has been resolved.…
- Major incident
+25 min
Blames Google Cloud
Grafana CloudIssues affecting prod-us-central-0
…Issues affecting prod-us-central-0 An incident from our CSP, Google Cloud, caused network issues impacting our customers on prod-us-central-0. The Grafana Cloud incident resolved shortly after the CSP…
- Incident, no impact listed
+52 min
Blames Google Cloud
JFrogJFrog Cloud Platform Service Disruption in GCP Central Region
…JFrog Cloud Platform Service Disruption in GCP Central Region Cloud Provider has confirmed that the issue has been resolved. No further service disruptions were observed since the last update. Cloud P…
1 to 4 hours later
1 vendor
- Minor incident
+1 h 18 min
Blames Google Cloud
BasetenGCP is reporting elevated packet loss in us-central1
…GCP is reporting elevated packet loss in us-central1 This incident has been resolved.…
Second hop: vendors that named another vendor
These incidents name a vendor other than Google Cloud, for example a messaging or CDN provider that was itself affected.
- Critical incident
+2 h 3 min
Blames Twilio
BrexSMS codes from Brex are unable to be sent to AT&T customers
…SMS codes from Brex are unable to be sent to AT&T customers Both Telesign and Twilio reported recovery at 11:12pm PT yesterday and resolved at 1:37am PT today.…
- Incident, no impact listed
+5 h 16 min
Blames Twilio
CloseCalling Service Disconnections
…Calling Service Disconnections This incident has been resolved. Our telephony provider, Twilio, has fixed the accounts affected so far and is actively working on preventing the problem from reoccurrin…
Same window, did not name anyone
5 incidents started during the event without naming Google Cloud or another vendor. Some are part of it, some are a normal day’s background (about 10 in these hours).
Show all 5
- +3 minMinor incident
- +21 minMinor incident
- +37 minMinor incident
- +42 minMajor incident
- +50 minMinor incident
Detected automatically from 9 status pages opening incidents in the peak hour (normally at most 6). Mentions are matched by name in each incident’s title and updates, then classified as cause, location or integration; quoted text is the vendor’s. Vendors that share one status page are shown once.