# Multiple services (N. Virginia): Increased Connectivity issues in US-EAST-1 - Provider: [AWS](https://down.guide/providers/aws) - Confidence: Confirmed - Impact: Impact not stated - lasted 2h 15m - started 2026-11-15 12:38 UTC - Multiple services - us-east-1 - id: DWN-469a1d897e - Official page: https://health.aws.amazon.com/health/status ## Summary The provider says connectivity issues in US-EAST-1 affecting IAM Identity Center sign-in and AWS SignUp are resolved. Authentication was fully mitigated at 5:20 AM PST, and a subset of Network Load Balancers in use1-az1 was fully mitigated at 6:21 AM PST. _Written by anthropic/claude-haiku-5.5 from AWS's own updates._ ## Updates from AWS ### 2026-11-15 12:38 UTC: 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. ### 2026-11-15 13:15 UTC: investigating 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. ### 2026-11-15 13:22 UTC: investigating We are seeing early signs of recovery for authentication via IAM Identity Center and SignUp. ### 2026-11-15 14:23 UTC: investigating 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. ### 2026-11-15 14:32 UTC: investigating We are seeing significant signs of recovery and are continuing to monitor for full recovery. ### 2026-11-15 14:53 UTC: 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. From the builder: does your app depend on AWS? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=aws) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention AWS. --- down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-469a1d897e), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.