Amazon Web Services
AMAZON
Partial Outage
Last checked: Mar 08, 2026 07:32
Incident History (Last 30 Days)
Investigating
Minor
Service impact: Amazon Elastic Container Registry Operational Issue
Amazon Elastic Container Registry in eu-central-2 is impacted by an event that affects Amazon Simple Storage Service. For more information, see the AWS Health Dashboard.
Mar 07, 2026
13:04
Resolved
Critical
Service is operating normally: [RESOLVED] Increased Error Rates
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. …
Mar 07, 2026
13:04
Resolved
Minor
Service is operating normally: [RESOLVED] AWS Transit Gateway Operational Issue
AWS Transit Gateway in eu-central-2 was impacted by an operational issue that affected Amazon Simple Storage Service. The maximum impact level to AWS Transit Gateway was Service impact. For more information, see the AWS Health Dashboard.
Mar 07, 2026
13:04
Monitoring
Minor
Service impact: Increased Error Rates
We are seeing early signs of recovery and continue to monitor and work toward full recovery.
Mar 07, 2026
12:28
Monitoring
Major
Service degradation: Increased Error Rates
We can confirm substantial error rates for PUT and GET requests to Amazon S3 in the EU-CENTRAL-2 Region. Engineers engaged immediately based on automated alarming. We have triangulated the issue to a subsystem responsible for assembling objects from bytes in storage. We have begun implementing mitigations, and are observing some improvement in error rates. We continue to work to identify the root cause, and are working on multiple parallel paths to fully mitigate the issue. Other AWS Services (such as EC2 launches) that rely on S3 are also affected by this issue. Existing EC2 instances are unaffected by this issue. …
Mar 07, 2026
12:17
Investigating
Minor
Service degradation: Increased Error Rates
We are investigating increased error rates in the EU-CENTRAL-2 Region.
Mar 07, 2026
11:53
Investigating
Minor
Service impact: Increased Connectivity Issues and API Error Rates
We are providing an update on the ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-SOUTH-1). We continue to make progress on recovery efforts across multiple workstreams. With the immediate phase of this event now better understood, we are moving to a more targeted communication model. Going forward, updates will be delivered directly to affected customers through the AWS Personal Health Dashboard. Customers who require assistance with this event are encouraged to contact AWS Support through the AWS Management Console or the AWS Support Center. We continue to strongly recommend that customers with workloads running in the Middle …
Mar 03, 2026
08:40
Resolved
Major
Service is operating normally: [RESOLVED] Amazon Transcribe Operational Issue
Amazon Transcribe in me-south-1 was impacted by an operational issue that affected Multiple services. The maximum impact level to Amazon Transcribe was Service impact. For more information, see the AWS Health Dashboard.
Mar 03, 2026
08:40
Investigating
Major
Service impact: AWS Transit Gateway Operational Issue
AWS Transit Gateway in me-south-1 is impacted by an event that affects Multiple services. For more information, see the AWS Health Dashboard.
Mar 03, 2026
08:40
Investigating
Minor
Service impact: Increased Connectivity Issues and API Error Rates
We are providing an update on the ongoing service disruptions affecting the AWS Middle East (Bahrain) Region (ME-SOUTH-1). We continue to make progress on recovery efforts across multiple workstreams. With the immediate phase of this event now better understood, we are moving to a more targeted communication model. Going forward, updates will be delivered directly to affected customers through the AWS Personal Health Dashboard. Customers who require assistance with this event are encouraged to contact AWS Support through the AWS Management Console or the AWS Support Center. We continue to strongly recommend that customers with workloads running in the Middle …
Mar 03, 2026
08:40
Investigating
Major
Service impact: Amazon Virtual Private Cloud Operational Issue
Amazon Virtual Private Cloud in me-central-1 is impacted by an event that affects Multiple services. For more information, see the AWS Health Dashboard.
Mar 03, 2026
08:14
Investigating
Major
Service disruption: Amazon Simple Notification Service Operational Issue
Amazon Simple Notification Service in me-central-1 is impacted by an event that affects Multiple services. For more information, see the AWS Health Dashboard.
Mar 03, 2026
08:14
Resolved
Major
Service is operating normally: [RESOLVED] AWS Global Accelerator Operational Issue
AWS Global Accelerator was impacted by an operational issue that affected Multiple services. The maximum impact level to AWS Global Accelerator was Service impact. For more information, see the AWS Health Dashboard.
Mar 03, 2026
08:14
Investigating
Major
Service degradation: AWS Transit Gateway Operational Issue
AWS Transit Gateway in me-central-1 is impacted by an event that affects Multiple services. For more information, see the AWS Health Dashboard.
Mar 03, 2026
08:14
Investigating
Minor
Service disruption: Increased Error Rates
We are providing an update on the ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1). We continue to make progress on recovery efforts across multiple workstreams. For Amazon S3, we are seeing continued improvement in PUT and LIST availability. Newly written objects are now able to be successfully retrieved, and we continue to work on reducing GET error rates for objects written prior to the event. Full recovery of GET operations for pre-existing data remains dependent on restoring the affected infrastructure. For Amazon DynamoDB, error rates remain elevated and our teams continue to focus on recovery; we …
Mar 03, 2026
08:14
Investigating
Critical
Service impact: Increased Connectivity Issues and API Error Rates
Recovery efforts in the affected Availability Zone (mes1-az2) in the ME-SOUTH-1 Region are ongoing, with the situation remaining consistent with our last update. We have no change to expected timelines for fully restoring power and connectivity. While progress is being made, significant work remains before full restoration is complete. We continue to recommend customers launch replacement resources in one of the unaffected Availability Zones or an alternate AWS Region. Given the extended nature of this event, we continue to encourage customers to replicate Amazon S3 data and other critical workloads from ME-SOUTH-1 to another AWS Region using the guidance shared …
Mar 03, 2026
06:02
Investigating
Minor
Service disruption: Increased Error Rates
We are providing an update on the ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1). The overall state of the region remains largely unchanged, though our teams continue to make progress on recovery efforts across multiple workstreams. For Amazon S3, we are seeing continued improvement in PUT and LIST availability. Newly written objects are now able to be successfully retrieved, and we continue to work on reducing GET error rates for objects written prior to the event. Full recovery of GET operations for pre-existing data remains dependent on restoring the affected infrastructure. For Amazon DynamoDB, error rates …
Mar 03, 2026
04:58
Investigating
Critical
Service impact: Increased Connectivity Issues and API Error Rates
We continue to work toward restoring power in the affected Availability Zone (mes1-az2) in the ME-SOUTH-1 Region. The overall state of the region remains largely unchanged from our previous update. At this time, we have no updated guidance on expected timelines for fully restoring power and connectivity. We are taking all necessary steps to support the recovery process. While progress is being made, significant work remains before full restoration is complete. Given the ongoing uncertainty, we encourage customers to replicate their Amazon S3 data and other critical data from the ME-SOUTH-1 Region to another AWS Region, using the guidance provided …
Mar 03, 2026
03:10
Resolved
Major
Service disruption: Increased Error Rates
We are providing an update on the ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1). The overall state of the region remains largely unchanged from our previous update. We continue to work closely with local authorities and are prioritizing the safety of our personnel throughout our recovery efforts. Teams continue to assess the damage to the affected facilities and are working to restore infrastructure impacted by the event. With respect to Amazon S3, we are seeing improvement in PUT and LIST availability. We continue to work on improving GET error rates, but full recovery will be dependent …
Mar 03, 2026
01:04
Investigating
Critical
Service impact: Increased Connectivity Issues and API Error Rates
We continue to work towards restoring power in the affected Availability Zone (mes1-az2) in the ME-SOUTH-1 Region. We have no updated guidance on expected recovery times, and still expect this to take at least a day to fully restore power and connectivity. AWS infrastructure is designed to be highly resilient, but given the uncertainty of the current situation, we encourage our customers to replicate Amazon S3 and critical data from the ME-SOUTH-1 Region to another AWS Region. For customers requiring guidance on alternate regions, we recommend considering AWS Regions in the United States, Europe, or Asia Pacific, as appropriate for …
Mar 02, 2026
22:27
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:26
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:26
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:26
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:26
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:26
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:26
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:26
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:26
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:26
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:26
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:26
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:26
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:26
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:26
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:26
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:26
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:26
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:26
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:26
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:26
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:26
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:26
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:25
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:25
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:25
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:25
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:25
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:25
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:25
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:25
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:25
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:24
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:24
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:24
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:24
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:24
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:24
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:24
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:24
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:23
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:23
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:23
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:23
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:23
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:21
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:20
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:20
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:20
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:20
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:20
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:20
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:20
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:20
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:20
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:20
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:20
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:20
Investigating
Minor
Feed Deprecated: This RSS Feed has been deprecated. Please check https://status.aws.amazon.com/ and update your bookmarks.
Mar 02, 2026
22:19
Investigating
Minor
Service disruption: Increased Error Rates
We continue to work towards recovery of the two impaired Availability Zones (mec1-az2 and mec1-az3) in the ME-CENTRAL-1 Region with a focus on restoring functionality to foundational services. Since our last update we have made incremental progress in recovering the DynamoDB control plane which will not be visible to external customers but are required for the restoration of service. Similarly we have made progress with the S3 control plane. The recovery of these foundational services, when complete, will enable a broad range of dependent AWS services to recover. We still estimate that the recovery time is at least a day …
Mar 02, 2026
21:13
Investigating
Critical
Service impact: Increased Connectivity Issues and API Error Rates
We are providing an update on the ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1) and the AWS Middle East (Bahrain) Region (ME-SOUTH-1). Due to the ongoing conflict in the Middle East, both affected regions have experienced physical impacts to infrastructure as a result of drone strikes. In the UAE, two of our facilities were directly struck, while in Bahrain, a drone strike in close proximity to one of our facilities caused physical impacts to our infrastructure. These strikes have caused structural damage, disrupted power delivery to our infrastructure, and in some cases required fire suppression activities …
Mar 02, 2026
16:22
Investigating
Critical
Service disruption: Increased Error Rates
We are providing an update on the ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1) and the AWS Middle East (Bahrain) Region (ME-SOUTH-1). Due to the ongoing conflict in the Middle East, both affected regions have experienced physical impacts to infrastructure as a result of drone strikes. In the UAE, two of our facilities were directly struck, while in Bahrain, a drone strike in close proximity to one of our facilities caused physical impacts to our infrastructure. These strikes have caused structural damage, disrupted power delivery to our infrastructure, and in some cases required fire suppression activities …
Mar 02, 2026
16:19
Investigating
Minor
Service impact: Increased Connectivity Issues and API Error Rates
We continue to work towards restoring power in the affected Availability Zone (mes1-az2) in the ME-SOUTH-1 Region. We have no updated guidance on expected recovery times, and still expect this to take at least a day to fully restore power and connectivity. We continue to advise customers to launch replacement resources in one of the unaffected Availability Zones or an alternate AWS Region. At this time we recommend that customers that are capable of backing up data outside of the region consider doing so. You can view the current status of affected AWS services below. We will provide you with …
Mar 02, 2026
14:29
Resolved
Minor
Service disruption: Increased Error Rates
We continue to work towards recovery of the two impaired Availability Zones (mec1-az2 and mec1-az3) in the ME-CENTRAL-1 Region. We have partially restored access to the AWS Management Console, however, some pages will continue to load unsuccessfully until we have recovered core services and power. In parallel to the power and recovery efforts, we are working to restore access to tools and utilities to allow customers to backup and migrate their data. We have no updated guidance on expected recovery times, and still expect this to take at least a day to fully restore power and connectivity. We continue advising …
Mar 02, 2026
13:36
Investigating
Minor
Service impact: Increased Connectivity Issues and API Error Rates
We continue to work towards restoring power in the affected Availability Zone (mes1-az2) in the ME-SOUTH-1 Region. We currently expect our recovery efforts to take at least a day. Our current guidance regarding immediate recovery remains unchanged from our previous update. Customers are able to disassociate Elastic IP addresses from resources in the affected Availability Zone and associate those with resources in the unaffected Availability Zones. This can be done by specifying --allow-reassociation when attempting to associate the Elastic IP to the new resource. We will provide you with further updates by 2:00 PM PST or sooner if new information …
Mar 02, 2026
10:52
Investigating
Major
Service disruption: Increased Error Rates
We continue to work towards recovery of the two impaired Availability Zones (mec1-az2 and mec1-az3) in the ME-CENTRAL-1 Region. The impact is causing elevated errors rates for both the Management Console and CLI. Our current expectation is that recovery will take at least a day to complete. We continue to recommend customers enact their disaster recovery plans and recover from remote backups into alternate AWS Regions. We will continue to provide periodic updates on recovery efforts. Our next update will be by 2:00 PM PST or sooner if new information becomes available.
Mar 02, 2026
09:59
Resolved
Minor
Service impact: Increased Connectivity Issues and API Error Rates
We continue to work toward restoring power in the impacted Availability Zone (mes1-az2) in the ME-SOUTH-1 Region. Meanwhile, EC2 instance and networking APIs have been restored for the other Availability Zones. Additionally, we have made improvements to the availability of RDS multi-AZ databases while operating with the impaired Availability Zone. These improvements will help customers create database exports to preserve data, and we recommend customers with databases in the affected Availability Zone consider creating exports as a precautionary measure. EC2 Instances, EBS Volumes, and other resources impacted in the affected Availability Zone will require a longer recovery timeline, as power …
Mar 02, 2026
06:23
Investigating
Major
Service disruption: Increased Error Rates
We continue to work towards recovery of the two impaired Availability Zones (mec1-az2 and mec1-az3) in the ME-CENTRAL-1 Region. We are expecting recovery to take at least a day, as it requires repair of facilities, cooling and power systems, coordination with local authorities, and careful assessment to ensure the safety of our operators. EC2, Amazon DynamoDB and other AWS Services continue to experience significant error rates and elevated latencies. We recommend customers enact their disaster recovery plans and recover from remote backups into alternate AWS Regions, ideally in Europe. Further, we strongly advise customers to update their applications to ingest …
Mar 02, 2026
06:22
Investigating
Critical
Service disruption: Increased Error Rates
We wanted to provide more information on Amazon S3 given that there are two impaired Availability Zones (mec1-az2 and mec1-az3) in the ME-CENTRAL-1 Region. Amazon S3 is a regional service and designed to withstand the total loss of a single Availability Zone while maintaining S3's durability and availability. When the mec1-az2 AZ was powered off at approximately 4:00 AM PST on Sunday, March 1, S3 continued to operate normally. As the second AZ became impaired, S3 error rates increased. With two Availability Zones significantly impacted, customers are seeing high failure rates for data ingest and egress. We strongly advise customers …
Mar 02, 2026
02:53
Resolved
Minor
Service impact: Increased Connectivity Issues and API Error Rates
We continue to work toward restoring power in the affected Availability Zone (mes1-az2) in the ME-SOUTH-1 Region. At this time, some AWS services have shifted traffic away from the affected Availability Zone and are seeing recovery for their affected operations and workflows. EC2 Instances, EBS Volumes, and other resources impacted in the affected Availability Zone will require a longer recovery timeline. Power has not yet been restored to the affected Availability Zone. If immediate recovery is required, we recommend customers restore from EBS Snapshots and/or launch replacement resources in one of the unaffected Availability Zones or an alternate Region. In …
Mar 02, 2026
02:41
Investigating
Minor
Service impact: Increased Connectivity Issues and API Error Rates
We continue to work on a localized power issue affecting a single Availability Zone (mes1-az2) in the ME-SOUTH-1 Region. In the impacted Availability Zone, EC2 Instances, DB Instances, EBS Volumes, and other AWS Services are also experiencing elevated error rates and latencies for some workflows. As part of our recovery effort, we have shifted traffic away from the impacted Availability Zone for most services. We recommend customers utilize one of the other Availability Zones in the ME-SOUTH-1 Region, as existing instances in other AZs remain unaffected by this issue. We are actively working to restore power and connectivity, at which …
Mar 02, 2026
01:03
Investigating
Critical
Service disruption: Increased Error Rates
We continue to work on a localized power issue affecting multiple Availability Zones in the ME-CENTRAL-1 Region (mec1-az2 and mec1-az3). Customers are experiencing increased EC2 API errors and instance launch failures across the region, and it is not currently possible to launch new instances; existing instances in mec1-az1 should not be affected. Amazon DynamoDB and Amazon S3 are also experiencing significant error rates and elevated latencies. We are actively working to restore power and connectivity, after which we will begin recovery of affected resources; full recovery is still expected to be many hours away. We recommend that affected customers failover, …
Mar 02, 2026
00:52
Investigating
Minor
Service impact: Increased connectivity issues and API Error Rates
We are investigating connectivity and power issues affecting APIs and instances in a single Availability Zone (mes1-az2) in the ME-SOUTH-1 Region due to a localized power issue. Existing instances in this zone will also be affected. Other AWS Services may also be experiencing increased errors and latencies for their workflows, and we are working to route requests away from this affected Availability Zone. We recommend customers make use of other Availability Zones at this time. During this time, we are also experiencing delays in propagating DNS changes for Route53 to pops (Points of Presence) in ME-SOUTH-1. Targeting new launches using …
Mar 01, 2026
23:09
Investigating
Major
Service disruption: Increased Error Rates
We can confirm that a localized power issue has affected another Availability Zone in the ME-CENTRAL-1 Region (mec1-az3). Customers are also experiencing increased EC2 APIs and instance launch errors for the remaining zone (mec1-az1). At this point it is not possible to launch new instances in the region, although existing instances should not be affected in mec1-az1. Other AWS Services, such as DynamoDB and S3 are also experiencing significant error rates and latencies. We are actively working to restore power and connectivity, at which time we will begin to work to recover affected resources. As of this time, we expect …
Mar 01, 2026
22:46
Investigating
Minor
Service disruption: Increased Error Rates
We are investigating additional connectivity issues and error rates in the ME-CENTRAL-1 Region.
Mar 01, 2026
21:59
Investigating
Minor
Service impact: Increased connectivity issues and API Error Rates
We are investigating increased API error rates in a single Availability Zone (mes1-az2) in the ME-SOUTH-1 Region.
Mar 01, 2026
21:56
Investigating
Minor
Service disruption: Increased Error Rates
We confirm the recovery of the AssociateAddress API requests. We have also applied a change that enables customers to disassociate Elastic IP addresses from resources that are impacted by the underlying power issue. With these mitigations, customers can now successfully create and associate new network addresses in the unaffected AZs as well as re-associate Elastic IPs from resources in the affected zone to resources in the unaffected zones. We still do not have an ETA for power restoration at this time. For customers that can, we recommend using alternate Availability Zones or other AWS Regions where applicable. We will provide …
Mar 01, 2026
18:01
Monitoring
Major
Service disruption: Increased Error Rates
We are seeing significant signs of recovery for AssociateAddress requests, and continue to work toward fully mitigating this issue. This combined with the earlier recovery of the AllocateAddress API means customers can now successfully create and associate new network addresses in the unaffected AZs. Other AWS Services are also now observing sustained improvement as a result of the EC2 Networking APIs recovery. We are now focusing on implementing a change that will allow customers to Disassociate Elastic IP addresses from resources that are impacted by the underlying power issue. We expect this specific mitigation to take another hour to complete. …
Mar 01, 2026
16:26
Investigating
Minor
Service disruption: Increased Error Rates
We are seeing positive signs of recovery for many of the EC2 APIs, such as Describes and AllocateAddress. We recognize that customers are still experiencing errors when attempting to call the AssociateAddress API, and are unable to disassociate addresses from resources that are affected by the underlying power issue. We continue to work on multiple parallel paths to mitigate both of these issues. We recommend continuing to retry requests wherever possible. We expect our current mitigation efforts for these specific issues to complete within the the two to three hours. As we progress with these mitigation efforts, customers will observe …
Mar 01, 2026
14:28
Investigating
Minor
Service disruption: Increased Error Rates
We are aware that some customers are experiencing errors when calling EC2 APIs, specifically networking related APIs (AllocateAddress, AssociateAddress, DescribeRouteTable, DescribeNetworkInterfaces). We are actively working on multiple paths to mitigate these issues. For customers experiencing throttling errors on the AllocateAddress APIs, we recommend retrying any failed API requests. We are deploying a configuration change to mitigate the AssociateAddress API errors and expect recovery in the next few hours. DescribeRouteTable and DescribeNetworkInterfaces API calls without specifying zone, Interface or Instance IDs are expected to fail until we restore the impacted zone. We recommend customers to pass these IDs explicitly in these …
Mar 01, 2026
12:14
Investigating
Minor
Service disruption: Increased Error Rates
We want to provide some additional information on the power issue in a single Availability Zone in the ME-CENTRAL-1 Region. At around 4:30 AM PST, one of our Availability Zones (mec1-az2) was impacted by objects that struck the data center, creating sparks and fire. The fire department shut off power to the facility and generators as they worked to put out the fire. We are still awaiting permission to turn the power back on, and once we have, we will ensure we restore power and connectivity safely. It will take several hours to restore connectivity to the impacted AZ. The …
Mar 01, 2026
09:41
Monitoring
Minor
Service degradation: Increased Error Rates
We continue to work toward restoring power in the affected Availability Zone in the ME-CENTRAL-1 Region (mec1-az2). In parallel, we are actively working on improving error rates and latencies that some customers are observing for EC2 Networking and EC2 Describe APIs. Due to increased demand in the unaffected Availability Zones, customers may experience longer than usual provisioning times or may need to retry requests for certain instance types, or pick an alternative instance type. We will provide an update by 10:30 AM PST, or sooner if we have additional information to share.
Mar 01, 2026
08:59
Resolved
Minor
Service degradation: Increased Error Rates
We wanted to provide some additional information on the isolated power issue. At this time, most AWS Services have weighted away from the affected Availability Zone (mec1-az2) and are seeing recovery for their affected operations and workflows. For EC2 Instances, EBS Volumes, and other resources that are impacted in the affected Zone, we will have a longer tail of recovery. At this time, power has not yet been restored to the affected AZ. For now, we recommend continuing to retry any failed API requests. If immediate recovery is required, we recommend customers restore from EBS Snapshots and/or replace affected resources …
Mar 01, 2026
07:09
Investigating
Critical
Service impact: Increased Error Rates
We can confirm that a localized power issue has affected a single Availability Zone in the ME-CENTRAL-1 Region (mec1-az2). EC2 Instances, DB Instances, EBS Volumes, and others resources are currently unavailable and will experience connectivity issues at this time. Other AWS Services are also experiencing error rates and latencies for some workflows. We have weighed away traffic for most services at this time. We recommend customers utilize one of the other Availability Zones in the ME-CENTRAL-1 Region at this time, as existing instances in other AZ's remain unaffected by this issue. We are actively working to restore power and connectivity, …
Mar 01, 2026
06:09
Investigating
Minor
Service impact: Increased Error Rates
We are investigating connectivity and power issues affecting APIs and instances in a single Availability Zone (mec1-az2) in the ME-CENTRAL-1 Region due to a localized power issue. Existing instances in this zone will also be affected. Other AWS Services may also be experiencing increased errors and latencies for their workflows, and we are working to route requests away from this affected Availability Zone. We recommend customers make use of other Availability Zones at this time. Targeting new launches using RunInstances in the remaining AZs should succeed. Existing instances in the other AZs are not affected.
Mar 01, 2026
05:19
Investigating
Minor
Service impact: Increased Error Rates
We are investigating issues with AWS services in the ME-CENTRAL-1 Region.
Mar 01, 2026
04:51
Resolved
Major
Service is operating normally: [RESOLVED] Intermittent missing or delayed EC2 instance and status check metrics
Between 7:00 AM and 12:05 PM PST, we experienced errors while publishing EC2 instance metrics and status checks in the US-EAST-1 Region. This issue resulted in metrics and status checks to be delayed or report INSUFFICIENT_DATA. EC2 APIs and instances were unaffected by this issue and continue to operate normally. We were automatically engaged at 7:05 AM and began identifying multiple parallel paths to mitigate the issue. By 7:20 AM, we identified that the issue was related to an underlying subsystem responsible for publishing EC2 metric data to CloudWatch. By 12:03 PM, we completed our mitigation efforts and observed full …
Feb 25, 2026
12:51
Resolved
Major
Service impact: Intermittent missing or delayed EC2 instance and status check metrics
We can confirm significant signs of recovery, and continuing to monitor to ensure stability. At this time, missing/delayed metrics and instance status checks are recovered. We are actively working to backfill delayed data.
Feb 25, 2026
12:33
Investigating
Major
Service impact: Intermittent missing or delayed EC2 instance and status check metrics
We are seeing early signs of recovery and continue to work toward full resolution. We will continue to provide updates.
Feb 25, 2026
12:10
Identified
Major
Service impact: Intermittent missing or delayed EC2 instance and status check metrics
We can confirm issues with intermittent missing and/or delayed EC2 instance metrics and status checks in the US-EAST-1 Region. While existing instances are unaffected by this issue and operating normally, metrics and status checks may be delayed or reporting INSUFFICIENT_DATA. We have identified the issue to be in an underlying subsystem responsible for publishing EC2 metric data to CloudWatch. Engineers were automatically engaged, and continue to investigate multiple paths to mitigate the issue in parallel. We recommend customers treat the INSUFFICIENT_DATA state as missing data instead of an alarm breach, especially when configuring the alarm to stop, terminate, reboot, or …
Feb 25, 2026
11:28
Investigating
Major
Service impact: Intermittent missing or delayed EC2 instance and status check metrics
We are experiencing intermittent missing or delayed EC2 instance and status check metrics in the US-EAST-1 Region. Alarms on delayed or missing metrics may transition into an INSUFFICIENT_DATA state. We are taking multiple parallel paths to mitigate this issue. While underlying resources are not affected by this issue, customers with automated actions based off of delayed or missing metric data may see their automations start. EC2 APIs are not impacted and therefore EC2 AutoScaling will not be affected by this issue.
Feb 25, 2026
10:14
Resolved
Critical
Service is operating normally: [RESOLVED] Change Propagation Delays
Between 12:20 PM and 1:55 PM PST, we experienced elevated DNS resolution errors for CloudFront distributions served from a subset of edge locations globally. During this time, customers may have received NXDOMAIN responses. Engineers were automatically engaged, immediately began investigating in multiple parallel paths and mitigated errors by taking the affected fleet of DNS servers out of service. Additionally, between 12:20 PM and 8:08 PM PST, we experienced longer than usual propagation times for changes to CloudFront configurations. The propagation delay was limited to certain types of changes, such as creating/deleting distributions, or updating the distributions for DNS or TLS …
Feb 10, 2026
20:18
Resolved
Minor
Service impact: Change Propagation Delays
We continue to make progress towards mitigating the change propagation delays to CloudFront distributions. We have completed a successful configuration updates to a set of edge pops and are now propagating to edge pops in other stripes. The delayed propagation impact is limited to certain types of changes, such as creating/deleting distributions, or updating the distributions for DNS or TLS certificate related changes. End-user requests for content delivery from our edge locations and invalidations continue to be served normally at this stage. We estimate approximately 60 minutes for full recovery.
Feb 10, 2026
19:06
Investigating
Minor
Service impact: Change Propagation Delays
We continue to work toward mitigating the change propagation delays to CloudFront distributions. We have further confirmed that the delayed propagation impact is limited to certain types of changes, such as creating/deleting distributions, or updating the distributions for DNS or TLS certificate related changes. End-user requests for content delivery from our edge locations and invalidations are being served normally at this stage. Our recovery is taking longer than anticipated in the previous update and we now estimate another 2 hours for full recovery. We will provide another update within 60 minutes, or sooner if information becomes available.
Feb 10, 2026
18:06
Investigating
Minor
Service impact: Change Propagation Delays
We are on track to apply mitigations towards resolving the change propagation delays to CloudFront distributions. We are implementing the mitigations in a striped manner on the affected systems that consume the configurations on the edge pops. Customers changes to CloudFront distributions will not propagate until we’ve fully mitigated this issue. End-user requests for content delivery from our edge locations and invalidations are being served normally at this stage. We expect full recovery in approximately 2 hours. We will provide another update within 60 minutes, or sooner if information becomes available.
Feb 10, 2026
17:01
Investigating
Minor
Service impact: Change Propagation Delays
We continue to apply mitigation steps for delays in propagating changes to CloudFront distributions. We are actively engaged and working on two parallel paths to mitigate the issue. Customers changes to CloudFront distributions will not propagate until we’ve fully mitigated this issue. End-user requests for content delivery from our edge locations and invalidations are being served normally at this stage. We expect full recovery is still 2-3 hours away. We will provide another update within 60 minutes, or sooner if information becomes available.
Feb 10, 2026
16:02
Investigating
Minor
Service impact: Change Propagation Delays
We continue to apply mitigation steps for delays in propagating changes to CloudFront distributions. We are actively engaged and working on two parallel paths to mitigate the issue. Customers changes to CloudFront distributions will not propagate until we’ve fully mitigated this issue. End-user requests for content delivery from our edge locations and invalidations are being served normally at this stage. We expect full recovery in 2-3 hours. We will provide another update within 60 minutes, or sooner if information becomes available.
Feb 10, 2026
16:02
Investigating
Minor
Service impact: Change Propagation Delays
We continue to work toward mitigating the current issue, which is delays in propagating changes to CloudFront distributions. Cache invalidation is not affected by this issue. In parallel, we are actively investigating options to increase the velocity of our recovery efforts. In order to ensure that we do not cause additional impact, we are proceeding cautiously but safely. During this time, customers can continue making changes but these changes will not propagate until we’ve fully mitigated this issue. We expect full recovery is a couple hours away.
Feb 10, 2026
15:06
Investigating
Minor
Service impact: Increased Error Rates and Latencies
We can confirm full recovery for DNS resolution errors for CloudFront Distributions. Due to some of the mitigation actions we have taken, customers will experience delays in propagating changes to CloudFront distributions, including the creation of new CloudFront distributions. We continue to work toward recovering change propagation delays and will provide an update in the next 30-60 minutes.
Feb 10, 2026
14:34
Investigating
Major
Service impact: Increased Error Rates and Latencies
We can confirm significant recovery for the DNS resolution errors for Cloudfront distributions. Customers are still experiencing delays propagating changes to Cloudfront distributions. We continue to work toward full recovery and will provide additional information in the next 30-60 minutes.
Feb 10, 2026
13:58
Investigating
Major
Service impact: Increased Error Rates and Latencies
We can confirm significant recovery for the DNS resolution errors for CloudFront distributions. Customers are still experiencing delays propagating changes to CloudFront distributions. We continue to work toward full recovery and will provide additional information in the next 30-60 minutes.
Feb 10, 2026
13:58
Investigating
Minor
Service impact: Increased Error Rates and Latencies
We are seeing early signs of recovery, and continue to work toward full recovery.
Feb 10, 2026
13:46
Identified
Minor
Service impact: Increased Error Rates and Latencies
We can confirm errors for DNS resolution for some Cloudfront distributions. During this time, customers may receive an NXDOMAIN response. Additionally, customers may also experience delayed propagation for changes to CloudFront distributions. We have identified the root cause of the issue and are actively working on multiple paths to resolving the errors. We have verified that our initial mitigation effort on a portion of the affected subsystem was successful, and we are actively working toward performing that mitigation across the fleet. We recommend customers continue to retry any failed requests while we work toward mitigation. A few services that use …
Feb 10, 2026
13:40
Identified
Minor
Service impact: Increased Error Rates and Latencies
We can confirm errors for DNS resolution for some CloudFront distributions. During this time, customers may receive an NXDOMAIN response. Additionally, customers may also experience delayed propagation for changes to CloudFront distributions. We have identified the root cause of the issue and are actively working on multiple paths to resolving the errors. We have verified that our initial mitigation effort on a portion of the affected subsystem was successful, and we are actively working toward performing that mitigation across the fleet. We recommend customers continue to retry any failed requests while we work toward mitigation. A few services that use …
Feb 10, 2026
13:40
Investigating
Minor
Service impact: Increased Error Rates and Latencies
We are investigating DNS resolution failures for some specific Cloudfront distributions. We are actively investigating and will provide additional information in the next 30-60 minutes.
Feb 10, 2026
13:15
Investigating
Minor
Service impact: Increased Error Rates and Latencies
We are investigating DNS resolution failures for some specific CloudFront distributions. We are actively investigating and will provide additional information in the next 30-60 minutes.
Feb 10, 2026
13:15
Resolved
Critical
Service impact: [Resolved] Network Connectivity
Between 6:36 AM and 7:09 AM PST, we experienced intermittent network connectivity issues between two Availability Zones (sae1-az1 and sae1-az3) in the SA-EAST-1 Region. This resulted in API error rates and latencies for AWS Services in the SA-EAST-1 Region. The issue has been resolved and all services are operating normally.
Feb 07, 2026
10:30