Live  /  Temporal  /  Incident

Temporal: Customers in us-central1 and asia-southeast2 may experience a delay in workflow progress

Temporal · temporal.ioMajor incidentResolved2026-09-11 00:18 UTC
Public — what happened

Summary

Temporal reported a major incident in which some customers with namespaces in the us-central1 and asia-southeast2 regions saw workflows stall or fail to move forward, beginning on 2026-09-10 at 20:51 UTC. The company said a configuration change was behind the problem, causing certain workflow requests to go unprocessed. Temporal said it reversed the change and processing picked back up, and it is still checking its systems and cleaning up leftover effects. The incident is in a monitoring state, with a resolution time recorded as 2026-09-11 at 07:22.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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 38, 2026, our weekly internet health report.

The full archive is on the Temporal status & history page.

Related: Temporal status & history. SquidGrid is not affiliated with Temporal.