Temporal Status

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

Past Incidents

May 21, 2026

No incidents reported today.

May 20, 2026

No incidents reported.

May 19, 2026

No incidents reported.

May 18, 2026

No incidents reported.

May 17, 2026

No incidents reported.

May 16, 2026

No incidents reported.

May 15, 2026

Temporal UI was unable to display human readable execution details

Resolved - A change to the Cloud UI caused a breaking change to the codec server endpoint. This impacted the UI for some customers for roughly 1.5 hours between May 15, 2026, 11:42:57 AM PDT and May 15, 2026 1:14:53 PM PDT. The change was rolled back and the UI is back to normal operating conditions.
May 15, 18:30 UTC

May 14, 2026

No incidents reported.

May 13, 2026

Some customers in GCP us-east4 experienced elevated API latencies

Resolved - Some customers in GCP us-east4 experienced elevated API latencies for two minutes between 13:03:30 and 13:05:30 UTC. The issue is currently resolved with latencies back to baseline.
May 13, 16:43 UTC

May 12, 2026

Some customers in GCP us-east4 experienced elevated API latencies

Resolved - Some customers in GCP us-east4 experienced elevated API latencies for two minutes between 12:38 and 12:40 UTC. The issue is currently resolved with latencies back to baseline.
May 12, 12:38 UTC

May 11, 2026

No incidents reported.

May 10, 2026

No incidents reported.

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.