Temporal Status

Resolved: AWS has resolved the underlying infrastructure issues in us-east-1. We have marked the region as healthy and are failing our AWS us-east-1 primary multi-region replication customers back into this region.

Monitoring: AWS continues to work to resolve the underlying infrastructure issues in us-east-1. We continue to monitor our service closely, and we have not observed any new impact.

Monitoring: We continue to monitor the situation and the service stability has been maintained.

Monitoring: We continue to work closely with AWS and monitor the situation. There are no new developments at this time, and service remains stable.

Identified: We continue to stay closely aligned with AWS and are actively monitoring the environment to ensure ongoing stability.

Identified: We are continuing to work closely with AWS as they address the underlying issue and are actively monitoring impacted namespaces for stability. We have also confirmed multi-region replication-enabled namespaces are in their expected replication configuration.

Identified: We are continuing to work closely with AWS as they address the underlying issue. We are also actively monitoring the health of impacted namespaces.

Identified: We have proactively failed over all impacted AWS us-east-1 multi‑region replication enabled primary namespaces due to ongoing AWS incident https://health.aws.amazon.com/health/status?path=open-issues

Investigating: Some customers in AWS us-east-1 may experience elevated API latencies.

Resolved: This incident has been resolved.

Monitoring: Some customers may have experienced additional latencies and errors during this period (17:40 - 18:01 UTC) when we applied additional mitigation.

Monitoring: 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: API latencies and error rates have remained stable after a fix in history service and we continue to monitor the situation.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: We continue working to mitigate the issue.

Identified: We are working to mitigate the issue. Error rates are recovering.

Investigating: This is still in investigation

Investigating: We are currently investigating the issue.