AWS Health

https://health.aws.amazon.com/public/currentevents

Edit Back
Adapter

aws

Active

Yes

Poll Interval

120s

Incidents

20

Notifications

Disabled

Recent Incidents

Increased Error Rates (Bahrain)

Region unavailable; customers should recover resources from remote back…

AWS Health · Mar 02 05:56 UTC · 15 updates · last Apr 30 07:07 UTC
Update

Increased Error Rates (UAE)

Region damaged by conflict; migrate resources and restore from backups

AWS Health · Mar 01 12:51 UTC · 24 updates · last Apr 30 07:25 UTC
Update

[RESOLVED] Increased API Error Rates (Oregon)

Resolved; monitoring recovery from elevated STS API errors in US-WEST-2

AWS Health · Sep 03 21:49 UTC · 7 updates · last Sep 04 00:07 UTC
Resolved

[RESOLVED] Increased Error Rates (Tokyo)

Resolved: AP-NORTHEAST-1 Connect real-time metrics delays mitigated

AWS Health · Aug 21 02:02 UTC · 4 updates · last Aug 21 02:40 UTC
Resolved

[RESOLVED] Increased Error Rates (London)

Resolved: EC2 launch errors in euw2-az4 fully recovered at 11:00 AM PDT

AWS Health · Aug 19 15:15 UTC · 3 updates · last Aug 19 18:47 UTC
Resolved

[RESOLVED] Increased Packet loss (Frankfurt)

Resolved: FR5 Direct Connect connectivity restored and stable

AWS Health · Aug 15 03:42 UTC · 23 updates · last Aug 18 04:01 UTC
Resolved

[RESOLVED] Elevated Packet Loss (Mumbai)

Between 9:42 AM and 11:44 AM PDT, we experienced elevated network packet loss impacting AWS Direct Connect connectivity in the AP-SOUTH-1 Region. Our engineering team was automatically engaged at 9:46 AM to begin investigating. By 10:51 AM, we understood the root cause to be a configuration change made to a system responsible for assigning routes to devices. As we gained confidence in our mitigation steps, we parallelized our efforts to further reduce the packet loss. The issue is resolved and the service is operating normally.

AWS Health · Jul 31 17:33 UTC · 3 updates · last Jul 31 18:54 UTC
Resolved

[RESOLVED] Connectivity Issues (Oregon)

Between 3:55 AM and 4:15 AM PDT, we experienced connectivity issues that impacted connectivity to the US-WEST-2 Region. This impacted multiple AWS services in the Region. Some customers may have also experienced issues accessing the AWS Management Console, with connection timeouts and unresponsive pages. Connectivity within the Region was not affected. Our engineers were automatically engaged at 4:01 AM PDT, and immediately began investigating this issue. We identified the root cause as an issue with networking devices responsible for network routing from the Region to the Seattle Metro, and began working in parallel on multiple paths to mitigate the impact. We took mitigation measures that led to initial recovery at 4:15 AM PDT. As the network continued to stabilize following our mitigation actions, a brief reconvergence event occurred between 4:47 AM and 4:59 AM PDT. During this reconvergence period, some customers may have experienced intermittent connectivity issues to the Region as network routes were re-established. By 4:59 AM PDT, all routes had been fully restored and service metrics returned to pre-event levels. Customers using AWS Direct Connect through EqSe2, Westin Building Exchange, Seattle experienced an extended impact window from 3:55 AM to 5:12 AM PDT. These customers would have experienced connectivity issues until network routes for this specific path were fully restored at 5:12 AM PDT. Customers connected redundantly through other AWS Direct Connect locations were not impacted by this event. The issue has been resolved and all AWS services are operating normally.

AWS Health · Jul 24 11:40 UTC · 5 updates · last Jul 24 13:01 UTC
Resolved

[RESOLVED] Inaccurate Estimated Billing Data

Between July 16 at 7:38 PM PDT and July 17 at 6:00 AM PDT, customers received erroneous budget and cost anomaly detection alerts, and saw inflated estimated cost and usage data in the Billing and Cost Management Console and the Cost and Usage Reports. These inaccurate billing estimates did not affect customer invoices. On July 16, 2026 at 7:46 PM PDT, our alarms detected cost anomalies but failed to halt the estimated bill generation process or alert our engineering teams. Our engineering teams were alerted to this issue on July 17 at 12:19 AM PDT by customer escalations, and we immediately began to investigate. We first informed customers in the Service Health Dashboard at 1:33 AM PDT. At 8:24 AM PDT we paused further updates to estimated billing data and turned off budget and cost anomaly alerts as a precautionary measure. We identified the root cause at 12:00 PM PDT, which was a configuration change in our bill computation system. This system relies on unit conversion data to calculate line item charges. The configuration change caused updates to the unit conversion data to fail, resulting in inflated line item costs, which propagated to the Billing and Cost Management console and triggered the budget and cost anomaly alerts. We implemented a mitigation at 12:30 PM PDT which corrected the unit conversion configuration, and we began to reprocess cost and usage data for all customer accounts. We observed recovery beginning at 4:19 PM PDT, and the majority of accounts were fully recovered on July 18 at 6:00 AM PDT. There is a small number of accounts still processing and we will post updates for these accounts on the Personal Health Dashboard. We have corrected our alarms to immediately halt processing and notify our engineering teams when anomalies occur. We apologize for the alarm this incident caused our customers and we are conducting a thorough retrospective to prevent events like this from reoccurring and to improve our response when billing incidents do occur. The issue has been resolved and all AWS services are now operating normally.

AWS Health · Jul 17 08:33 UTC · 15 updates · last Jul 18 13:57 UTC
Resolved

[RESOLVED] Increased 5xx Errors

Between 12:45 AM and 4:18 AM PDT, we experienced increased 5xx errors for CloudFront customers utilizing VPC Origins connectivity. Our engineers were automatically engaged and immediately began investigating the root cause. By 2:57 AM PDT, we identified the root cause of the issue as an internal constraint on the fleet that manages connections to private VPC origins. When this constraint was reached, the system responsible for distributing routing configuration to our network processors failed to load the updated configuration data correctly, affecting routing of VPC Origin connections. At 3:52 AM PDT, we took multiple mitigation actions that led to to full recovery at 4:18 AM PDT. Now that the issue has been mitigated, customers who temporarily changed their origin type can safely revert these changes. Customers utilizing other origin types were not affected by this issue. The issue has been resolved and the service is operating normally.

AWS Health · Jul 16 08:44 UTC · 7 updates · last Jul 16 12:21 UTC
Resolved

[RESOLVED] Elevated connectivity issues with a single Avalability zone (Frankfurt)

Between 2:56 PM and 6:07 PM PDT, we experienced connectivity issues to a subset of EC2 instances in a single Availability Zone (euc1-az2) in the EU-CENTRAL-1 Region. During this time, customers may also have experienced increased error rates and latencies for new instance launches in the affected zone, along with some AWS APIs that use the affected EC2 instances. Some AWS Services also experienced connectivity issues and increased error rates within the affected zone. Engineers were automatically engaged and immediately began investigating. As part of our recovery effort, we shifted traffic away from the impacted Availability Zone for affected services at 3:04 PM. At 3:05 PM we identified the root cause to be a recent networking change causing the impact. Engineers immediately began reverting this change which completed at 4:28 PM. This resulted in restoration of network connectivity to the affected zone at 4:30 PM. We continued to work until we fully recovered the impacts at 6:07 PM. We do not expect this issue to reoccur. The issue has been resolved and the service is operating normally.

AWS Health · Jul 15 23:11 UTC · 3 updates · last Jul 16 01:24 UTC
Resolved

[RESOLVED] Increased Launch Template API Error Rates (N. Virginia)

Between 2:56 AM and 6:54 AM PDT, we experienced increased error rates when calling EC2 Launch Template APIs in the US-EAST-1 Region. During this time, affected customers may have experienced errors when creating, modifying, or decribing Launch Templates. Other AWS services that rely on Launch Templates were also impacted. Amazon EC2 instances and Amazon EKS workloads already running on provisioned nodes continued to operate normally. Cluster modification operations, and Managed Node Group creation were also impacted. For EKS Auto Mode, impact was limited to operations requiring new capacity or changes, including node provisioning and pod scheduling. Our engineers were automatically engaged and immediately began investigating the root cause. We identified the root cause as a congestion issue within an EC2 internal subsystem responsible for processing EC2 launch template workflows. At 3:26 AM PDT, we took mitigation actions by introducing throttling for the affected APIs and we saw some recovery which was communicated directly with a subset of customers via the 'Your Account view' of the AWS Health Dashboard. We took multiple additional mitigation paths, incrementally lifting these throttle limits, and by 6:54 AM PDT, the issue was fully mitigated. We recommend that customers retry any requests. The issue has been resolved and all AWS services are now operating normally.

AWS Health · Jul 06 12:45 UTC · 6 updates · last Jul 06 14:53 UTC
Resolved

[RESOLVED] Increased Error Rates and Latencies (Stockholm)

Between 1:42 PM and 2:25 PM PDT we experienced increased error rates and latencies for EC2 APIs in the EU-NORTH-1 Region. This issue also affected new instance launches. Other AWS Services that launch new instances or call EC2 APIs as part of their workflows were also affected by this issue. Existing EC2 instances were unaffected by this issue. During this time, customers would have received an Internal Server Error in the Management Console and APIs. Engineers were automatically engaged and began investigating the root cause. We identified the root cause as a planned configuration change. This change was reverted and we began observing recovery at 2:19 PM. By 2:25 PM, the issue was fully mitigated. We do not expect this issue to reoccur. Since the issue was mitigated at 2:25 PM, we have been processing a backlog for ELB workflows and expect this backlog to complete within the next 30 minutes. We recommend customers retry requests that failed during this time. The issue has been resolved and all services are operating normally.

AWS Health · Jun 30 21:02 UTC · 5 updates · last Jun 30 21:53 UTC
Resolved

[RESOLVED] Fable 5 and Mythos 5 Access (N. Virginia)

Claude Fable 5 and Claude Mythos 5 models remain unavailable for all users in all regions. We are resolving this Health event. For further details please view the Anthropic statement.

AWS Health · Jun 13 01:26 UTC · 4 updates · last Jun 15 18:13 UTC
Resolved

[RESOLVED] Internet Connectivity Issues (Sao Paulo)

Between 5:50 PM and 7:15 PM PDT, we experienced connectivity issues that may have impacted Internet performance for some customers in the SA-EAST-1 Region. During this time, connectivity to instances and services within the Region was not affected. Our engineering team was automatically engaged at 5:51 PM PDT and immediately began investigating the issue. We identified the root cause and implemented a fix, which mitigated the issue at 7:15 PM PDT. The issue has been resolved and the service is operating normally.

AWS Health · Jun 06 04:24 UTC · 1 update · last Jun 06 04:24 UTC
Resolved

We are investigating increased error rates for Route53 API calls

We are investigating increased error rates for Route53 API calls.

AWS Health · May 22 23:39 UTC · 1 update · last May 22 23:39 UTC
Resolved

[RESOLVED] Increased API Error Rates

Between 4:00 PM and 4:46 PM, we experienced increased error rates for the Route53 APIs. This issue did not impact resolution of existing DNS records. Engineers were automatically engaged and immediately began investigating the issue. During this time, customers may have received 500s for Route53 APIs and the Route53 Management Console. We have identified the root cause and have mitigated this issue. Other AWS Services that call the Route53 APIs in their workflows may also have been impacted during this time. We recommend retrying any failed operations or stuck workflows. We do not expect recurrence of this issue. The issue has been resolved and the service is operating normally.

AWS Health · May 22 23:38 UTC · 3 updates · last May 23 00:13 UTC
Resolved

[RESOLVED] Increased Error Rate and Latency (N. Virginia)

Starting May 7 4:20 PM PDT, we experienced increased impaired EC2 instances and degraded EBS volumes in a single facility (data center) within a single Availability Zone (use1-az4) in the US-EAST-1 Region. The issue was caused by a thermal event resulting in a loss of power. As part of our recovery effort, we shifted traffic away from the impacted Availability Zone for most services at May 7 5:06 PM. AWS services, like Elastic Load Balancing, Elastic Kubernetes Service, ElastiCache, Redshift, OpenSearch, Managed Streaming for Apache Kafka among others, that depend on the affected EC2 instances and EBS volumes in this Availability Zone, also experienced elevated error rates and latencies for some workflows and/or configurations. Our main effort during the event mitigation strategy was to bring back our cooling systems capacity. By May 8 1:50 PM, we were able to stabilize cooling system capacity to pre-event levels, which helped us to restore the majority of the impaired EC2 instances and EBS volumes. A small number of instances and EBS volumes remain impaired and we continue to work to recover all affected remaining resources. We will communicate with customers who are still impacted via the Your Account view of the AWS Health Dashboard. Customers that require further assistance with this event may contact AWS Support through the AWS Management Console or the AWS Support Center.

AWS Health · May 08 00:25 UTC · 17 updates · last May 09 03:04 UTC
Resolved

[RESOLVED] Increased Connectivity Issues (Paris)

Between 3:58 AM and 4:40 AM PDT, we experienced increased error rates and increased launch failures for EC2 instances in a single Availability Zone (euw3-az2) in the EU-WEST-3 Region. During this time, customers attempting to launch new EC2 instances in the affected Availability Zone would have experienced launch failures. Additionally, a subset of existing EC2 instances and EBS volumes in this Availability Zone were impacted and became unreachable. We have identified the root cause to be a loss of power to infrastructure within the affected Availability Zone. Engineers were engaged at 4:02 AM and immediately began working to restore power and assess the scope of impact. By 4:20 AM, power was successfully restored to the affected infrastructure. We then focused our efforts on recovering impacted EC2 instances and EBS volumes. By 4:40 AM, all impacted EC2 instances and EBS volumes had been fully recovered and were operating normally. No additional action is required for EC2 instances and EBS volumes that were impacted during the power loss event, as these have been fully recovered. The issue has been resolved and the service is operating normally.

AWS Health · Apr 27 11:27 UTC · 3 updates · last Apr 27 12:05 UTC
Resolved

[RESOLVED] Increased Error Rates (Zurich)

Between 11:27 AM and 12:20 PM PST we experienced substantial error rates for S3 PUT/GET requests in EU-CENTRAL-2 Region. Engineers were engaged immediately based on automated alarming. We identified the root cause as an issue with a subsystem responsible for assembling objects bytes in storage. At 12:04 PM PST, we implemented mitigations and began observing early signs of recovery for S3. Error rates continued to improve, and other AWS Services continued to recover until 12:50 PM PST when we observed full recovery. We continue to work toward backfilling Cloudwatch logs, and expect that to continue over the next couple hours. We recommend customers retry any failed requests. The issue has been resolved and all services are operating normally.

AWS Health · Mar 07 19:53 UTC · 4 updates · last Mar 07 21:04 UTC
Resolved