Temporal incident
Customers in us-central1 and asia-southeast2 may experience a delay in workflow progress
Resolved after 10 hours 29 minutes, affecting us-central1 and asia-southeast2, on September 10, 2026.
The environment has been validated and all residual issues have been cleared. This incident is now resolved.
Affected components
Update timeline
- 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.
- 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.
- monitoring Sep 10, 2026, 10:29 PM UTC
We are continuing to monitor for any further issues.
- 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.
- monitoring Sep 10, 2026, 11:29 PM UTC
We are continuing to monitor for any further issues.
- monitoring Sep 10, 2026, 11:30 PM UTC
We are continuing to monitor for any further issues.
- 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.
Your product runs on more than Temporal
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services