Live / Temporal / Incident
Temporal: Elevated GCP storage latency in us-central1 – precautionary namespace failover
Temporal · temporal.ioResolved2026-10-09 02:17 UTC
Public — what happened
Summary
Temporal said it was watching slower-than-normal response times from Google Cloud's storage service in the us-central1 region starting at 21:53 UTC on October 8, 2026. As a safety step, the company moved multi-region namespaces in that region over to their backup regions, and it reported seeing no effect on running workflows. By 01:04 UTC on October 9, Temporal said storage performance had recovered and it planned to shift those namespaces back, and the incident was marked resolved at 02:17.
Timeline
- Started — 2026-10-08 21:53 UTC
- Investigating — 2026-10-08 21:53 UTC
- Monitoring — 2026-10-09 01:04 UTC
- Resolved — 2026-10-09 02:17 UTC · 4h 25m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Temporal against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Temporal: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Temporal report →
More from Temporal
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.