Increased Connectivity issues in US-EAST-1 (N. Virginia)
Connectivity issues affect US-EAST-1 in N. Virginia. The affected components include Amazon CloudWatch, Amazon Connect, Kiro, AWS NAT Gateway, AWS IAM Identity Center, Amazon VPC Lattice, AWS IoT Device Management, Amazon Elastic Load Balancing, and AWS Sign Up. AWS continues to investigate. AWS reports early signs of recovery for authentication via IAM Identity Center and SignUp.
State
Active
Started
Ongoing for
1 h 8 min
Worst impact
Degraded
Timeline
6 updatesActive
1 h 8 min 100%
Updates
Times in UTCAs posted by AWS
We are seeing early signs of recovery for authentication via IAM Identity Center and SignUp.
We are seeing early signs of recovery for authentication via SSO and SignUp.
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.
We continue to investigate Connectivity issues in the US-EAST-1 Region. IAM Identity center sign-in requests and AWS SignUps 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.
We are investigating reports of Connectivity issues in the US-EAST-1 Region. IAM Identity center sign-in requests and AWS SignUps are also impacted at this time.
We are investigating Connectivity issues in the US-EAST-1 Region. IAM Identity center sign-in requests and AWS SignUps are also impacted at this time.
Affected components
6AWS in the last 90 days
Full historyIncidents in 90 days
5
Days with an incident
90
Median duration
3 h 58 min
This incident
72% shorter than the median
Other AWS incidents
All incidentsAWS·Elevated API issues and Launch Failures (Tokyo)
AWS reports elevated API error rates and launch failures in the AP-NORTHEAST-1 Region. This affects many services, including Amazon Elastic Kubernetes Service, Amazon Relational Database Service, AWS Fargate, and Amazon Redshift. AWS later reported connectivity issues to newly created or modified instances in one Availability Zone, apne1-az1. The incident is resolved. It lasted about 5 hours and 32 minutes.
AWS·Elevated Launch Failures (Oregon)
AWS EC2 instance launch failures affected all availability zones in the US-WEST-2 (Oregon) Region. Many services in that Region also had failures. AWS resolved the incident after about 2 hours and 24 minutes.
AWS·Region Availability (Bahrain)
AWS reports a major outage in the Middle East (Bahrain) me-south-1 Region. Many services do not work there, including Amazon Simple Storage Service, Amazon Redshift, AWS WAF, and AWS Internet Connectivity. AWS states that resources and data hosted only in this Region cannot be restored.
AWS·Region Availability (UAE)
AWS reports a major outage in the Middle East (UAE) me-central-1 Region. Many services do not work, including Amazon S3 Replication Time Control, Amazon Relational Database Service, AWS Sign-In, AWS Direct Connect, and AWS Secrets Manager. The mec1-az2 Availability Zone cannot be restored, and AWS continues recovery work in mec1-az1 and mec1-az3.
Follow AWS
Your coding agent knows when AWS is down, and tells you when a failure is theirs, not yours. You can also get AWS incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "aws" and tell me if AWS has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=aws/feed subscribe https://outages.live/feed.xml?providers=awsFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane