Temporal incident
Some customers in us-west-2 may experience elevated rate of API errors and high latency
Temporal experienced a major incident on May 5, 2026 affecting us-west-2, lasting 16h 2m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 05, 2026, 05:43 AM UTC
We are currently investigating the issue.
- investigating May 05, 2026, 06:22 AM UTC
This is still in investigation
- identified May 05, 2026, 07:12 AM UTC
We are working to mitigate the issue. Error rates are recovering.
- identified May 05, 2026, 07:39 AM UTC
We continue working to mitigate the issue.
- monitoring May 05, 2026, 07:50 AM UTC
A fix has been implemented and we are monitoring the results.
- monitoring May 05, 2026, 09:24 AM UTC
API latencies and error rates have remained stable after a fix in history service and we continue to monitor the situation.
- monitoring May 05, 2026, 04:47 PM UTC
We are continuing to monitor the affected cell and have kept our status page in a monitoring state while we validate stability. As a precaution, Multi-region Namespace traffic has been failed over to secondary regions, where it continues to be served normally. While we complete stabilization work, Multi-region Namespaces will continue running from secondary regions. Our current priority is to ensure the affected cell is stable and operating normally. Once confirmed, and the incident is resolved, we will restore Multi-region Namespace traffic to primary regions. For Multi-region Namespaces failed over by Temporal, we will manage fail back. For manually failed over namespaces, customers can initiate fail back once the incident is resolved.
- monitoring May 05, 2026, 08:09 PM UTC
Some customers may have experienced additional latencies and errors during this period (17:40 - 18:01 UTC) when we applied additional mitigation.
- resolved May 05, 2026, 09:46 PM UTC
This incident has been resolved.