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 Provider (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

Oct 27, 2025

No incidents reported today.

Oct 26, 2025

No incidents reported.

Oct 25, 2025

No incidents reported.

Oct 24, 2025

No incidents reported.

Oct 23, 2025

Increased latencies for schedules, batches and versioning APIs in us-east-1

Resolved - This incident has been resolved.
Oct 23, 20:43 UTC

Update - We scaled worker pods and pollers, which reduced the latencies back to normal.
Oct 23, 20:42 UTC

Investigating - We are currently investigating the issue.
Oct 23, 19:13 UTC

Oct 22, 2025

Namespaces in aws us-west-2 experiencing increased latencies

Resolved - Latencies appear to have recovered
Oct 22, 02:15 UTC

Investigating - We are currently investigating this issue
Oct 22, 01:51 UTC

Oct 21, 2025

Intermittent failures attempting to add us-east-2 replicas to existing namespaces

Resolved - At around 2025-10-20 UTC 23:00, some customer requests to add an aws us-east-2 replica to an existing namespace failed. We successfully retried these failed requests around 2025-10-21 UTC 05:00
Oct 21, 03:00 UTC

Oct 20, 2025

Service disruptions in AWS us-east-1

Resolved - Update: Our systems are showing full recovery across all previously impacted namespaces. Namespaces that failed over during the incident have not yet been failed back. We are working directly with a small number of customers on follow-up recovery steps for issues indirectly related to this incident.

Update [ 10/22/2025 - 21:00:00Z ] - All multi-region namespaces have been failed back to their preferred region (excluding any namespaces that were specifically requested to not fail back on)
Oct 20, 19:30 UTC

Update - We continue to see recovery and are actively monitoring stability in the affected region
Oct 20, 19:00 UTC

Update - All pre-existing multi-region and multicloud namespaces to unaffected regions have been failed-over.

We are seeing major improvements in networking in the region. We will continue monitoring the situation until full recovery.
Oct 20, 18:35 UTC

Update - Investigating service disruptions due to ongoing AWS outage in US-East-1. See: https://health.aws.amazon.com/health/status

We are experiencing network instability in us-east-1. Some customers may see increased latency and error rates in this region.

We are currently failing over pre-existing multi-region and multi-cloud namespaces to unaffected regions.
Oct 20, 16:50 UTC

Update - Investigating service disruptions due to ongoing AWS outage in US-East-1. See: https://health.aws.amazon.com/health/status

We are currently seeing network instability in us-east-1. Some customers may see increased latency and error rates in this region.
Oct 20, 16:35 UTC

Monitoring - AWS is observing services recovering, see: https://health.aws.amazon.com/health/status

Workflow operations are currently not affected.
Oct 20, 10:22 UTC

Identified - Investigating service disruptions due to ongoing AWS outage in US-East-1. See: https://health.aws.amazon.com/health/status

There is a loss of OpenMetrics endpoint data for namespaces in us-east-1

Workflow operations are currently not affected.
Oct 20, 08:11 UTC

Update - Investigating service disruptions due to ongoing AWS outage in US-East-1. See: https://health.aws.amazon.com/health/status

Workflow operations are currently not affected.
Oct 20, 08:07 UTC

Investigating - Investigating increased latency in control-plane operations for some customers in AWS US-EAST-1 due to ongoing cloud operational issue. Workflow operations are not impacted.
Oct 20, 07:42 UTC

Oct 19, 2025

No incidents reported.

Oct 18, 2025

No incidents reported.

Oct 17, 2025

No incidents reported.

Oct 16, 2025

No incidents reported.

Oct 15, 2025

No incidents reported.

Oct 14, 2025

No incidents reported.

Oct 13, 2025

No incidents reported.