Skip to content
OutageDeck

Incident detail

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

Resolved incidentMinor

Timeline window

to

Outage alerts

Get alerted the next time Temporal Cloud breaks

Free email alerts for up to 5 providers. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Set up free alertsHow Temporal Cloud alerts work

Timeline

Incident updates

Every update Temporal Cloud posted, oldest to newest, exactly as it appeared on their official status page.

  1. Investigating

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

  2. 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

  3. 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.

  4. 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.

  5. Identified

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

  6. Monitoring

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

  7. Monitoring

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

  8. 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.

  9. 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.

Keep exploring

More from Temporal Cloud

Neighboring incidents on Temporal Cloud's timeline and the rest of their record on OutageDeck.

← Older incident

Some customers in us-west-2 may experience elevated rate of API errors and high latency

Newer incident →

Some customers in GCP us-east4 experienced elevated API latencies

All Temporal Cloud incidentsTemporal Cloud live status