Live / Incidents / Temporal
Temporal: Customers in us-central1 and asia-southeast2 may experience a delay in workflow progress
Temporal · temporal.ioImpact: majorResolved2026-09-11 00:18 UTC
Public — what happened
Summary
A configuration change affecting namespaces in the us-central1 and asia-southeast2 regions resulted in some workflow requests not being processed as expected. The change was rolled back and workflow processing resumed. We are continuing to validate the environment and clear any residual issues, and will provide further updates as that work completes.
Timeline
- Started — 2026-09-10 20:51 UTC
- Last update — 2026-09-11 00:18 UTC
- Resolved — 2026-09-11 07:22 UTC
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 →