Temporal incident

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

Major Resolved View vendor source →

Temporal experienced a major incident on September 10, 2026 affecting us-central1 and asia-southeast2, lasting 10h 29m. The incident has been resolved; the full update timeline is below.

Started
Sep 10, 2026, 08:51 PM UTC
Resolved
Sep 11, 2026, 07:21 AM UTC
Duration
10h 29m
Detected by Pingoru
Sep 10, 2026, 08:51 PM UTC

Affected components

us-central1asia-southeast2

Update timeline

  1. identified Sep 10, 2026, 09:51 PM UTC

    Some customers with namespaces in the us-central1 and asia-southeast2 regions may experience errors and blocked progress on their workflows. We are currently rolling out a fix.

  2. monitoring Sep 10, 2026, 10:27 PM UTC

    The issue has been mitigated (as of 21:55 UTC) and we are actively monitoring the previously impacted environments.

  3. monitoring Sep 10, 2026, 10:29 PM UTC

    We are continuing to monitor for any further issues.

  4. monitoring Sep 10, 2026, 10:59 PM UTC

    While a small number of customer environments may still see some issues, mitigation has been in place and we continue to actively monitor.

  5. monitoring Sep 10, 2026, 11:29 PM UTC

    We are continuing to monitor for any further issues.

  6. monitoring Sep 10, 2026, 11:30 PM UTC

    We are continuing to monitor for any further issues.

  7. resolved Sep 11, 2026, 07:21 AM UTC

    The environment has been validated and all residual issues have been cleared. This incident is now resolved.