Skip to content

Incident detail

Increased Connectivity issues in US-EAST-1 (N. Virginia)

Resolved incidentMajor1 region: us-east-1

Timeline window

to

Get alerted the next time AWS breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. Investigating

    We are investigating reports of Connectivity issues in the US-EAST-1 Region. IAM Identity center sign-in requests and AWS SignUp are also impacted at this time.

  2. Monitoring

    We continue to investigate Connectivity issues in the US-EAST-1 Region. IAM Identity center sign-in requests and AWS SignUp are impacted at this time.

    We can confirm errors when attempted to authenticate when using identity center or when using services that rely on IAM Identity center. For Kiro users, logins from social sign in methods are not impacted at this time. There are no workarounds for impacted customers.

  3. Monitoring

    We are seeing early signs of recovery for authentication via IAM Identity Center and SignUp.

  4. Monitoring

    We can confirm recovery for most AWS Services. We have fully mitigated the issue authentication errors from IAM Identity Center that was impacting Kiro, Connect, and other services which rely on IAM Identity Center for authentication.

    We continue to investigate an issue that is affecting a subset of Network Load Balancers in a single cell, in a single Availability Zone (use1-az1) in the US-EAST-1 Region. For customers who need immediate resolution, we recommend creating a new NLB with targets in multiple Availability Zones. We are actively working on multiple parallel paths to mitigate the issue. We will provide an update by 7:30 AM, or sooner if we have additional information to share.

  5. Monitoring

    We are seeing significant signs of recovery and are continuing to monitor for full recovery.

  6. Resolved

    Between 3:05 AM and 6:10 AM PST we experienced signup errors, authentication issues, and connectivity issues in the US-EAST-1 Region. Customers using IAM Identity Center for authentication into the AWS Console, or for authentication into other AWS Services such as Kiro, Connect, etc would have been affected during this time.

    Engineers were automatically engaged at 3:10 AM PST and immediately began investigating the root cause, while in parallel working to mitigate both impacts. At 5:20, we fully mitigated the issue affecting authentication, and most AWS Services observed full recovery at this time.

    A subset of customers using NLB in a single cell in use1-az1 continued to experience connectivity issues until we fully mitigated the underlying issue at 6:21 AM PST. We recommend customers retry any failed requests. The issue has been resolved and all AWS Services are operating normally.

Keep exploring

More from AWS

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