Some customers may have experienced additional latencies and errors during this period (17:40 - 18:01 UTC) when we applied additional mitigation.
Posted May 05, 2026 - 20:09 UTC
Update
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.
Posted May 05, 2026 - 16:47 UTC
Update
API latencies and error rates have remained stable after a fix in history service and we continue to monitor the situation.
Posted May 05, 2026 - 09:24 UTC
Monitoring
A fix has been implemented and we are monitoring the results.
Posted May 05, 2026 - 07:50 UTC
Update
We continue working to mitigate the issue.
Posted May 05, 2026 - 07:39 UTC
Identified
We are working to mitigate the issue. Error rates are recovering.
Posted May 05, 2026 - 07:12 UTC
Update
This is still in investigation
Posted May 05, 2026 - 06:22 UTC
Investigating
We are currently investigating the issue.
Posted May 05, 2026 - 05:43 UTC
This incident affected: Amazon Web Services (AWS) (us-west-2).