All Systems Operational

Amazon Web Services (AWS) Operational
ap-northeast-1 Operational
ap-northeast-2 Operational
ap-south-1 Operational
ap-south-2 Operational
ap-southeast-1 Operational
ap-southeast-2 Operational
ca-central-1 Operational
eu-central-1 Operational
eu-west-1 Operational
eu-west-2 Operational
sa-east-1 Operational
us-east-1 Operational
us-east-2 Operational
us-west-2 Operational
Google Cloud Platform (GCP) Operational
asia-south1 Operational
europe-west3 Operational
us-east4 Operational
us-central1 Operational
us-west1 Operational
Global Services Operational
Web UI Operational
Cloud Ops API Operational
Metrics Operational
Namespace Management Operational
Auth(n)/Auth(z) Operational
Audit Logging Operational
Export History Operational
Billing Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
May 9, 2026
Some customers in AWS us-east-1 may experience elevated API latencies
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.
May 9, 03:56 UTC
Update - 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.
May 8, 17:37 UTC
Update - We continue to monitor the situation and the service stability has been maintained.
May 8, 12:29 UTC
Monitoring - We continue to work closely with AWS and monitor the situation. There are no new developments at this time, and service remains stable.
May 8, 09:27 UTC
Update - We continue to stay closely aligned with AWS and are actively monitoring the environment to ensure ongoing stability.
May 8, 07:43 UTC
Update - 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.
May 8, 03:40 UTC
Update - We are continuing to work closely with AWS as they address the underlying issue. We are also actively monitoring the health of impacted namespaces.
May 8, 02:55 UTC
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
May 8, 01:50 UTC
Investigating - Some customers in AWS us-east-1 may experience elevated API latencies.
May 8, 01:14 UTC
May 8, 2026
May 7, 2026

No incidents reported.

May 6, 2026

No incidents reported.

May 5, 2026
Some customers in us-west-2 may experience elevated rate of API errors and high latency
Resolved - This incident has been resolved.
May 5, 21:46 UTC
Update - Some customers may have experienced additional latencies and errors during this period (17:40 - 18:01 UTC) when we applied additional mitigation.
May 5, 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.
May 5, 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.
May 5, 09:24 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
May 5, 07:50 UTC
Update - We continue working to mitigate the issue.
May 5, 07:39 UTC
Identified - We are working to mitigate the issue. Error rates are recovering.
May 5, 07:12 UTC
Update - This is still in investigation
May 5, 06:22 UTC
Investigating - We are currently investigating the issue.
May 5, 05:43 UTC
Some customers in AWS us-east-1 may be seeing a small number of gRPC UNIMPLEMENTED errors
Resolved - This incident has been resolved.
May 5, 00:36 UTC
Monitoring - The issue has been identified as being related to a proxy node replacement rollout which has been halted. We are currently monitoring the region but do not anticipate any new errors at this point.
May 4, 23:23 UTC
Investigating - We are currently investigating a small number of gRPC UNIMPLEMENTED errors being returned in the AWS us-east-1 region.
May 4, 22:50 UTC
May 4, 2026
May 3, 2026

No incidents reported.

May 2, 2026

No incidents reported.

May 1, 2026

No incidents reported.

Apr 30, 2026

No incidents reported.

Apr 29, 2026

No incidents reported.

Apr 28, 2026

No incidents reported.

Apr 27, 2026

No incidents reported.

Apr 26, 2026

No incidents reported.

Apr 25, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage

2025 © Temporal Technologies. All Rights Reserved.

Privacy Policy Terms of Service Code of Conduct