{"multipleservices-us-west-2":[{"summary":"[RESOLVED] Connectivity Issues","arn":"arn:aws:health:us-west-2::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_83A36_24C89B493A6","status":"1","date":"1784893200","event_log":[{"message":"We are investigating connecivity issues impacting multiple AWS services in the US-WEST-2 Region.","summary":"Connectivity Issues","status":"1","timestamp":1784893200},{"message":"We are seeing initial signs of recovery and continue to work toward full recovery.","summary":"Connectivity Issues","status":"1","timestamp":1784894181},{"message":"We continue to see significant signs of recovery as a result of our mitigation efforts for the connectivity issues impacting multiple AWS services in the US-WEST-2 Region. We have identified the root cause as an issue with a networking device responsible for network routing from the Region to the Seattle Metro. Engineers have finished all mitigation work. As routes continue to be restored, customers should see a continued reduction in error rates and timeouts when connecting to affected services. We are monitoring recovery progress closely and will continue working until all routes have been fully restored and service metrics return to pre-event levels. We will provide another update in the next 30-45 minutes.","summary":"Connectivity Issues","status":"1","timestamp":1784896220},{"message":"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. \n\nCustomers 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.\n\nThe issue has been resolved and all AWS services are operating normally.","summary":"[RESOLVED] Connectivity Issues","status":"0","timestamp":1784898081}],"impacted_services":{"apigateway-us-west-2":{"service_name":"Amazon API Gateway","current":"0","max":"1"},"awsiot-us-west-2":{"service_name":"AWS IoT Core","current":"0","max":"1"},"directconnect-us-west-2":{"service_name":"AWS Direct Connect","current":"0","max":"1"},"ec2-us-west-2":{"service_name":"Amazon Elastic Compute Cloud","current":"0","max":"1"},"ecs-us-west-2":{"service_name":"Amazon Elastic Container Service","current":"0","max":"1"},"elb-us-west-2":{"service_name":"Amazon Elastic Load Balancing","current":"0","max":"1"},"globalaccelerator":{"service_name":"AWS Global Accelerator","current":"0","max":"1"},"internetconnectivity-us-west-2":{"service_name":"AWS Internet Connectivity","current":"0","max":"1"},"vpc-us-west-2":{"service_name":"Amazon Virtual Private Cloud","current":"0","max":"1"},"vpnvpc-us-west-2":{"service_name":"AWS Site-to-Site VPN","current":"0","max":"1"}},"impacted_service_status_changes":[{"service":"apigateway-us-west-2","service_name":"Amazon API Gateway","previous_status":"0","current_status":"1","timestamp":1784893200000},{"service":"awsiot-us-west-2","service_name":"AWS IoT Core","previous_status":"0","current_status":"1","timestamp":1784893200000},{"service":"directconnect-us-west-2","service_name":"AWS Direct Connect","previous_status":"0","current_status":"1","timestamp":1784893200000},{"service":"ec2-us-west-2","service_name":"Amazon Elastic Compute Cloud","previous_status":"0","current_status":"1","timestamp":1784893200000},{"service":"ecs-us-west-2","service_name":"Amazon Elastic Container Service","previous_status":"0","current_status":"1","timestamp":1784893200000},{"service":"elb-us-west-2","service_name":"Amazon Elastic Load Balancing","previous_status":"0","current_status":"1","timestamp":1784893200000},{"service":"globalaccelerator","service_name":"AWS Global Accelerator","previous_status":"0","current_status":"1","timestamp":1784893200000},{"service":"internetconnectivity-us-west-2","service_name":"AWS Internet Connectivity","previous_status":"0","current_status":"1","timestamp":1784893200000},{"service":"vpc-us-west-2","service_name":"Amazon Virtual Private Cloud","previous_status":"0","current_status":"1","timestamp":1784893200000},{"service":"vpnvpc-us-west-2","service_name":"AWS Site-to-Site VPN","previous_status":"0","current_status":"1","timestamp":1784893200000},{"service":"apigateway-us-west-2","service_name":"Amazon API Gateway","previous_status":"1","current_status":"0","timestamp":1784898081000},{"service":"awsiot-us-west-2","service_name":"AWS IoT Core","previous_status":"1","current_status":"0","timestamp":1784898081000},{"service":"directconnect-us-west-2","service_name":"AWS Direct Connect","previous_status":"1","current_status":"0","timestamp":1784898081000},{"service":"ec2-us-west-2","service_name":"Amazon Elastic Compute Cloud","previous_status":"1","current_status":"0","timestamp":1784898081000},{"service":"ecs-us-west-2","service_name":"Amazon Elastic Container Service","previous_status":"1","current_status":"0","timestamp":1784898081000},{"service":"elb-us-west-2","service_name":"Amazon Elastic Load Balancing","previous_status":"1","current_status":"0","timestamp":1784898081000},{"service":"globalaccelerator","service_name":"AWS Global Accelerator","previous_status":"1","current_status":"0","timestamp":1784898081000},{"service":"internetconnectivity-us-west-2","service_name":"AWS Internet Connectivity","previous_status":"1","current_status":"0","timestamp":1784898081000},{"service":"vpc-us-west-2","service_name":"Amazon Virtual Private Cloud","previous_status":"1","current_status":"0","timestamp":1784898081000},{"service":"vpnvpc-us-west-2","service_name":"AWS Site-to-Site VPN","previous_status":"1","current_status":"0","timestamp":1784898081000}]},{"summary":"[RESOLVED] Increased API Error Rates","arn":"arn:aws:health:us-west-2::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_926DB_F0036494EA4","status":"1","date":"1788472198","event_log":[{"message":"Starting at 2:12 PM PDT, we began experiencing increased API error rates for STS and Sign In when using SAML in the US-WEST-2 Region. Our engineering team was automatically engaged at 2:19 PM to begin investigating the root cause. There is no work around available at this time. We will provide another update by 3:30 PM PDT.","summary":"Increased API Error Rates","status":"1","timestamp":1788472198},{"message":"We are seeing early signs of recovery and continue to monitor for full recovery. We will provide another update at 4:15 PM, or sooner if we have additional information to share.","summary":"Increased API Error Rates","status":"1","timestamp":1788474388},{"message":"We continue to see recovery holding steady for the STS AssumeRoleWithSAML and AssumeRoleWithWebIdentity APIs in the US-WEST-2 Region. Error rates are now back to pre-event levels, and we continue actively monitoring to confirm full recovery. We will provide another update by 5:15 PM or earlier.","summary":"Increased API Error Rates","status":"1","timestamp":1788477609},{"message":"Between 2:12 PM and 3:18 PM PDT, we experienced increased API error rates affecting the STS AssumeRoleWithSAML  and AssumeRoleWithWebIdentity APIs in the US-WEST-2 Region. The root cause was determined to be due to an issue with an STS subsystem responsible for communicating with external identity providers. Other AWS Services that rely on these identity federation protocols were also affected. At 3:18 PM, we observed signs of recovery and continued to monitor to ensure stability and full recovery. The issue is resolved and the service is operating normally at this time.","summary":"[RESOLVED] Increased API Error Rates","status":"0","timestamp":1788480474}],"impacted_services":{"connect-us-west-2":{"service_name":"Amazon Connect","current":"0","max":"1"},"iamidentitycenter-us-west-2":{"service_name":"AWS IAM Identity Center","current":"0","max":"1"},"signin-us-west-2":{"service_name":"AWS Sign-In","current":"0","max":"1"},"sts-us-west-2":{"service_name":"AWS Security Token Service","current":"0","max":"1"}},"impacted_service_status_changes":[{"service":"connect-us-west-2","service_name":"Amazon Connect","previous_status":"0","current_status":"1","timestamp":1788472198000},{"service":"iamidentitycenter-us-west-2","service_name":"AWS IAM Identity Center","previous_status":"0","current_status":"1","timestamp":1788472198000},{"service":"signin-us-west-2","service_name":"AWS Sign-In","previous_status":"0","current_status":"1","timestamp":1788472198000},{"service":"sts-us-west-2","service_name":"AWS Security Token Service","previous_status":"0","current_status":"1","timestamp":1788472198000},{"service":"connect-us-west-2","service_name":"Amazon Connect","previous_status":"1","current_status":"0","timestamp":1788480474000},{"service":"iamidentitycenter-us-west-2","service_name":"AWS IAM Identity Center","previous_status":"1","current_status":"0","timestamp":1788480474000},{"service":"signin-us-west-2","service_name":"AWS Sign-In","previous_status":"1","current_status":"0","timestamp":1788480474000},{"service":"sts-us-west-2","service_name":"AWS Security Token Service","previous_status":"1","current_status":"0","timestamp":1788480474000}]}],"connect-ap-northeast-1":[{"summary":"[RESOLVED] Increased Error Rates","arn":"arn:aws:health:ap-northeast-1::event/CONNECT/AWS_CONNECT_OPERATIONAL_ISSUE/AWS_CONNECT_OPERATIONAL_ISSUE_BFE2B_2DD530F8C5B","status":"1","date":"1787277742","event_log":[{"message":"AP-NORTHEAST-1リージョンにおいて、エラー率が上昇しており、リアルタイムメトリクスに影響が出ています。お客様はリアルタイムメトリクスデータの欠落または遅延を経験する可能性があります。| We are experiencing increased error rates affecting real-time metrics in the AP-NORTHEAST-1 Region. Customers may experience missing or delayed real-time metric data.\n","summary":"Increased Error Rates","status":"1","timestamp":1787277742},{"message":"日本時間 8:58 AM から 10:34 AM の間、AP-NORTHEAST-1 リージョンにおける Amazon Connect のリアルタイムメトリクスに影響する遅延が増加し、データが欠落する、またはデータが最新の状態に更新されない事象が発生しました。この間、お客様は分析レポート内で一部のデータが反映されない状況を経験した可能性があり、また、コンタクトフロー内でリアルタイムメトリクス (例: 人員の確認ブロック) にアクセスする際に問題が発生した可能性があります。根本原因は、メトリクスイベント配信を担うサブシステムの問題であると特定しました。日本時間 10:13 AM に緩和策の適用を開始し、 10:34 AM までに影響を解消しました。本事象は解決済みであり、サービスは正常に稼働しています。| Between 4:58 PM and 6:34 PM PDT, we experienced increased delays affecting real-time metrics for Amazon Connect in the AP-NORTHEAST-1 Region, resulting in missing or stale data. During this time, customers may have experienced missing data within analytics reports, and may have observed issues if accessing realtime metrics within contact Flows, such as checking agent staffing. We identified the root cause to be an issue with the subsystem responsible for metric event delivery. We started applying the mitigations at 6:13 PM and mitigated the issue by 6:34 PM. The issue has been resolved and the service is operating normally.\n","summary":"[RESOLVED] Increased Error Rates","status":"0","timestamp":1787280002}]}],"ec2-eu-west-2":[{"summary":"[RESOLVED] Increased Error Rates","arn":"arn:aws:health:eu-west-2::event/EC2/AWS_EC2_OPERATIONAL_ISSUE/AWS_EC2_OPERATIONAL_ISSUE_25280_73B0FC79387","status":"1","date":"1787152514","event_log":[{"message":"We are investigating an issue that is impacting launching new EC2 instances and resources in a newly launched Availability Zone (euw2-az4) in the EU-WEST-2 Region. During this time, affected customers may experience issues when creating or modifying resources in the Region. Other AWS services may also be impacted. For immediate recovery, we recommend that customers use alternative Availability Zones (euw2-az1, euw2-az2, and euw2-az3) where applicable. Existing running instances and resources are not affected. We will provide another update by 10:00 AM PDT, or sooner if we have additional information to share.","summary":"Increased Error Rates","status":"1","timestamp":1787152514},{"message":"On August 18 we launched a new Availability Zone (euw2-az4) in the EU-WEST-2 Region. After the launch, we began experiencing errors launching EC2 instances in the new Availability Zone when a default subnet is not present. We can confirm that existing running instances and resources are not affected. Workflows that automatically get a list of Availability Zones in the Region via the DescribeAvailabilityZones API and then attempt to launch new instances or create resources in the new Availability Zone may encounter errors. For EC2 instance launch failures, we are taking mitigating steps to automatically create default subnets, where one is not already present, when an EC2 instance launch is targeting the new Availability Zone. For customers and workflows that require immediate remediation <a href=\"https://docs.aws.amazon.com/vpc/latest/userguide/work-with-default-vpc.html#create-default-subnet\">you may create a default subnet</a> in the new Availability Zone. This will enable EC2 instance launches to successfully complete. \n\nFor other resources, such as Lambda functions, where the new Availability Zone is currently not supported, we recommend customers update their workflows to exclude the newly launched Availability Zone and continue resource creation using the other Availability Zones in the Region. While we don't have an exact estimate for how long our mitigation efforts will take, we will keep you up to date on our progress and provide you with another update by 1:00 PM PDT or sooner as new information becomes available.","summary":"Increased Error Rates","status":"1","timestamp":1787159039},{"message":"Between August 18 5:00 PM and August 19 11:00 AM PDT, we experienced elevated errors launching EC2 instances in a newly launched Availability Zone (euw2-az4) in the EU-WEST-2 Region. After the new Availability Zone launch, we began experiencing errors when using a default VPC. We discovered the root cause of the issue on August 19 at 9:00 AM and began deploying a change to resolve the issue at 9:30 AM. While the change was underway, we began to see incremental improvements in new instance launches, with full recovery at 11:00 AM. Existing running instances and resources were not affected. \n\nSome regional services, such as Lambda functions or Aurora databases, were not available at the launch of the new Availability Zone and service availability will be added over time. Customers attempting to create resources before the services become available will see a message reporting that it is not supported in the Availability Zone. \n\nThe issue has been resolved and the service is operating normally.","summary":"[RESOLVED] Increased Error Rates","status":"0","timestamp":1787165240}]}],"directconnect-eu-central-1":[{"summary":"[RESOLVED] Increased Packet loss","arn":"arn:aws:health:eu-central-1::event/DIRECTCONNECT/AWS_DIRECTCONNECT_OPERATIONAL_ISSUE/AWS_DIRECTCONNECT_OPERATIONAL_ISSUE_E23AA_ADAB9D3D11F","status":"1","date":"1786765379","event_log":[{"message":"We are investigating increased packet loss, impacting AWS Direct Connect connectivity for some customers in the EU-CENTRAL-1 Region.","summary":"Increased Packet loss","status":"1","timestamp":1786765379},{"message":"We can confirm packet loss impacting Direct Connect connections in the EU-CENTRAL-1 Region. Engineers were automatically engaged and immediately began working to both identify the root cause, and identify multiple parallel paths to mitigate the issue. At this time, we are seeing early signs of recovery. We will provide another update in 60 minutes, or sooner if we have additional information to share.","summary":"Increased Packet loss","status":"1","timestamp":1786768970},{"message":"Starting at 7:33 PM PDT, we began experiencing increased packet loss impacting AWS Direct Connect connectivity for some customers in the EU-CENTRAL-1 Region. While we have made progress, connections to the following Direct Connect location are still impaired: Equinix FR5, Frankfurt, DEU. Customers who have multi-site redundancy configured with their Direct Connect paths should not be observing impact at this time. Customers whom only have connections at the Equinix FR5, Frankfurt, DEU location will continue to experience connectivity issues. We are actively working to mitigate the impact and work toward full recovery, but expect full recovery is multiple hours away. We will provide an update in 90 minutes, or sooner if we have additional information to share.","summary":"Increased Packet loss","status":"1","timestamp":1786773313},{"message":"We are actively working to restore connectivity through the Direct Connect location: Equinix FR5, Frankfurt, DEU. Customers whom only have connections at the Equinix FR5, Frankfurt, DEU location will continue to experience connectivity issues. For a workaround impacted customers who have the option available to failover to VPN are recommended to do so to achieve recovery. For customers using Direct Connect gateway and Transit Gateway, we recommend creating a AWS Site-to-Site VPN and attach it to your Transit Gateway, refer steps <a href=\"https://aws.amazon.com/premiumsupport/knowledge-center/dx-configure-dx-and-vpn-failover-tgw/\">here</a>. For other customers we recommend establishing a AWS Site-to-Site VPN as a temporary backup path,  refer steps <a href=\"https://docs.aws.amazon.com/vpn/latest/s2svpn/SetUpVPNConnections.html\">here</a>. As of this time, we expect recovery is multiple hours away. We will provide another update in 90 minutes, or sooner if we have additional information to share.","summary":"Increased Packet loss","status":"1","timestamp":1786778668},{"message":"We continue to work towards recovery of connectivity for AWS Direct Connect connections at Equinix FR5, Frankfurt, DEU. The root cause is related to a facility infrastructure issue at the location that is impacting network infrastructure. Customers with connections solely at this location will continue to experience packet loss or connectivity degradation. Customers with multi-site or redundant configurations across other locations are not impacted. For a workaround, impacted customers who have the option available to failover to VPN are recommended to do so. For customers using Direct Connect gateway and Transit Gateway, we recommend creating a AWS Site-to-Site VPN and attaching it to your Transit Gateway, refer to steps <a href=\"https://aws.amazon.com/premiumsupport/knowledge-center/dx-configure-dx-and-vpn-failover-tgw/\">here</a>. For other customers we recommend establishing an AWS Site-to-Site VPN as a temporary backup path, refer to steps <a href=\"https://docs.aws.amazon.com/vpn/latest/s2svpn/SetUpVPNConnections.html\">here</a>. As of this time, we expect recovery is multiple hours away. We will provide another update within 2 hours or as soon as we have more information to share.","summary":"Increased Packet loss","status":"1","timestamp":1786784894},{"message":"AWS Direct Connect connectivity remains impaired for customers with connections at the Equinix FR5 location in Frankfurt, DEU. Customers with multi-site or redundant configurations across other locations continue to be unaffected. Engineers are actively working to restore connectivity, with efforts ongoing across multiple workstreams to resolve the underlying facility issue and bring the impacted network equipment back into service. We continue to expect recovery is multiple hours away. For a workaround, impacted customers who have the option to failover to VPN are recommended to do so. For customers using Direct Connect gateway and Transit Gateway, we recommend creating a AWS Site-to-Site VPN and attaching it to your Transit Gateway, refer to steps <a href=\"https://aws.amazon.com/premiumsupport/knowledge-center/dx-configure-dx-and-vpn-failover-tgw/\">here</a>. For other customers we recommend establishing an AWS Site-to-Site VPN as a temporary backup path, refer to steps <a href=\"https://docs.aws.amazon.com/vpn/latest/s2svpn/SetUpVPNConnections.html\">here</a>. We will provide another update within 2 hours or as soon as we have more information to share.","summary":"Increased Packet loss","status":"1","timestamp":1786792229},{"message":"Engineers continue work to restore connectivity at Equinix FR5 location in Frankfurt, DEU. Our co-location partner is working to resolve the underlying facility infrastructure issue and while the improvements are not yet customer visible, we are making positive progress towards resolution. For customers who require immediate recovery, we recommend failing over to VPN, as outlined in our previous updates. We will provide another update by 9:30 AM PDT, or sooner if we have additional information to share.","summary":"Increased Packet loss","status":"1","timestamp":1786799870},{"message":"Our co-location partner continues to work to resolve the underlying facility infrastructure issue at the Equinix FR5 location in Frankfurt, DEU. Access to the affected area is currently restricted due to safety concerns, which is impacting our ability to assess the physical condition of the network equipment and provide a more accurate recovery timeline. Based on current information, full recovery is not expected in the near term and may extend beyond today. AWS Direct Connect connections at this location remain impaired. Customers with redundant connections through other locations remain unaffected. For customers using Direct Connect gateway and Transit Gateway, we recommend creating a AWS Site-to-Site VPN and attaching it to your Transit Gateway, refer to steps <a href=\"https://aws.amazon.com/premiumsupport/knowledge-center/dx-configure-dx-and-vpn-failover-tgw/\">here</a>. For other customers we recommend establishing an AWS Site-to-Site VPN as a temporary backup path, refer to steps <a href=\"https://docs.aws.amazon.com/vpn/latest/s2svpn/SetUpVPNConnections.html\">here</a>. We will provide another update by 3:30 PM PDT, or sooner if we have additional information to share.","summary":"Increased Packet loss","status":"1","timestamp":1786811261},{"message":"Our co-location partner is continuing work to restore safe access to the affected area at the Equinix FR5 location in Frankfurt, DEU. Once safe access has been secured, our engineers will be able to assess the affected network devices. We continue to closely track progress and will share an update by 9:30 PM PDT, or sooner as new information becomes available.","summary":"Increased Packet loss","status":"1","timestamp":1786832802},{"message":"We are actively engaged with our co-location partner to restore connectivity at Equinix FR5 location in Frankfurt, DEU. Since our last update, we have made incremental progress to restore safe access to the affected area at the Equinix FR5 location in Frankfurt, DEU. In parallel, we have prioritized the order in which critical and high-priority racks will be restored, as part of the mitigation efforts. Based on our current assessment, full recovery is not expected in the near term and may extend beyond today. AWS Direct Connect connections at this location remain impaired. Customers with connections exclusively at this location will continue to experience packet loss. Customers with multi-site or redundant configurations across other Direct Connect locations remain unaffected. For a workaround, impacted customers who have the option available to failover to VPN are recommended to do so. For customers using Direct Connect gateway and Transit Gateway, we recommend creating a AWS Site-to-Site VPN and attaching it to your Transit Gateway, refer to steps <a href=\"https://aws.amazon.com/premiumsupport/knowledge-center/dx-configure-dx-and-vpn-failover-tgw/\">here</a>. For other customers we recommend establishing an AWS Site-to-Site VPN as a temporary backup path, refer to steps <a href=\"https://docs.aws.amazon.com/vpn/latest/s2svpn/SetUpVPNConnections.html\">here</a>. We continue to closely track progress and will share an update by August 16 3:30 AM PDT, or sooner as new information becomes available.","summary":"Increased Packet loss","status":"1","timestamp":1786855067},{"message":"We continue to work with our co-location partner to restore connectivity at the Equinix FR5 location in Frankfurt, DEU. Since our last update, we have made significant progress toward restoring safe access to the affected area. The electrical isolation procedure is now underway, with our teams on site in the electrical room executing the de-energization of the affected infrastructure. Once isolation is verified and confirmed safe, engineers will begin a physical inspection of the impacted network equipment to determine the scope of replacement required. \n\nBased on our current assessment, full recovery is not expected in the near term due to the scope of potential impacted to equipment. AWS Direct Connect connections at this location remain impaired. Customers with connections exclusively at this location will continue to experience packet loss. Customers with multi-site or redundant configurations across other Direct Connect locations remain unaffected. For a workaround, impacted customers who have the option available to failover to VPN are recommended to do so. For customers using Direct Connect gateway and Transit Gateway, we recommend creating a AWS Site-to-Site VPN and attaching it to your Transit Gateway, refer to steps <a href=\"https://aws.amazon.com/premiumsupport/knowledge-center/dx-configure-dx-and-vpn-failover-tgw/\">here</a>. For other customers we recommend establishing an AWS Site-to-Site VPN as a temporary backup path, refer to steps <a href=\"https://docs.aws.amazon.com/vpn/latest/s2svpn/SetUpVPNConnections.html\">here</a>. We continue to closely track progress and will share an update by August 16 9:30 AM PDT, or sooner as new information becomes available.","summary":"Increased Packet loss","status":"1","timestamp":1786875932},{"message":"The electrical isolation at Equinix FR5 in Frankfurt, DEU is now complete and our engineers have begun physically inspecting the impacted network equipment. We do not yet have a timeline for full resolution while we continue to assess the extent of impact to equipment.\n\nDirect Connect connections at this location remain impaired. Customers with connections exclusively at this location will continue to experience packet loss. Customers with multi-site or redundant configurations across other Direct Connect locations are not affected.\n\nWe recommend that impacted customers failover to VPN until we have more clarity on next steps and a recovery timeline. For customers using Direct Connect gateway and Transit Gateway, you can create an AWS Site-to-Site VPN and attach it to your Transit Gateway, refer to steps <a href=\"https://aws.amazon.com/premiumsupport/knowledge-center/dx-configure-dx-and-vpn-failover-tgw/\">here</a>. For other customers, we recommend establishing an AWS Site-to-Site VPN as a temporary backup path, refer to steps <a href=\"https://docs.aws.amazon.com/vpn/latest/s2svpn/SetUpVPNConnections.html\">here</a>. \n\nWe will provide another update by August 16 5:30 PM PDT, or sooner as new information becomes available.","summary":"Increased Packet loss","status":"1","timestamp":1786897839},{"message":"We have completed our assessment of the impacted network equipment at the Equinix FR5 location in Frankfurt, DEU and now have a clear understanding of the scope of impact. We are making progress toward restoring connectivity and will be taking a phased approach to remediation.\n\nCustomers with connections exclusively at this location will continue to experience packet loss until remediation is complete. Customers with multi-site or redundant configurations across other Direct Connect locations are not affected.\n\nWe will provide another update by August 16 10:30 PM PDT, or sooner as new information becomes available.","summary":"Increased Packet loss","status":"1","timestamp":1786920667},{"message":"We continue to make progress in our phased remediation at the Equinix FR5 location in Frankfurt, DEU. Since our last update, some dependent network infrastructure has been restored. Remediation of remaining infrastructure is ongoing, with a portion of recovery dependent on the delivery of replacement hardware. Cooling has been fully restored, with environmental conditions stable within normal operating thresholds.\n\nCustomers with connections exclusively at this location will continue to experience packet loss as remediation progresses. Customers with multi-site or redundant configurations across other Direct Connect locations are not affected. Previously communicated mitigation guidance and recommendations remain unchanged at this time. We will provide another update by August 17 4:30 AM PDT, or sooner as remediation progresses.","summary":"Increased Packet loss","status":"1","timestamp":1786945084},{"message":"We continue to make progress in our phased remediation at the Equinix FR5 location in Frankfurt, DEU. Network infrastructure and dependent systems continue to improve as we bring affected hardware back online. Some replacement hardware has been delivered and installation is proceeding as components arrive on-site. In parallel, we are shifting network traffic to allow restored devices to begin serving customers as they come online. \n\nAs we progress through recovery, customers will observe restoration occurring in two stages. In the first stage, BGP sessions will re-establish but IP prefixes will not yet be advertised, this indicates that recovery is still in progress and the underlying infrastructure is not yet ready to carry traffic. In the second stage, IP prefix advertisement will resume, at which point the infrastructure is fully remediated and connectivity is restored.\n\nWhile we do not currently have an ETA for full recovery, we continue to work as quickly and safely as possible to mitigate the impact for customers. We will provide another update by August 17 10:30 AM PDT, or sooner as remediation progresses.","summary":"Increased Packet loss","status":"1","timestamp":1786965750},{"message":"We continue to work on phased remediation incrementally at the Equinix FR5 location in Frankfurt, DEU. We are seeing early signs of recovery while we continue to fully remediate the issue. We are actively working to bring the remaining affected hardware back online and we will provide another update by 12:30 PM PDT, or sooner as remediation progresses.","summary":"Increased Packet loss","status":"1","timestamp":1786983922},{"message":"We are seeing broad signs of recovery at the Equinix FR5 location in Frankfurt, DEU. We have restored connectivity for the majority of affected hardware and most of the connections are fully recovered and stable. There are a small number of customers that will remain affected until the remaining devices are fully restored. We will provide another update by 2:00 PM PDT, or sooner as remediation progresses.","summary":"Increased Packet loss","status":"1","timestamp":1786989560},{"message":"We continue to work on bringing affected hardware back online. Since our last update we have made progress that will not be visible to customers, but is required for recovery. We are working in parallel to bring all devices online as safely as possible. This work is expected to take several hours to complete and validate.\n\nFor customers that require workarounds, we recommend that you consider failing over to VPN. For customers using Direct Connect gateway and Transit Gateway, you can create an AWS Site-to-Site VPN and attach it to your Transit Gateway, refer to steps <a href=\"https://aws.amazon.com/premiumsupport/knowledge-center/dx-configure-dx-and-vpn-failover-tgw/\">here</a>. For other customers, we recommend establishing an AWS Site-to-Site VPN as a temporary backup path, refer to steps <a href=\"https://docs.aws.amazon.com/vpn/latest/s2svpn/SetUpVPNConnections.html\">here</a>.\n\nWe will provide another update by 7:00 PM PDT or sooner as new information becomes available.","summary":"Increased Packet loss","status":"1","timestamp":1787000411},{"message":"We are seeing significant recovery for most of the customer connections at this stage. While we are not yet fully recovered, restoration efforts are progressing as expected at the Equinix FR5 location in Frankfurt, DEU. Remediation of remaining infrastructure involves completion of hardware replacements and traffic validation, both of which are actively underway. We anticipate further customer-visible recovery as the remaining infrastructure is brought back into service. \n\nCustomers with connections exclusively at this location will continue to experience packet loss until remediation is complete. Previously communicated mitigation guidance and recommendations remain unchanged at this time. We will provide another update by August 17 11:00 PM PDT or sooner.","summary":"Increased Packet loss","status":"1","timestamp":1787017812},{"message":"Starting August 14 7:33 PM PDT, we experienced increased packet loss impacting AWS Direct Connect connectivity for customers with connections at the Equinix FR5 location in Frankfurt, DEU. Engineers were automatically engaged at 7:45 PM on August 14 and immediately began investigating mitigations. By 8:30 PM, we identified that network equipment at the FR5 location was impaired due to water ingress into the co-location facility. As a result, cooling system was impaired which resulted in devices overheating and shutting down. Water also affected power distribution systems which disabled the power for the network devices. Initial recovery efforts were delayed as environmental conditions within the facility required stabilization before engineers could safely access the affected area. Throughout August 15 and 16, our engineers worked in coordination with the facility operator to restore impaired network devices while the underlying infrastructure issue was addressed. By 7:26 PM on August 17, all impaired network equipment was successfully restored and connectivity to the location was verified as fully operational with sustained recovery. We do not expect this issue to recur. \n\nCustomers with redundant connections across other Direct Connect locations maintained connectivity through their alternate paths throughout this event and require no further action. Customers who implemented VPN failover as a workaround may now safely revert to their primary Direct Connect paths. Connectivity has been verified as stable and fully operational. Customers requiring further assistance may contact AWS Support through the AWS Management Console or the <a href=\"https://console.aws.amazon.com/support\">AWS Support Center</a>.","summary":"[RESOLVED] Increased Packet loss","status":"0","timestamp":1787025679}]}],"directconnect-ap-south-1":[{"summary":"[RESOLVED] Elevated Packet Loss","arn":"arn:aws:health:ap-south-1::event/DIRECTCONNECT/AWS_DIRECTCONNECT_OPERATIONAL_ISSUE/AWS_DIRECTCONNECT_OPERATIONAL_ISSUE_00B73_1C6411F1489","status":"1","date":"1785519198","event_log":[{"message":"We can confirm elevated network packet loss, impacting AWS Direct Connect connectivity in AP-SOUTH-1 Region. Our engineering team was automatically engaged at 9:54 AM to begin investigating the issue. There are no workarounds available at this time. We will provide another update by 11:30 AM PDT.","summary":"Elevated Packet Loss","status":"1","timestamp":1785519198},{"message":"We have identified the root cause to be related to a change made to a configuration system responsible for assigning routes to the devices. We have begun the work to reduce the packet loss that is impacting AWS Direct Connect in the AP-SOUTH-1 Region, and we expect recovery to take place gradually over the next 30 minutes. As we gain confidence in these efforts, we will seek to parallelize our efforts to speed recovery. We will provide another update by 12:00 PM PDT.","summary":"Elevated Packet Loss","status":"1","timestamp":1785522444},{"message":"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.","summary":"[RESOLVED] Elevated Packet Loss","status":"0","timestamp":1785524075}]}],"billingconsole":[{"summary":"[RESOLVED] Inaccurate Estimated Billing Data","arn":"arn:aws:health:global::event/BILLING/AWS_BILLING_OPERATIONAL_ISSUE/AWS_BILLING_OPERATIONAL_ISSUE_47B68_BACBD91434F","status":"1","date":"1784277216","event_log":[{"message":"We are investigating issues with Cost Explorer reflecting inaccurate estimated billing data.","summary":"Inaccurate Estimated Billing Data","status":"1","timestamp":1784277216},{"message":"Beginning on July 16 7:38 PM PDT, we began displaying incorrect estimated billing data in the Billing and Cost Management Console. Our engineering teams are engaged and investigating root cause. We will provide another update by 3:00 AM PDT or sooner if more information becomes available.","summary":"Inaccurate Estimated Billing Data","status":"1","timestamp":1784279253},{"message":"We continue to work to resolve the issue affecting estimated cost and usage data displayed in the Billing and Cost Management Console. We have identified the root cause as an issue with unit pricing within the estimated billing computation subsystem and we are working on a mitigation. The displayed billing estimates do not reflect actual usage and charges. There are no customer actions required at this time. Once the issue has been mitigated, we expect full resolution to take multiple hours as we work through recomputing the estimated billing data. We will provide another update by 4:00 AM PDT or sooner if more information becomes available.","summary":"Inaccurate Estimated Billing Data","status":"1","timestamp":1784282606},{"message":"We continue to work to resolve the issue affecting estimated cost and usage data displayed in the Billing and Cost Management Console. As previously shared, we have identified the root cause as an issue with unit pricing within the estimated billing computation subsystem. To prevent further inaccurate billing estimates from being displayed, we have paused estimated billing computations. Customers who are currently seeing normal bill estimates will continue to see those estimates, and customers who are seeing inflated estimates will not see them increase further while we work toward resolution. The displayed billing estimates do not reflect actual usage and charges. We continue to work on fully mitigating the issue. Once the issue has been mitigated, we expect full resolution to take multiple hours as we work through recomputing the estimated billing data. There are no customer actions required at this time. We will provide another update by 5:00 AM PDT or sooner if more information becomes available.","summary":"Inaccurate Estimated Billing Data","status":"1","timestamp":1784285568},{"message":"We continue to work to resolve the issue affecting estimated cost and usage data displayed in the Billing and Cost Management Console. We are actively working on multiple mitigation paths in parallel. The first path involves reverting to the last known good estimated bill computation. With this approach, customers will only see cost and usage data through July 15, however the inflated cost data will be removed. The second path involves rolling back a recent change to the billing computation subsystem. The displayed billing estimates do not reflect actual usage and charges. There are no customer actions required at this time. Once the issue has been mitigated, we expect full resolution to take multiple hours as we work through recomputing the estimated billing data. We will provide another update by 6:00 AM PDT or sooner if more information becomes available.","summary":"Inaccurate Estimated Billing Data","status":"1","timestamp":1784289519},{"message":"We continue to work on multiple mitigation paths in parallel to resolve the issue affecting estimated cost and usage data displayed in the Billing and Cost Management Console, including the Cost and Usage Report. We are evaluating resuming estimated billing computations, as our internal monitoring indicates the billing computation subsystem is now producing accurate estimates. We are conducting additional validation before proceeding with this path. The displayed billing estimates do not reflect actual usage and charges. There are no customer actions required at this time. We will provide another update by 8:00 AM PDT or sooner if more information becomes available.","summary":"Inaccurate Estimated Billing Data","status":"1","timestamp":1784292886},{"message":"We continue to work to resolve the issue affecting estimated cost and usage data displayed in the Billing and Cost Management Console, including the Cost and Usage Report. The rollback of a recent change did not resolve the issue and we are continuing to investigate multiple mitigation paths. Estimated bill updates remain paused. We are in the process of reverting to the last accurate estimated billing data. The displayed billing estimates do not reflect actual usage and charges. There are no customer actions required at this time. We expect this mitigation to take several hours to complete as we work through recomputing the estimated billing data. We will provide another update by 10:00 AM PDT or sooner if more information becomes available.","summary":"Inaccurate Estimated Billing Data","status":"1","timestamp":1784299988},{"message":"We have identified the root cause and mitigated the underlying issue causing incorrect estimated cost and usage data to be displayed in the Billing and Cost Management Console, and Cost and Usage Reports. We have begun backfilling data to correct cost data for all customers. We expect some customers to begin seeing recovery within the next three hours, and full recovery for all customers by July 18 12:00 PM PDT. Until the backfill is complete, some customers may still see incorrect cost and usage data. The displayed billing estimates do not reflect actual usage and charges. There are no customer actions required at this time. We will provide another update by 1:00 PM, or sooner if information becomes available.","summary":"Inaccurate Estimated Billing Data","status":"1","timestamp":1784307576},{"message":"Our efforts to backfill corrected estimated cost and usage data are still underway. We are progressing slower than anticipated. While we are seeing some accounts recover with correct cost and usage data, we expect all affected accounts to be recovered by July 19 12:00 AM PDT. Until the backfill is complete, some customers may still see incorrect cost and usage data. The displayed billing estimates do not reflect actual usage and charges. There are no customer actions required at this time. We will provide another update by 7:00 PM, or sooner if information becomes available.","summary":"Inaccurate Estimated Billing Data","status":"1","timestamp":1784318178},{"message":"We continue to make steady progress toward resolving the issue affecting estimated cost and usage data displayed in the Billing and Cost Management Console. Our efforts to backfill corrected data remain underway, and we expect all affected accounts to be fully recovered by July 19, 12:00 AM PDT. Until the backfill is complete, some customers may still observe incorrect cost and usage data in the Billing and Cost Management Console and Cost and Usage Reports. These estimates do not reflect actual usage or charges. Customers who configured their Cost and Usage Report with the \"Overwrite\" option require no action — their report will be automatically updated with corrected data once the backfill completes. Customers who configured their Cost and Usage Report with the \"Create new report versions\" option retain all previous report deliveries in their S3 bucket. The report version delivered during the impacted window may contain inaccurate data. Once the data backfill is complete, a corrected report version will be delivered under a new assemblyId. Customers using this configuration should update any downstream processes (Athena tables, Redshift pipelines, Amazon QuickSight, or custom ETL) to reference the latest assemblyId for the affected billing period, and may delete or archive the impacted report version to prevent processing stale data. To identify the latest report, customers can follow the steps in our <a href=\"https://docs.aws.amazon.com/cur/latest/userguide/view-latest-cur.html\">documentation</a>. We will provide another update by July 18, 1:00 AM PDT, or sooner if additional information becomes available.","summary":"Inaccurate Estimated Billing Data","status":"1","timestamp":1784338681},{"message":"We continue to make substantial progress toward resolving the issue affecting estimated cost and usage data displayed in the Billing and Cost Management Console. Our mitigation efforts are working as expected and we are seeing an increasing number of accounts reflecting correct cost and usage data. We expect all affected accounts to be fully recovered by July 19, 12:00 AM PDT. Until the backfill is complete, some customers may still observe incorrect cost and usage data in the Billing and Cost Management Console and Cost and Usage Reports. These estimates do not reflect actual usage or charges. We will provide another update by July 18, 7:00 AM PDT, or sooner if additional information becomes available.","summary":"Inaccurate Estimated Billing Data","status":"1","timestamp":1784361935},{"message":"Between July 16 at 7:38 PM PDT and July 18 at 6:00 AM PDT, we began displaying incorrect estimated billing data in the Billing and Cost Management Console, including the Cost and Usage Report. Customers may have received erroneous budget and cost anomaly detection alerts, and observed inflated estimated cost and usage data.\n\nOn July 16 at 7:46 PM PDT, our alarms detected cost anomalies but failed to halt the estimated bill generation process or alert our engineering teams. We were alerted to this issue on July 17 at 12:19 AM PDT by customer escalations, and immediately began to investigate. We first informed customers via AWS Health on July 17 at 1:33 AM. 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.\n\nWe identified the root cause on July 17 at 12:00 PM PDT as 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 budget and cost anomaly alerts.\n\nWe mitigated the issue on July 17 at 12:30 PM PDT which corrected the unit conversion configuration, and began reprocessing cost and usage data for all customer accounts. We started observing recovery at 4:19 PM PDT, and the majority of accounts were fully recovered by July 18 at 6:00 AM PDT. There are 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. \n\nWe apologize for the alarm this incident caused our customers and are conducting a thorough retrospective to prevent events like this from reoccurring, as well as improve our response when billing incidents occur. The issue has been resolved and all AWS services are now operating normally.","summary":"[RESOLVED] Inaccurate Estimated Billing Data","status":"0","timestamp":1784383061}]}],"cloudfront":[{"summary":"[RESOLVED] Change Propagation Delays","arn":"arn:aws:health:global::event/CLOUDFRONT/AWS_CLOUDFRONT_OPERATIONAL_ISSUE/AWS_CLOUDFRONT_OPERATIONAL_ISSUE_5D2B3_81D5FA9EA2B","status":"1","date":"1770758100","event_log":[{"message":"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.","summary":"Increased Error Rates and Latencies","status":"1","timestamp":1770758100},{"message":"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 CloudFront distributions for delivering content may also be affected at this time.","summary":"Increased Error Rates and Latencies","status":"1","timestamp":1770759600},{"message":"We are seeing early signs of recovery, and continue to work toward full recovery.","summary":"Increased Error Rates and Latencies","status":"1","timestamp":1770759960},{"message":"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.","summary":"Increased Error Rates and Latencies","status":"1","timestamp":1770760680},{"message":"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.","summary":"Increased Error Rates and Latencies","status":"1","timestamp":1770762840},{"message":"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. ","summary":"Change Propagation Delays","status":"1","timestamp":1770764785},{"message":"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. ","summary":"Change Propagation Delays","status":"1","timestamp":1770768120},{"message":"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.","summary":"Change Propagation Delays","status":"1","timestamp":1770771707},{"message":"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.","summary":"Change Propagation Delays","status":"1","timestamp":1770775603},{"message":"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. ","summary":"Change Propagation Delays","status":"1","timestamp":1770779215},{"message":"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 certificate related changes. Following mitigation of the DNS resolution errors at 1:55 PM, end-user requests for content delivery from our edge locations were not affected and are being served normally. Invalidations operated normally throughout the event. Both issues have been resolved and all services are operating normally. We are confident this issue will not reoccur.","summary":"[RESOLVED] Change Propagation Delays","status":"0","timestamp":1770783512}],"impacted_services":{"apigateway":{"service_name":"Amazon API Gateway","current":"0","max":"1"},"appsync":{"service_name":"AWS AppSync","current":"0","max":"1"},"awswaf":{"service_name":"AWS WAF","current":"0","max":"1"},"pinpoint":{"service_name":"Amazon Pinpoint","current":"0","max":"1"},"route53":{"service_name":"Amazon Route 53","current":"0","max":"1"},"transfer":{"service_name":"AWS Transfer Family","current":"0","max":"1"},"vpclattice":{"service_name":"Amazon VPC Lattice","current":"0","max":"1"}}},{"summary":"[RESOLVED] Increased 5xx Errors","arn":"arn:aws:health:global::event/CLOUDFRONT/AWS_CLOUDFRONT_OPERATIONAL_ISSUE/AWS_CLOUDFRONT_OPERATIONAL_ISSUE_EDF4C_83808542A4E","status":"2","date":"1784191440","event_log":[{"message":"We are investigating increased 5xx errors for Cloudfront customers utilizing VPC Origins connectivity. ","summary":"Increased 5xx Errors","status":"1","timestamp":1784191440},{"message":"Starting at 12:45 AM PDT, we are experiencing increased 5xx errors for CloudFront customers utilizing VPC Origins connectivity. We have confirmed that customers utilizing other origin types are not impacted by this issue. Our engineers are engaged and are actively working to mitigate impact. As a workaround, customers who do not require VPC Origins can change their origin type to resolve the errors. We will provide another update by 3:15 AM PDT, or sooner if more information becomes available.","summary":"Increased 5xx Errors","status":"1","timestamp":1784193679},{"message":"We continue working to resolve the increased 5xx errors for CloudFront customers utilizing VPC Origins connectivity. Customers utilizing other origin types remain unaffected by this issue. Based on our investigation, we believe the root cause is related to a packet processing subsystem responsible for routing requests from CloudFront's edge locations to resources within customer VPCs. We continue to recommend that customers who are able to do so temporarily change their origin type to resolve the errors. We will provide another update by 4:15 AM PDT, or sooner if additional information becomes available.","summary":"Increased 5xx Errors","status":"2","timestamp":1784197113},{"message":"We continue working to resolve the increased 5xx errors for CloudFront customers utilizing VPC Origins connectivity. Customers utilizing other origin types remain unaffected by this issue. We have further scoped the issue down to routing table capacity within the packet processing subsystem responsible for routing requests from CloudFront's edge locations to resources within customer VPCs. We have identified and are currently testing a mitigation strategy to resolve the issue. Once testing is complete, we will deploy the mitigation in a phased approach. Based on the results from these tests, we will provide a clearer estimated time for resolution in our next update. We continue to recommend that customers who are able to do so temporarily change their origin type to resolve the errors. We will provide another update by 5:15 AM PDT, or sooner if additional information becomes available.","summary":"Increased 5xx Errors","status":"2","timestamp":1784200565},{"message":"We are seeing initial signs of recovery and continue to work toward full recovery.","summary":"Increased 5xx Errors","status":"2","timestamp":1784201243},{"message":"We continue to see significant signs of recovery as a result of our mitigation efforts, with full recovery expected within the next 45 minutes.","summary":"Increased 5xx Errors","status":"1","timestamp":1784203045},{"message":"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.","summary":"[RESOLVED] Increased 5xx Errors","status":"0","timestamp":1784204519}]}],"multipleservices-eu-central-1":[{"summary":"[RESOLVED] Elevated connectivity issues with a single Avalability zone","arn":"arn:aws:health:eu-central-1::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_25DBE_2EF1D48B613","status":"1","date":"1784157067","event_log":[{"message":"We are investigating elevated connectivity issues with a single Avalability zone (euc1-az2) in the EU-CENTRAL-1 Region.","summary":"Elevated connectivity issues with a single Avalability zone","status":"1","timestamp":1784157067},{"message":"We are seeing early signs of recovery and continue to work toward full resolution. We will continue to provide updates.","summary":"Elevated connectivity issues with a single Avalability zone","status":"1","timestamp":1784158561},{"message":"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.","summary":"[RESOLVED] Elevated connectivity issues with a single Avalability zone","status":"0","timestamp":1784165075}],"impacted_services":{"ec2-eu-central-1":{"service_name":"Amazon Elastic Compute Cloud","current":"0","max":"1"},"elasticache-eu-central-1":{"service_name":"Amazon ElastiCache","current":"0","max":"1"},"kafka-eu-central-1":{"service_name":"Amazon Managed Streaming for Apache Kafka","current":"0","max":"1"},"rds-eu-central-1":{"service_name":"Amazon Relational Database Service","current":"0","max":"1"},"sagemaker-eu-central-1":{"service_name":"Amazon SageMaker","current":"0","max":"1"}},"impacted_service_status_changes":[{"service":"ec2-eu-central-1","service_name":"Amazon Elastic Compute Cloud","previous_status":"0","current_status":"1","timestamp":1784157067000},{"service":"elasticache-eu-central-1","service_name":"Amazon ElastiCache","previous_status":"0","current_status":"1","timestamp":1784157067000},{"service":"kafka-eu-central-1","service_name":"Amazon Managed Streaming for Apache Kafka","previous_status":"0","current_status":"1","timestamp":1784157067000},{"service":"rds-eu-central-1","service_name":"Amazon Relational Database Service","previous_status":"0","current_status":"1","timestamp":1784157067000},{"service":"sagemaker-eu-central-1","service_name":"Amazon SageMaker","previous_status":"0","current_status":"1","timestamp":1784157067000},{"service":"ec2-eu-central-1","service_name":"Amazon Elastic Compute Cloud","previous_status":"1","current_status":"0","timestamp":1784165075000},{"service":"elasticache-eu-central-1","service_name":"Amazon ElastiCache","previous_status":"1","current_status":"0","timestamp":1784165075000},{"service":"kafka-eu-central-1","service_name":"Amazon Managed Streaming for Apache Kafka","previous_status":"1","current_status":"0","timestamp":1784165075000},{"service":"rds-eu-central-1","service_name":"Amazon Relational Database Service","previous_status":"1","current_status":"0","timestamp":1784165075000},{"service":"sagemaker-eu-central-1","service_name":"Amazon SageMaker","previous_status":"1","current_status":"0","timestamp":1784165075000}]}],"ec2-us-east-1":[{"summary":"[RESOLVED] Increased API Error Rates","arn":"arn:aws:health:us-east-1::event/EC2/AWS_EC2_OPERATIONAL_ISSUE/AWS_EC2_OPERATIONAL_ISSUE_4E29E_52D07C27DA6","status":"1","date":"1757586563","event_log":[{"message":"We are investigating increased API error rates in the US-EAST-1 Region.","summary":"Increased API Error Rates","status":"1","timestamp":1757586563},{"message":"Starting at 3:01 AM PDT, we began experiencing increased API error rates in the US-EAST-1 Region. Engineering teams were engaged immediately and successfully mitigated the issue by 3:30 AM PDT, with subsequent full recovery by 3:40 AM PDT. The issue has been resolved and the service is operating normally.","summary":"[RESOLVED] Increased API Error Rates","status":"0","timestamp":1757588393}],"impacted_services":{"datasync-us-east-1":{"service_name":"AWS DataSync","current":"0","max":"1"},"ecs-us-east-1":{"service_name":"Amazon Elastic Container Service","current":"0","max":"1"},"eks-us-east-1":{"service_name":"Amazon Elastic Kubernetes Service","current":"0","max":"1"},"kafka-us-east-1":{"service_name":"Amazon Managed Streaming for Apache Kafka","current":"0","max":"1"},"lightsail-us-east-1":{"service_name":"Amazon Lightsail","current":"0","max":"1"},"sagemaker-us-east-1":{"service_name":"Amazon SageMaker","current":"0","max":"1"},"transitgateway-us-east-1":{"service_name":"AWS Transit Gateway","current":"0","max":"1"},"vpclattice-us-east-1":{"service_name":"Amazon VPC Lattice","current":"0","max":"1"}}},{"summary":"[RESOLVED] Intermittent missing or delayed EC2 instance and status check metrics","arn":"arn:aws:health:us-east-1::event/EC2/AWS_EC2_OPERATIONAL_ISSUE/AWS_EC2_OPERATIONAL_ISSUE_E54AB_1F72578856F","status":"1","date":"1772043269","event_log":[{"message":"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.","summary":"Intermittent missing or delayed EC2 instance and status check metrics","status":"1","timestamp":1772043269},{"message":"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 recover an instance. More information is available <a href=\"https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/UsingAlarmActions.html\">here</a>. While we do not have a firm ETA for resolution, we will provide another update by 12:30 PM, or sooner if we have additional information to share.","summary":"Intermittent missing or delayed EC2 instance and status check metrics","status":"1","timestamp":1772047680},{"message":"We are seeing early signs of recovery and continue to work toward full resolution. We will continue to provide updates.","summary":"Intermittent missing or delayed EC2 instance and status check metrics","status":"1","timestamp":1772050225},{"message":"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.","summary":"Intermittent missing or delayed EC2 instance and status check metrics","status":"1","timestamp":1772051589},{"message":"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.\n\nWe 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 recovery at 12:05 PM. New metrics are being published as expected. Delayed metrics are in the process of backfilling and may take a few hours to fully complete. The issue has been resolved and the service is operating normally.","summary":"[RESOLVED] Intermittent missing or delayed EC2 instance and status check metrics","status":"0","timestamp":1772052712}]},{"summary":"[RESOLVED] Increased Error Rate and Latency","arn":"arn:aws:health:us-east-1::event/EC2/AWS_EC2_OPERATIONAL_ISSUE/AWS_EC2_OPERATIONAL_ISSUE_FFA94_A4DC515D30F","status":"1","date":"1778199926","event_log":[{"message":"We are investigating instance impairments in a single Availability Zone (use1-az4) in the US-EAST-1 Region. Other Availability Zones are not affected by the event and we are working to resolve the issue.","summary":"Increased Error Rate and Latency","status":"1","timestamp":1778199926},{"message":"We continue to investigate instance impairments to a single Availability Zone (use1-az4) in the US-EAST-1 Region. We have experienced an increase in temperatures within a single data center, which in some cases has caused impairments for instances in the Availability Zone. EC2 instances and EBS volumes hosted on impacted hardware are affected by the loss of power during the thermal event. Other AWS services that depend on the affected EC2 instances and EBS volumes in this Availability Zone, may also experience impairments. We will continue to provide updates as recovery continues.","summary":"Increased Error Rate and Latency","status":"1","timestamp":1778201632},{"message":"We continue to work towards mitigating the increased temperatures to its normal levels in the affected Availability Zone (use1-az4) in the US-EAST-1 Region. Other AWS services that depend on the affected EC2 instances and EBS volumes in this Availability Zone, may also experience impairments. We have weighed away traffic for most services at this time. We recommend customers utilize one of the other Availability Zones in the US-EAST-1 Region at this time, as existing instances in other AZ's remain unaffected by this issue. Customers may experience longer than usual provisioning times. We will provide an update by 7:45 PM PDT, or sooner if we have additional information to share.","summary":"Increased Error Rate and Latency","status":"1","timestamp":1778204823},{"message":"We are actively working to restore temperatures to normal levels in the affected Availability Zone (use1-az4) in the US-EAST-1 Region, though progress is slower than originally anticipated. Since our last update we have made incremental progress to restore cooling systems within the affected AZ, which will not be visible to external customers but are required for the restoration of affected services. In the impacted Availability Zone, EC2 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 US-EAST-1 Region, as existing instances in other AZs remain unaffected by this issue. If immediate recovery is required, we recommend customers restore from EBS Snapshots and/or replace affected resources by launching new replacement resources in one of the unaffected zones. We will provide an update by 10:00 PM PDT, or sooner if we have additional information to share.","summary":"Increased Error Rate and Latency","status":"1","timestamp":1778209588},{"message":"We are observing early signs of recovery. We continue to work towards restoring temperatures to normal levels and bring impacted racks back online in the affected Availability Zone (use1-az4) in the US-EAST-1 Region. We have been able to get additional cooling system capacity online, which has allowed us to recover some affected racks and are actively working to recover additional racks in a controlled and safe manner. In the impacted Availability Zone, EC2 Instances, EBS Volumes, and other AWS Services may continue to experience elevated error rates and latencies for some workflows until full recovery is achieved. We will provide an update by 11:30 PM PDT, or sooner if we have additional information to share.","summary":"Increased Error Rate and Latency","status":"1","timestamp":1778217069},{"message":"We continue to make progress in resolving the impaired EC2 instances in the affected Availability Zone (use1-az4) in the US-EAST-1 Region, and are working towards full recovery. We are actively working to bring additional cooling system capacity online, which will enable us to recover the remaining affected racks in a controlled and safe manner.  In the impacted Availability Zone, EC2 Instances, EBS Volumes, and other AWS Services may continue to experience elevated error rates and latencies for some workflows. Customers will continue to see some of their affected EC2 instances and EBS volumes as impaired until we achieve full recovery. We will provide an update by May 8, 1:30 AM PDT, or sooner if we have additional information to share.","summary":"Increased Error Rate and Latency","status":"1","timestamp":1778222324},{"message":"Mitigation efforts remain underway to resolve the impaired EC2 instances and degraded EBS volumes in a single Availability Zone (use1-az4) in the US-EAST-1 Region. These EC2 instances and EBS volumes were impacted due to a loss of power during the thermal event. The work to bring additional cooling system capacity online, which will enable us to recover the remaining affected infrastructure in a controlled and safe manner, is taking longer than we had initially anticipated. Some services, such as IoT Core, ELB, NAT Gateway, and Redshift, have seen significant improvements in the recovery of their workflows. However, some customers will continue to see their affected EC2 instances and EBS volumes as impaired until we achieve full recovery. While we do not currently have an ETA for full recovery, we are prioritizing this issue and will provide another update by 3:30 AM PDT or sooner if additional information becomes available.","summary":"Increased Error Rate and Latency","status":"1","timestamp":1778229161},{"message":"We continue to make progress towards resolving the impaired EC2 instances and degraded EBS volumes in a single Availability Zone (use1-az4) in the US-EAST-1 Region. At this time, we wanted to provide some more details on the issue. Beginning on May 7 at 4:20 PM PDT, we began experiencing an increase in instance impairments within the affected zone due to the loss of power during a thermal event. Engineers were automatically engaged within minutes and immediately began investigating multiple mitigations. By 9:12 PM PDT, we restored power to a subset of the affected infrastructure and observed some signs of recovery, which have remained stable. \n\nWe continue working to bring additional cooling system capacity online, which will enable us to recover the remaining affected hardware in the impacted zone in a controlled and safe manner. Some AWS services, such as IoT Core, ELB, NAT Gateway, and Redshift, continue to see significant improvements in the recovery of their workflows. However, some customers will continue to see their affected EC2 instances and EBS volumes as impaired until we achieve full recovery. If immediate recovery is required, we recommend customers restore from EBS snapshots and/or replace affected resources by launching new replacement resources in one of the unaffected zones. \n\nBased on our current mitigation efforts, we expect full recovery to take several hours. We are prioritizing this issue and will provide another update by 6:30 AM PDT or sooner if additional information becomes available.\n","summary":"Increased Error Rate and Latency","status":"1","timestamp":1778237661},{"message":"We continue working to resolve the impaired EC2 instances and degraded EBS volumes in a single Availability Zone (use1-az4) in the US-EAST-1 Region caused by a thermal event. During such an event, servers automatically shut down when the temperatures exceeded the operating thresholds in order to protect the hardware. We are actively working to bring additional cooling system capacity online, which will enable us to recover the remaining affected hardware in the impacted zone. Some customers will continue to see their affected EC2 instances and EBS volumes as impaired until we achieve full recovery. If immediate recovery is required, we recommend customers restore from EBS snapshots and/or replace affected resources by launching new replacement resources in one of the unaffected zones.\n\nIn parallel, we are investigating increased error rates and query failures for Redshift clusters in the US-EAST-1 Region. During this time, affected customers may see errors for resume and restart workflows, as well as failover operations and availability issues. Our engineers are actively working to resolve this issue.\n\nFull recovery is still expected to take several hours. We are prioritizing this issue and will provide another update by 9:00 AM PDT or sooner if additional information becomes available.\n","summary":"Increased Error Rate and Latency","status":"1","timestamp":1778248311},{"message":"We continue our efforts to work towards the recovery of the impaired EC2 instances and degraded EBS volumes in a single Availability Zone (use1-az4) in the US-EAST-1 Region. We are making progress towards the restoration of the cooling system capacity that is required to recover the affected hardware in the impacted zone. Some customers will continue to see their affected EC2 instances and EBS volumes as impaired until the affected racks are recovered. We continue to recommend that customers who require immediate recovery restore from EBS snapshots and/or replace affected resources by launching new replacement resources in one of the unaffected zones. \n\nAs part of our parallel investigation, we have identified the root cause of the increased error rates and query failures for Redshift clusters in the US-EAST-1 Region. This has been confirmed to be related to impact from an upstream dependency. Affected customers may continue to see errors for resume and restart workflows, failover operations, and impact to general availability. We are actively working to resolve the issue.\n\nOur timeline for full recovery is still expected to take several hours and will be incremental as we bring racks online in phases. We will provide an additional update by 12:30 PM or sooner if we have new information to provide. ","summary":"Increased Error Rate and Latency","status":"1","timestamp":1778255936},{"message":"We have observed complete recovery of increased error rates and query failures for Redshift clusters in the US-EAST-1 Region. We were able to resolve the impact independently of the ongoing efforts to recover the affected hardware in the use1-az4 Availability Zone. The issue affecting Redshift has been resolved and the service is operating normally. We will provide an additional update regarding the efforts towards hardware restoration by 12:30 PM or sooner.","summary":"Increased Error Rate and Latency","status":"1","timestamp":1778257834},{"message":"We are experiencing an increase in timeouts to Amazon Managed Streaming for Apache Kafka partitions on a subset of clusters as a result of the ongoing issue in a single Availability Zone (use1-az4) in the US-EAST-1 Region. We are working in parallel to determine a path towards mitigation for affected clusters. We will provide an additional update by 12:30 PM or sooner.","summary":"Increased Error Rate and Latency","status":"1","timestamp":1778263966},{"message":"We continue to work towards the recovery of the impaired EC2 instances and degraded EBS volumes in a single Availability Zone (use1-az4) in the US-EAST-1 Region though efforts are slower than we had previously anticipated. We are taking measured steps to ensure that cooling capacity is brought online in a safe and controlled manner. As a result, EBS Volumes and EC2 instances affected by the issue will continue to experience impairments. We continue to recommend that customers who require immediate recovery restore from EBS snapshots and/or replace affected resourced by launching new replacement resources. \n\nFull recovery is still expected to take several hours. We will provide an additional update by 4:00 PM or sooner if we have new information to provide. ","summary":"Increased Error Rate and Latency","status":"1","timestamp":1778268552},{"message":"We have begun to see improvements in the overall number of affected EC2 instances and degraded EBS volumes in a single Availability Zone (use1-az4) in the US-EAST-1 Region. The steps taken to supply additional cooling capacity have been showing steady signs of progress. Some EBS Volumes and EC2 instances affected by the issue will continue to experience impairments while we continue to drive these efforts. We continue to recommend that customers who require immediate recovery restore from EBS snapshots and/or replace affected resources by launching new replacement resources.\n\nIn parallel, we have seen some improvements in Amazon Managed Streaming for Apache Kafka as a result of the parallel mitigation efforts being performed. We are still experiencing timeouts to partitions but are seeing continued progress.\n\nWe do anticipate that recovery will still take several hours. We will provide an additional update by 7:30 PM or sooner if we have new information to provide.","summary":"Increased Error Rate and Latency","status":"1","timestamp":1778281252},{"message":"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.\n\nAWS 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.\n\nOur 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. \n\nWe 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.","summary":"[RESOLVED] Increased Error Rate and Latency","status":"0","timestamp":1778295847}],"impacted_services":{"awsiot-us-east-1":{"service_name":"AWS IoT Core","current":"0","max":"1"},"eks-us-east-1":{"service_name":"Amazon Elastic Kubernetes Service","current":"0","max":"1"},"elasticache-us-east-1":{"service_name":"Amazon ElastiCache","current":"0","max":"1"},"elasticsearch-us-east-1":{"service_name":"Amazon OpenSearch Service","current":"0","max":"1"},"elb-us-east-1":{"service_name":"Amazon Elastic Load Balancing","current":"0","max":"1"},"kafka-us-east-1":{"service_name":"Amazon Managed Streaming for Apache Kafka","current":"0","max":"1"},"natgateway-us-east-1":{"service_name":"AWS NAT Gateway","current":"0","max":"1"},"redshift-us-east-1":{"service_name":"Amazon Redshift","current":"0","max":"1"},"sagemaker-us-east-1":{"service_name":"Amazon SageMaker","current":"0","max":"1"}},"impacted_service_status_changes":[{"service":"awsiot-us-east-1","service_name":"AWS IoT Core","previous_status":"0","current_status":"1","timestamp":1778199926000},{"service":"eks-us-east-1","service_name":"Amazon Elastic Kubernetes Service","previous_status":"0","current_status":"1","timestamp":1778199926000},{"service":"elasticache-us-east-1","service_name":"Amazon ElastiCache","previous_status":"0","current_status":"1","timestamp":1778199926000},{"service":"elasticsearch-us-east-1","service_name":"Amazon OpenSearch Service","previous_status":"0","current_status":"1","timestamp":1778199926000},{"service":"elb-us-east-1","service_name":"Amazon Elastic Load Balancing","previous_status":"0","current_status":"1","timestamp":1778199926000},{"service":"kafka-us-east-1","service_name":"Amazon Managed Streaming for Apache Kafka","previous_status":"0","current_status":"1","timestamp":1778199926000},{"service":"natgateway-us-east-1","service_name":"AWS NAT Gateway","previous_status":"0","current_status":"1","timestamp":1778199926000},{"service":"redshift-us-east-1","service_name":"Amazon Redshift","previous_status":"0","current_status":"1","timestamp":1778199926000},{"service":"sagemaker-us-east-1","service_name":"Amazon SageMaker","previous_status":"0","current_status":"1","timestamp":1778199926000},{"service":"awsiot-us-east-1","service_name":"AWS IoT Core","previous_status":"1","current_status":"0","timestamp":1778295847000},{"service":"eks-us-east-1","service_name":"Amazon Elastic Kubernetes Service","previous_status":"1","current_status":"0","timestamp":1778295847000},{"service":"elasticache-us-east-1","service_name":"Amazon ElastiCache","previous_status":"1","current_status":"0","timestamp":1778295847000},{"service":"elasticsearch-us-east-1","service_name":"Amazon OpenSearch Service","previous_status":"1","current_status":"0","timestamp":1778295847000},{"service":"elb-us-east-1","service_name":"Amazon Elastic Load Balancing","previous_status":"1","current_status":"0","timestamp":1778295847000},{"service":"kafka-us-east-1","service_name":"Amazon Managed Streaming for Apache Kafka","previous_status":"1","current_status":"0","timestamp":1778295847000},{"service":"natgateway-us-east-1","service_name":"AWS NAT Gateway","previous_status":"1","current_status":"0","timestamp":1778295847000},{"service":"redshift-us-east-1","service_name":"Amazon Redshift","previous_status":"1","current_status":"0","timestamp":1778295847000},{"service":"sagemaker-us-east-1","service_name":"Amazon SageMaker","previous_status":"1","current_status":"0","timestamp":1778295847000}]},{"summary":"[RESOLVED] Increased Launch Template API Error Rates","arn":"arn:aws:health:us-east-1::event/EC2/AWS_EC2_OPERATIONAL_ISSUE/AWS_EC2_OPERATIONAL_ISSUE_5269E_F1B7AF74706","status":"1","date":"1783341929","event_log":[{"message":"We are investigating increased error rates when calling EC2 Launch Template APIs in US-EAST-1 Region. During this time, affected customers may experience errors when creating, modifying, or referencing launch templates. Other AWS services that rely on launch templates may also be impacted. We will provide another update by 6:30 AM PDT or sooner, if we have additional information to share.","summary":"Increased Launch Template API Error Rates","status":"1","timestamp":1783341929},{"message":"Starting at 2:56 AM PDT, we began experiencing increased error rates when calling EC2 Launch Template APIs in the US-EAST-1 Region. Our engineers have been engaged and are actively working to mitigate the impact. Additionally, Amazon Elastic Kubernetes (EKS) customers may experience errors when creating or updating clusters, or when launching and scaling nodes via Managed Node Groups, EKS Auto Mode, or Karpenter; this issue does not impact existing clusters and nodes. We have identified the root cause to be a congestion issue within an EC2 internal subsystem responsible for processing EC2 launch template workflows. We are pursuing multiple mitigation paths. We recommend that customers retry any failed requests during the impact window. While we do not currently have an ETA for full recovery, we are prioritizing this issue and will provide another update by 7:15 AM PDT or sooner if we have additional information to share.","summary":"Increased Launch Template API Error Rates","status":"1","timestamp":1783344887},{"message":"We are seeing initial signs of recovery and continue to work toward full recovery.","summary":"Increased Launch Template API Error Rates","status":"1","timestamp":1783347144},{"message":"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 describing 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 failed requests. The issue has been resolved and all AWS services are now operating normally.","summary":"[RESOLVED] Increased Launch Template API Error Rates","status":"0","timestamp":1783349591}],"impacted_services":{"eks-us-east-1":{"service_name":"Amazon Elastic Kubernetes Service","current":"0","max":"1"}},"impacted_service_status_changes":[{"service":"eks-us-east-1","service_name":"Amazon Elastic Kubernetes Service","previous_status":"0","current_status":"1","timestamp":1783341929000},{"service":"eks-us-east-1","service_name":"Amazon Elastic Kubernetes Service","previous_status":"1","current_status":"0","timestamp":1783349591000}]}],"ec2-eu-north-1":[{"summary":"[RESOLVED] Increased Error Rates and Latencies","arn":"arn:aws:health:eu-north-1::event/EC2/AWS_EC2_OPERATIONAL_ISSUE/AWS_EC2_OPERATIONAL_ISSUE_77410_461A699110A","status":"1","date":"1782853340","event_log":[{"message":"We are investigating increased launch errors and API errors in the EU-NORTH-1 Region. Existing instances are not affected by this issue.","summary":"EC2 API Errors","status":"1","timestamp":1782853340},{"message":"We can confirm increased error rates for the EC2 APIs, as well as errors launching new EC2 instances in the EU-NORTH-1 Region. Other AWS Services that launch new instances or call the EC2 APIs as part of their workflows may also be affected by this issue. During this time, customers may receive an Internal Server Error in the Management Console and APIs. Engineers were automatically engaged and began investigating the issue. We are actively working on identifying the root cause. Existing instances are unaffected by this issue. We will provide an update by 3:15 PM, or sooner if we have additional information to share. ","summary":"EC2 API Errors","status":"1","timestamp":1782854513},{"message":"We are seeing early signs of recovery and continue to work toward full recovery. ","summary":"Increased Error Rates and Latencies","status":"1","timestamp":1782854975},{"message":"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. ","summary":"[RESOLVED] Increased Error Rates and Latencies","status":"0","timestamp":1782856403}],"impacted_services":{"appsync-eu-north-1":{"service_name":"AWS AppSync","current":"0","max":"1"},"elb-eu-north-1":{"service_name":"Amazon Elastic Load Balancing","current":"0","max":"1"},"emr-eu-north-1":{"service_name":"Amazon Elastic MapReduce","current":"0","max":"1"},"emrserverless-eu-north-1":{"service_name":"Amazon EMR Serverless","current":"0","max":"1"},"glue-eu-north-1":{"service_name":"AWS Glue","current":"0","max":"1"},"natgateway-eu-north-1":{"service_name":"AWS NAT Gateway","current":"0","max":"1"},"pcs-eu-north-1":{"service_name":"AWS Parallel Computing Service","current":"0","max":"1"},"rds-eu-north-1":{"service_name":"Amazon Relational Database Service","current":"0","max":"1"},"sagemaker-eu-north-1":{"service_name":"Amazon SageMaker","current":"0","max":"1"}},"impacted_service_status_changes":[{"service":"appsync-eu-north-1","service_name":"AWS AppSync","previous_status":"0","current_status":"1","timestamp":1782853340000},{"service":"elb-eu-north-1","service_name":"Amazon Elastic Load Balancing","previous_status":"0","current_status":"1","timestamp":1782853340000},{"service":"emr-eu-north-1","service_name":"Amazon Elastic MapReduce","previous_status":"0","current_status":"1","timestamp":1782853340000},{"service":"emrserverless-eu-north-1","service_name":"Amazon EMR Serverless","previous_status":"0","current_status":"1","timestamp":1782853340000},{"service":"glue-eu-north-1","service_name":"AWS Glue","previous_status":"0","current_status":"1","timestamp":1782853340000},{"service":"natgateway-eu-north-1","service_name":"AWS NAT Gateway","previous_status":"0","current_status":"1","timestamp":1782853340000},{"service":"pcs-eu-north-1","service_name":"AWS Parallel Computing Service","previous_status":"0","current_status":"1","timestamp":1782853340000},{"service":"rds-eu-north-1","service_name":"Amazon Relational Database Service","previous_status":"0","current_status":"1","timestamp":1782853340000},{"service":"sagemaker-eu-north-1","service_name":"Amazon SageMaker","previous_status":"0","current_status":"1","timestamp":1782853340000},{"service":"appsync-eu-north-1","service_name":"AWS AppSync","previous_status":"1","current_status":"0","timestamp":1782856403000},{"service":"elb-eu-north-1","service_name":"Amazon Elastic Load Balancing","previous_status":"1","current_status":"0","timestamp":1782856403000},{"service":"emr-eu-north-1","service_name":"Amazon Elastic MapReduce","previous_status":"1","current_status":"0","timestamp":1782856403000},{"service":"emrserverless-eu-north-1","service_name":"Amazon EMR Serverless","previous_status":"1","current_status":"0","timestamp":1782856403000},{"service":"glue-eu-north-1","service_name":"AWS Glue","previous_status":"1","current_status":"0","timestamp":1782856403000},{"service":"natgateway-eu-north-1","service_name":"AWS NAT Gateway","previous_status":"1","current_status":"0","timestamp":1782856403000},{"service":"pcs-eu-north-1","service_name":"AWS Parallel Computing Service","previous_status":"1","current_status":"0","timestamp":1782856403000},{"service":"rds-eu-north-1","service_name":"Amazon Relational Database Service","previous_status":"1","current_status":"0","timestamp":1782856403000},{"service":"sagemaker-eu-north-1","service_name":"Amazon SageMaker","previous_status":"1","current_status":"0","timestamp":1782856403000}]}],"multipleservices-me-central-1":[{"summary":"Increased Error Rates","arn":"arn:aws:health:me-central-1::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_5E6B8_EF2498889B5","status":"3","date":"1772369485","event_log":[{"message":"We are investigating issues with AWS services in the ME-CENTRAL-1 Region.","summary":"Increased Error Rates","status":"1","timestamp":1772369485},{"message":"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.","summary":"Increased Error Rates","status":"1","timestamp":1772371152},{"message":"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, at which time we will begin to work to recover affected resources. As of this time, we expect recovery is multiple hours away. We will provide an update by 7:15 AM PST, or sooner if we have additional information to share.","summary":"Increased Error Rates","status":"1","timestamp":1772374140},{"message":"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 by launching replacement resources in one of the unaffected zones, or an alternate region. As of this time, recovery is still several hours away. We will provide an update by 8:30 AM PST, or sooner if we have additional information to share.","summary":"Increased Error Rates","status":"2","timestamp":1772377753},{"message":"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. ","summary":"Increased Error Rates","status":"2","timestamp":1772384340},{"message":"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 other AZs in the region are functioning normally. Customers who were running their applications redundantly across the AZs are not impacted by this event. EC2 Instance launches will continue to be impaired in the impacted AZ. We recommend that customers continue to retry any failed API requests. If immediate recovery of an affected resource (EC2 Instance, EBS Volume, RDS DB Instance, etc.) is required, we recommend restoring from your most recent backup, by launching replacement resources in one of the unaffected zones, or an alternate AWS Region. We will provide an update by 12:30 PM PST, or sooner if we have additional information to share.","summary":"Increased Error Rates","status":"3","timestamp":1772386871},{"message":"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 API requests. For customers that can, we recommend considering using alternate AWS Regions. We will provide another update by 3:30 PM PST, or sooner if we have more to share.","summary":"Increased Error Rates","status":"3","timestamp":1772396043},{"message":"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 higher success rates for these operations. Additionally, we are investigating ways to speed up these specific mitigation efforts, but are ensuring we do so safely. As of this time, power restoration is still several hours away. We will provide another update by 5:30 PM PST, or sooner if we have additional information to share.","summary":"Increased Error Rates","status":"3","timestamp":1772404099},{"message":"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. We 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 another update by 6:30 PM, or sooner if we have additional information to share.","summary":"Increased Error Rates","status":"3","timestamp":1772411201},{"message":"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 another update by 10:00 PM, or sooner if we have additional information to share.","summary":"Increased Error Rates","status":"3","timestamp":1772416907},{"message":"We are investigating additional connectivity issues and error rates in the ME-CENTRAL-1 Region.","summary":"Increased Error Rates","status":"3","timestamp":1772431169},{"message":"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 recovery is multiple hours away. For customers that can, we recommend failing away to another AWS Region at this time. We will provide an update by 12:00 AM PST, or sooner if we have additional information to share.","summary":"Increased Error Rates","status":"3","timestamp":1772433960},{"message":"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, and backup any critical data, to another AWS Region. We will provide an update by 2:00 AM PST, or sooner if the situation changes.","summary":"Increased Error Rates","status":"3","timestamp":1772441520},{"message":"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 to update their applications to ingest S3 data to an alternate AWS Region. As soon as practically possible, we will begin the restoration of our two Availability Zones which will include a careful assessment of data health and any repair of storage if necessary.\n\nIn addition, we can confirm that the AWS Management Console and command line interface (CLI) are disrupted by the failure of two Availability Zones. We continue to work towards recovery across all services, and we will provide an update by 6:00 AM PST on March 2, or sooner if we have additional information to share.","summary":"Increased Error Rates","status":"3","timestamp":1772448800},{"message":"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.\nWe 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 S3 data to an alternate AWS Region. We will provide an update by 11:00 AM PST on March 2, or sooner if we have additional information to share.","summary":"Increased Error Rates","status":"3","timestamp":1772461323},{"message":"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.","summary":"Increased Error Rates","status":"3","timestamp":1772474389},{"message":"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 customers enact their disaster recovery plans and recover from remote backups into alternate AWS Regions. We will provide you with another update by 6:00 PM PST, or sooner if new information becomes available.","summary":"Increased Error Rates","status":"3","timestamp":1772487370},{"message":"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 that resulted in additional water damage. We are working closely with local authorities and prioritizing the safety of our personnel throughout our recovery efforts.\n\nIn the ME-CENTRAL-1 (UAE) Region, two of our three Availability Zones (mec1-az2 and mec1-az3) remain significantly impaired. The third Availability Zone (mec1-az1) continues to operate normally, though some services have experienced indirect impact due to dependencies on the affected zones. In the ME-SOUTH-1 (Bahrain) Region, one facility has been impacted. Across both regions, customers are experiencing elevated error rates and degraded availability for services including Amazon EC2, Amazon S3, Amazon DynamoDB, AWS Lambda, Amazon Kinesis, Amazon CloudWatch, Amazon RDS, and the AWS Management Console and CLI. We are working to restore full service availability as quickly as possible, though we expect recovery to be prolonged given the nature of the physical damage involved.\n\nIn parallel with efforts to restore the physical infrastructure at the affected sites, we are pursuing multiple software-based recovery paths that do not depend on the underlying facilities being fully brought back online. For Amazon S3 and Amazon DynamoDB, we are actively working to restore data access and service availability through software mitigations, including deploying updates to enable S3 to operate within the current infrastructure constraints and remediating impaired DynamoDB tables to restore read and write availability for dependent services. Our focus on restoring these foundational services is deliberate, as recovery of Amazon S3 and Amazon DynamoDB will in turn enable a broad range of dependent AWS services to recover. For other affected service APIs, we are deploying targeted software updates to reduce error rates and restore functionality where possible, independent of the physical recovery timeline. We are also working to restore access to the AWS Management Console and CLI through network-level changes that route traffic away from the affected infrastructure. While these software-based mitigations can address many of the service-level impacts, some recovery actions are constrained by the physical state of the affected facilities — meaning that full restoration of certain services will require the underlying infrastructure to be repaired and brought back online. Across all services, our teams are working in parallel on both the physical restoration of the affected facilities and these software-based mitigations, with the goal of restoring as much customer access as possible as quickly as possible, even ahead of full infrastructure recovery. In addition, we are prioritizing the restoration of services and tools that enable customers to back up and migrate their data and applications out of the affected regions.\n\nFinally, even as we work to restore these facilities, the ongoing conflict in the region means that the broader operating environment in the Middle East remains unpredictable. We recommend that customers with workloads running in the Middle East consider taking action now to backup data and potentially migrate your workloads to alternate AWS Regions. We recommend customers exercise their disaster recovery plans, recover from remote backups stored in other regions, and update their applications to direct traffic away from the affected regions. For customers requiring guidance on alternate regions, we recommend considering AWS Regions in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements.\n\nWe will continue to provide updates as recovery progresses and as the situation evolves. Our next update will be provided by 9:00 PM PST on March 2, 2026, or sooner if new information becomes available.","summary":"Increased Error Rates","status":"3","timestamp":1772497188},{"message":"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 before we are able to fully restore power and connectivity. We will provide you with another update by March 3 2:00 AM PST, or sooner if new information becomes available.","summary":"Increased Error Rates","status":"3","timestamp":1772514818},{"message":"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.\n\nWith 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 on restoring the affected infrastructure, which our teams continue to work toward.\n\nFor Amazon DynamoDB, error rates remain elevated and our teams continue to focus on recovery efforts. We have not yet seen meaningful improvement in DynamoDB availability, but expect conditions to improve over the coming hours as recovery work progresses.\n\nAmazon EC2 instance launches remain throttled in the ME-CENTRAL-1 Region. We will begin relaxing these throttles as soon as we have fully recovered our foundational services and have sufficient capacity to support new launches safely.\n\nThe AWS Management Console is now operational, though customers may continue to experience errors on certain pages and operations as the underlying services work through their recovery. We recommend customers continue to retry requests where possible.\n\nAWS Lambda, Amazon Kinesis, Amazon CloudWatch, Amazon RDS, and a number of other AWS services that were impacted by this event remain degraded. The availability of these services is dependent on the recovery of our foundational services — primarily Amazon S3 and Amazon DynamoDB — and we expect to see improvement across these services as that recovery progresses.\n\nFinally, even as we work to restore these facilities, the ongoing conflict in the region means that the broader operating environment in the Middle East remains unpredictable. We strongly recommend that customers with workloads running in the Middle East take action now to migrate those workloads to alternate AWS Regions. Customers should enact their disaster recovery plans, recover from remote backups stored in other regions, and update their applications to direct traffic away from the affected regions. For customers requiring guidance on alternate regions, we recommend considering AWS Regions in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements.\n\nWe will continue to provide updates as recovery progresses and as the situation evolves. Our next update will be provided by 5:00 AM PST on March 3, or sooner if new information becomes available.","summary":"Increased Error Rates","status":"3","timestamp":1772528640},{"message":"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. \n\nFor 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 expect to see improvement over the coming hours. As these foundational services recover, dependent services — including AWS Lambda, Amazon Kinesis, Amazon CloudWatch, and Amazon RDS will follow. Amazon EC2 instance launches remain throttled in the ME-CENTRAL-1 Region and will be relaxed as foundational service recovery and capacity allow. \n\nThe AWS Management Console is operational, though customers may continue to experience errors on certain pages as underlying services work through their recovery. We recommend that customers continue to retry requests where possible. \n\nWe strongly recommend that customers with workloads running in the Middle East take action now to migrate those workloads to alternate AWS Regions. Customers should enact their disaster recovery plans, recover from remote backups stored in other Regions, and update their applications to direct traffic away from the affected Regions. For customers requiring guidance on alternate regions, we recommend considering AWS Regions in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. \n\nWe will provide another update by March 3 at 10:00 AM PST, or sooner if new information becomes available. ","summary":"Increased Error Rates","status":"3","timestamp":1772542694},{"message":"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.\n\nFor 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 expect to see improvement over the coming hours. As these foundational services recover, dependent services — including AWS Lambda, Amazon Kinesis, Amazon CloudWatch, and Amazon RDS — will follow. Amazon EC2 instance launches remain throttled in the ME-CENTRAL-1 Region and will be relaxed as foundational service recovery and capacity allow. The AWS Management Console is operational, though customers may continue to experience errors on certain pages as underlying services work through their recovery.\n\nWith 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.\n\nWe continue to strongly recommend that customers with workloads running in the Middle East take action now to migrate those workloads to alternate AWS Regions. Customers should enact their disaster recovery plans, recover from remote backups stored in other Regions, and update their applications to direct traffic away from the affected Regions. For customers requiring guidance on alternate regions, we recommend considering AWS Regions in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements.","summary":"Increased Error Rates","status":"3","timestamp":1772554485},{"message":"We are providing an update on the ongoing service disruption. The Middle East (UAE) Region (ME-CENTRAL-1) has suffered damage as a result of the conflict in the Middle East and is currently unable to reliably support customer applications. While some workloads continue to function normally, we strongly recommend customers migrate all accessible resources to other Regions and restore inaccessible resources from remote backups as soon as possible. Relevant billing operations are currently suspended while we restore normal operations in this AWS Region. This process is expected to take several months. ","summary":"Increased Error Rates","status":"3","timestamp":1777533954}],"impacted_services":{"acm-pca-me-central-1":{"service_name":"AWS Private Certificate Authority","current":"3","max":"3"},"airflow-me-central-1":{"service_name":"Amazon Managed Workflows for Apache Airflow","current":"3","max":"3"},"amplify":{"service_name":"AWS Amplify","current":"3","max":"3"},"apigateway-me-central-1":{"service_name":"Amazon API Gateway","current":"3","max":"3"},"appconfig-me-central-1":{"service_name":"AWS AppConfig","current":"3","max":"3"},"applicationinsights-me-central-1":{"service_name":"Amazon CloudWatch Application Insights","current":"3","max":"3"},"appsync-me-central-1":{"service_name":"AWS AppSync","current":"3","max":"3"},"appwizard-me-central-1":{"service_name":"AWS Launch Wizard","current":"3","max":"3"},"aps":{"service_name":"Amazon Managed Service for Prometheus","current":"3","max":"3"},"athena-me-central-1":{"service_name":"Amazon Athena","current":"3","max":"3"},"autoscaling-me-central-1":{"service_name":"Auto Scaling","current":"3","max":"3"},"awsiot-me-central-1":{"service_name":"AWS IoT Core","current":"3","max":"3"},"awsiotdevicemanagement-me-central-1":{"service_name":"AWS IoT Device Management","current":"3","max":"3"},"awswaf-me-central-1":{"service_name":"AWS WAF","current":"3","max":"3"},"backup-me-central-1":{"service_name":"AWS Backup","current":"3","max":"3"},"batch-me-central-1":{"service_name":"AWS Batch","current":"3","max":"3"},"bedrock-me-central-1":{"service_name":"Amazon Bedrock","current":"3","max":"3"},"certificatemanager-me-central-1":{"service_name":"AWS Certificate Manager","current":"3","max":"3"},"clientvpn-me-central-1":{"service_name":"AWS Client VPN","current":"3","max":"3"},"cloudformation-me-central-1":{"service_name":"AWS CloudFormation","current":"3","max":"3"},"cloudfront":{"service_name":"Amazon CloudFront","current":"0","max":"1"},"cloudhsm-me-central-1":{"service_name":"AWS CloudHSM","current":"3","max":"3"},"cloudshell-me-central-1":{"service_name":"AWS CloudShell","current":"3","max":"3"},"cloudtrail-me-central-1":{"service_name":"AWS CloudTrail","current":"3","max":"3"},"cloudwan":{"service_name":"AWS Cloud WAN","current":"0","max":"1"},"cloudwatch-me-central-1":{"service_name":"Amazon CloudWatch","current":"3","max":"3"},"cloudwatchsynthetics-me-central-1":{"service_name":"Amazon CloudWatch Synthetics","current":"3","max":"3"},"codebuild-me-central-1":{"service_name":"AWS CodeBuild","current":"3","max":"3"},"codecommit-me-central-1":{"service_name":"AWS CodeCommit","current":"3","max":"3"},"codedeploy-me-central-1":{"service_name":"AWS CodeDeploy","current":"3","max":"3"},"codepipeline-me-central-1":{"service_name":"AWS CodePipeline","current":"3","max":"3"},"cognito-me-central-1":{"service_name":"Amazon Cognito","current":"3","max":"3"},"computeoptimizer-me-central-1":{"service_name":"AWS Compute Optimizer","current":"3","max":"3"},"config-me-central-1":{"service_name":"AWS Config","current":"3","max":"3"},"consolemobileapp-me-central-1":{"service_name":"AWS Console Mobile App","current":"3","max":"3"},"controlcatalog-me-central-1":{"service_name":"Control Catalog","current":"3","max":"3"},"controltower-me-central-1":{"service_name":"AWS Control Tower","current":"3","max":"3"},"datasync-me-central-1":{"service_name":"AWS DataSync","current":"3","max":"3"},"directconnect-me-central-1":{"service_name":"AWS Direct Connect","current":"3","max":"3"},"directoryservice-me-central-1":{"service_name":"AWS Directory Service","current":"3","max":"3"},"dlm-me-central-1":{"service_name":"Amazon Data Lifecycle Manager","current":"3","max":"3"},"dms-me-central-1":{"service_name":"AWS Database Migration Service","current":"3","max":"3"},"docdb-me-central-1":{"service_name":"Amazon DocumentDB","current":"3","max":"3"},"drs-me-central-1":{"service_name":"AWS Elastic Disaster Recovery","current":"3","max":"3"},"dynamodb-me-central-1":{"service_name":"Amazon DynamoDB","current":"3","max":"3"},"ec2-me-central-1":{"service_name":"Amazon Elastic Compute Cloud","current":"3","max":"3"},"ec2serialconsole-me-central-1":{"service_name":"EC2 Serial Console","current":"3","max":"3"},"ec2systemsmanager-me-central-1":{"service_name":"AWS Systems Manager","current":"3","max":"3"},"ecr-me-central-1":{"service_name":"Amazon Elastic Container Registry","current":"3","max":"3"},"ecs-me-central-1":{"service_name":"Amazon Elastic Container Service","current":"3","max":"3"},"eks-me-central-1":{"service_name":"Amazon Elastic Kubernetes Service","current":"3","max":"3"},"elasticache-me-central-1":{"service_name":"Amazon ElastiCache","current":"3","max":"3"},"elasticbeanstalk-me-central-1":{"service_name":"AWS Elastic Beanstalk","current":"3","max":"3"},"elasticfilesystem-me-central-1":{"service_name":"Amazon Elastic File System","current":"3","max":"3"},"elasticsearch-me-central-1":{"service_name":"Amazon OpenSearch Service","current":"3","max":"3"},"elb-me-central-1":{"service_name":"Amazon Elastic Load Balancing","current":"3","max":"3"},"elemental-me-central-1":{"service_name":"AWS Elemental","current":"3","max":"3"},"emr-me-central-1":{"service_name":"Amazon Elastic MapReduce","current":"3","max":"3"},"emrserverless-me-central-1":{"service_name":"Amazon EMR Serverless","current":"3","max":"3"},"endusermessaging-me-central-1":{"service_name":"AWS End User Messaging","current":"3","max":"3"},"events-me-central-1":{"service_name":"Amazon EventBridge","current":"3","max":"3"},"fargate-me-central-1":{"service_name":"AWS Fargate","current":"3","max":"3"},"firehose-me-central-1":{"service_name":"Amazon Data Firehose","current":"3","max":"3"},"fis-me-central-1":{"service_name":"AWS Fault Injection Service","current":"3","max":"3"},"fms-me-central-1":{"service_name":"AWS Firewall Manager","current":"3","max":"3"},"fsx-me-central-1":{"service_name":"Amazon FSx","current":"3","max":"3"},"glacier-me-central-1":{"service_name":"Amazon Glacier","current":"3","max":"3"},"globalaccelerator":{"service_name":"AWS Global Accelerator","current":"0","max":"1"},"glue-me-central-1":{"service_name":"AWS Glue","current":"3","max":"3"},"grafana":{"service_name":"Amazon Managed Grafana","current":"3","max":"3"},"guardduty-me-central-1":{"service_name":"Amazon GuardDuty","current":"3","max":"3"},"iamidentitycenter-me-central-1":{"service_name":"AWS IAM Identity Center","current":"3","max":"3"},"iamrolesanywhere-me-central-1":{"service_name":"AWS Identity and Access Management Roles Anywhere","current":"3","max":"3"},"imagebuilder-me-central-1":{"service_name":"EC2 Image Builder","current":"3","max":"3"},"infrastructureperformance-me-central-1":{"service_name":"Infrastructure Performance","current":"3","max":"3"},"inspector-me-central-1":{"service_name":"Amazon Inspector","current":"3","max":"3"},"internetconnectivity-me-central-1":{"service_name":"AWS Internet Connectivity","current":"3","max":"3"},"internetmonitor-me-central-1":{"service_name":"Amazon CloudWatch Internet Monitor","current":"3","max":"3"},"iotdevicedefender-me-central-1":{"service_name":"AWS IoT Device Defender","current":"3","max":"3"},"ipam-me-central-1":{"service_name":"Amazon VPC IP Address Manager","current":"3","max":"3"},"kafka-me-central-1":{"service_name":"Amazon Managed Streaming for Apache Kafka","current":"3","max":"3"},"kinesis-me-central-1":{"service_name":"Amazon Kinesis Data Streams","current":"3","max":"3"},"kinesisanalytics-me-central-1":{"service_name":"Amazon Managed Service for Apache Flink","current":"3","max":"3"},"kms-me-central-1":{"service_name":"AWS Key Management Service","current":"3","max":"3"},"lakeformation-me-central-1":{"service_name":"AWS Lake Formation","current":"3","max":"3"},"lambda-me-central-1":{"service_name":"AWS Lambda","current":"3","max":"3"},"licensemanager-me-central-1":{"service_name":"AWS License Manager","current":"3","max":"3"},"managedssh-me-central-1":{"service_name":"Amazon EC2 Instance Connect","current":"3","max":"3"},"management-console":{"service_name":"AWS Management Console","current":"0","max":"3"},"mgn-me-central-1":{"service_name":"AWS Application Migration Service","current":"3","max":"3"},"mq-me-central-1":{"service_name":"Amazon MQ","current":"3","max":"3"},"natgateway-me-central-1":{"service_name":"AWS NAT Gateway","current":"3","max":"3"},"neptune-db-me-central-1":{"service_name":"Amazon Neptune","current":"3","max":"3"},"networkfirewall-me-central-1":{"service_name":"AWS Network Firewall","current":"3","max":"3"},"outposts-me-central-1":{"service_name":"AWS Outposts","current":"3","max":"3"},"pca-connector-scep-me-central-1":{"service_name":"AWS Private CA Connector for SCEP","current":"3","max":"3"},"pcaconnectorad-me-central-1":{"service_name":"AWS Private CA Connector for Active Directory","current":"3","max":"3"},"privatelink-me-central-1":{"service_name":"AWS VPCE PrivateLink","current":"3","max":"3"},"quicksight-me-central-1":{"service_name":"Amazon Quick Suite","current":"3","max":"3"},"ram-me-central-1":{"service_name":"AWS Resource Access Manager","current":"3","max":"3"},"rds-me-central-1":{"service_name":"Amazon Relational Database Service","current":"3","max":"3"},"reachabilityanalyzer":{"service_name":"Reachability Analyzer","current":"3","max":"3"},"redshift-me-central-1":{"service_name":"Amazon Redshift","current":"3","max":"3"},"resourceexplorer-me-central-1":{"service_name":"AWS Resource Explorer","current":"3","max":"3"},"resourcegroups-me-central-1":{"service_name":"AWS Resource Groups","current":"3","max":"3"},"resourcegroupstaggingapi-me-central-1":{"service_name":"AWS Resource Groups Tagging API","current":"3","max":"3"},"route53":{"service_name":"Amazon Route 53","current":"0","max":"2"},"route53privatedns-me-central-1":{"service_name":"Amazon Route 53 Private DNS","current":"3","max":"3"},"route53resolver-me-central-1":{"service_name":"Amazon Route 53 Resolver","current":"3","max":"3"},"rum-me-central-1":{"service_name":"Amazon CloudWatch RUM","current":"3","max":"3"},"s3-me-central-1":{"service_name":"Amazon Simple Storage Service","current":"3","max":"3"},"s3rtc-me-central-1":{"service_name":"Amazon S3 Replication Time Control","current":"3","max":"3"},"sagemaker-me-central-1":{"service_name":"Amazon SageMaker","current":"3","max":"3"},"scheduler-me-central-1":{"service_name":"Amazon EventBridge Scheduler","current":"3","max":"3"},"secretsmanager-me-central-1":{"service_name":"AWS Secrets Manager","current":"3","max":"3"},"security-ir-me-central-1":{"service_name":"AWS Security Incident Response","current":"3","max":"3"},"securityhub-me-central-1":{"service_name":"AWS Security Hub","current":"3","max":"3"},"servicecatalog-me-central-1":{"service_name":"AWS Service Catalog","current":"3","max":"3"},"servicediscovery-me-central-1":{"service_name":"AWS Cloud Map","current":"3","max":"3"},"servicequotas-me-central-1":{"service_name":"AWS Service Quotas","current":"3","max":"3"},"ses-me-central-1":{"service_name":"Amazon Simple Email Service","current":"3","max":"3"},"signin-me-central-1":{"service_name":"AWS Sign-In","current":"3","max":"3"},"sns-me-central-1":{"service_name":"Amazon Simple Notification Service","current":"3","max":"3"},"sqs-me-central-1":{"service_name":"Amazon Simple Queue Service","current":"3","max":"3"},"ssmsap-me-central-1":{"service_name":"AWS Systems Manager for SAP","current":"3","max":"3"},"state-me-central-1":{"service_name":"AWS Step Functions","current":"3","max":"3"},"storagegateway-me-central-1":{"service_name":"AWS Storage Gateway","current":"3","max":"3"},"sts-me-central-1":{"service_name":"AWS Security Token Service","current":"3","max":"3"},"swf-me-central-1":{"service_name":"Amazon Simple Workflow Service","current":"3","max":"3"},"trafficmirroring-me-central-1":{"service_name":"Traffic Mirroring","current":"3","max":"3"},"transfer-me-central-1":{"service_name":"AWS Transfer Family","current":"3","max":"3"},"transitgateway-me-central-1":{"service_name":"AWS Transit Gateway","current":"3","max":"3"},"verifiedaccess":{"service_name":"AWS Verified Access","current":"3","max":"3"},"verifiedpermissions-me-central-1":{"service_name":"Amazon Verified Permissions","current":"3","max":"3"},"vmimportexport-me-central-1":{"service_name":"VM Import/Export","current":"3","max":"3"},"vpc-me-central-1":{"service_name":"Amazon Virtual Private Cloud","current":"3","max":"3"},"vpclattice-me-central-1":{"service_name":"Amazon VPC Lattice","current":"3","max":"3"},"vpnvpc-me-central-1":{"service_name":"AWS Site-to-Site VPN","current":"3","max":"3"},"workspaces":{"service_name":"Amazon WorkSpaces","current":"3","max":"3"},"xray-me-central-1":{"service_name":"AWS X-Ray","current":"3","max":"3"}},"impacted_service_status_changes":[{"service":"acm-pca-me-central-1","service_name":"AWS Private Certificate Authority","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"airflow-me-central-1","service_name":"Amazon Managed Workflows for Apache Airflow","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"amplify","service_name":"AWS Amplify","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"apigateway-me-central-1","service_name":"Amazon API Gateway","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"appconfig-me-central-1","service_name":"AWS AppConfig","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"applicationinsights-me-central-1","service_name":"Amazon CloudWatch Application Insights","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"appsync-me-central-1","service_name":"AWS AppSync","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"appwizard-me-central-1","service_name":"AWS Launch Wizard","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"aps","service_name":"Amazon Managed Service for Prometheus","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"athena-me-central-1","service_name":"Amazon Athena","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"autoscaling-me-central-1","service_name":"Auto Scaling","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"awsiot-me-central-1","service_name":"AWS IoT Core","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"awsiotdevicemanagement-me-central-1","service_name":"AWS IoT Device Management","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"awswaf-me-central-1","service_name":"AWS WAF","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"backup-me-central-1","service_name":"AWS Backup","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"batch-me-central-1","service_name":"AWS Batch","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"bedrock-me-central-1","service_name":"Amazon Bedrock","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"certificatemanager-me-central-1","service_name":"AWS Certificate Manager","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"clientvpn-me-central-1","service_name":"AWS Client VPN","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"cloudformation-me-central-1","service_name":"AWS CloudFormation","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"cloudfront","service_name":"Amazon CloudFront","previous_status":"0","current_status":"1","timestamp":1772369485000},{"service":"cloudhsm-me-central-1","service_name":"AWS CloudHSM","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"cloudshell-me-central-1","service_name":"AWS CloudShell","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"cloudtrail-me-central-1","service_name":"AWS CloudTrail","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"cloudwan","service_name":"AWS Cloud WAN","previous_status":"0","current_status":"1","timestamp":1772369485000},{"service":"cloudwatch-me-central-1","service_name":"Amazon CloudWatch","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"cloudwatchsynthetics-me-central-1","service_name":"Amazon CloudWatch Synthetics","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"codebuild-me-central-1","service_name":"AWS CodeBuild","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"codecommit-me-central-1","service_name":"AWS CodeCommit","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"codedeploy-me-central-1","service_name":"AWS CodeDeploy","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"codepipeline-me-central-1","service_name":"AWS CodePipeline","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"cognito-me-central-1","service_name":"Amazon Cognito","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"computeoptimizer-me-central-1","service_name":"AWS Compute Optimizer","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"config-me-central-1","service_name":"AWS Config","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"consolemobileapp-me-central-1","service_name":"AWS Console Mobile App","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"controlcatalog-me-central-1","service_name":"Control Catalog","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"controltower-me-central-1","service_name":"AWS Control Tower","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"datasync-me-central-1","service_name":"AWS DataSync","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"directconnect-me-central-1","service_name":"AWS Direct Connect","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"directoryservice-me-central-1","service_name":"AWS Directory Service","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"dlm-me-central-1","service_name":"Amazon Data Lifecycle Manager","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"dms-me-central-1","service_name":"AWS Database Migration Service","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"docdb-me-central-1","service_name":"Amazon DocumentDB","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"drs-me-central-1","service_name":"AWS Elastic Disaster Recovery","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"dynamodb-me-central-1","service_name":"Amazon DynamoDB","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"ec2-me-central-1","service_name":"Amazon Elastic Compute Cloud","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"ec2serialconsole-me-central-1","service_name":"EC2 Serial Console","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"ec2systemsmanager-me-central-1","service_name":"AWS Systems Manager","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"ecr-me-central-1","service_name":"Amazon Elastic Container Registry","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"ecs-me-central-1","service_name":"Amazon Elastic Container Service","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"eks-me-central-1","service_name":"Amazon Elastic Kubernetes Service","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"elasticache-me-central-1","service_name":"Amazon ElastiCache","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"elasticbeanstalk-me-central-1","service_name":"AWS Elastic Beanstalk","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"elasticfilesystem-me-central-1","service_name":"Amazon Elastic File System","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"elasticsearch-me-central-1","service_name":"Amazon OpenSearch Service","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"elb-me-central-1","service_name":"Amazon Elastic Load Balancing","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"elemental-me-central-1","service_name":"AWS Elemental","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"emr-me-central-1","service_name":"Amazon Elastic MapReduce","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"emrserverless-me-central-1","service_name":"Amazon EMR Serverless","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"endusermessaging-me-central-1","service_name":"AWS End User Messaging","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"events-me-central-1","service_name":"Amazon EventBridge","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"fargate-me-central-1","service_name":"AWS Fargate","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"firehose-me-central-1","service_name":"Amazon Data Firehose","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"fis-me-central-1","service_name":"AWS Fault Injection Service","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"fms-me-central-1","service_name":"AWS Firewall Manager","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"fsx-me-central-1","service_name":"Amazon FSx","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"glacier-me-central-1","service_name":"Amazon Glacier","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"globalaccelerator","service_name":"AWS Global Accelerator","previous_status":"0","current_status":"1","timestamp":1772369485000},{"service":"glue-me-central-1","service_name":"AWS Glue","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"grafana","service_name":"Amazon Managed Grafana","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"guardduty-me-central-1","service_name":"Amazon GuardDuty","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"iamidentitycenter-me-central-1","service_name":"AWS IAM Identity Center","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"iamrolesanywhere-me-central-1","service_name":"AWS Identity and Access Management Roles Anywhere","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"imagebuilder-me-central-1","service_name":"EC2 Image Builder","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"infrastructureperformance-me-central-1","service_name":"Infrastructure Performance","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"inspector-me-central-1","service_name":"Amazon Inspector","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"internetconnectivity-me-central-1","service_name":"AWS Internet Connectivity","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"internetmonitor-me-central-1","service_name":"Amazon CloudWatch Internet Monitor","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"iotdevicedefender-me-central-1","service_name":"AWS IoT Device Defender","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"ipam-me-central-1","service_name":"Amazon VPC IP Address Manager","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"kafka-me-central-1","service_name":"Amazon Managed Streaming for Apache Kafka","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"kinesis-me-central-1","service_name":"Amazon Kinesis Data Streams","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"kinesisanalytics-me-central-1","service_name":"Amazon Managed Service for Apache Flink","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"kms-me-central-1","service_name":"AWS Key Management Service","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"lakeformation-me-central-1","service_name":"AWS Lake Formation","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"lambda-me-central-1","service_name":"AWS Lambda","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"licensemanager-me-central-1","service_name":"AWS License Manager","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"managedssh-me-central-1","service_name":"Amazon EC2 Instance Connect","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"management-console","service_name":"AWS Management Console","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"mgn-me-central-1","service_name":"AWS Application Migration Service","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"mq-me-central-1","service_name":"Amazon MQ","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"natgateway-me-central-1","service_name":"AWS NAT Gateway","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"neptune-db-me-central-1","service_name":"Amazon Neptune","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"networkfirewall-me-central-1","service_name":"AWS Network Firewall","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"outposts-me-central-1","service_name":"AWS Outposts","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"pca-connector-scep-me-central-1","service_name":"AWS Private CA Connector for SCEP","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"pcaconnectorad-me-central-1","service_name":"AWS Private CA Connector for Active Directory","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"privatelink-me-central-1","service_name":"AWS VPCE PrivateLink","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"quicksight-me-central-1","service_name":"Amazon Quick Suite","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"ram-me-central-1","service_name":"AWS Resource Access Manager","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"rds-me-central-1","service_name":"Amazon Relational Database Service","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"reachabilityanalyzer","service_name":"Reachability Analyzer","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"redshift-me-central-1","service_name":"Amazon Redshift","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"resourceexplorer-me-central-1","service_name":"AWS Resource Explorer","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"resourcegroups-me-central-1","service_name":"AWS Resource Groups","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"resourcegroupstaggingapi-me-central-1","service_name":"AWS Resource Groups Tagging API","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"route53","service_name":"Amazon Route 53","previous_status":"0","current_status":"2","timestamp":1772369485000},{"service":"route53privatedns-me-central-1","service_name":"Amazon Route 53 Private DNS","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"route53resolver-me-central-1","service_name":"Amazon Route 53 Resolver","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"rum-me-central-1","service_name":"Amazon CloudWatch RUM","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"s3-me-central-1","service_name":"Amazon Simple Storage Service","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"s3rtc-me-central-1","service_name":"Amazon S3 Replication Time Control","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"sagemaker-me-central-1","service_name":"Amazon SageMaker","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"scheduler-me-central-1","service_name":"Amazon EventBridge Scheduler","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"secretsmanager-me-central-1","service_name":"AWS Secrets Manager","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"security-ir-me-central-1","service_name":"AWS Security Incident Response","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"securityhub-me-central-1","service_name":"AWS Security Hub","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"servicecatalog-me-central-1","service_name":"AWS Service Catalog","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"servicediscovery-me-central-1","service_name":"AWS Cloud Map","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"servicequotas-me-central-1","service_name":"AWS Service Quotas","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"ses-me-central-1","service_name":"Amazon Simple Email Service","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"signin-me-central-1","service_name":"AWS Sign-In","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"sns-me-central-1","service_name":"Amazon Simple Notification Service","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"sqs-me-central-1","service_name":"Amazon Simple Queue Service","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"ssmsap-me-central-1","service_name":"AWS Systems Manager for SAP","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"state-me-central-1","service_name":"AWS Step Functions","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"storagegateway-me-central-1","service_name":"AWS Storage Gateway","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"sts-me-central-1","service_name":"AWS Security Token Service","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"swf-me-central-1","service_name":"Amazon Simple Workflow Service","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"trafficmirroring-me-central-1","service_name":"Traffic Mirroring","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"transfer-me-central-1","service_name":"AWS Transfer Family","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"transitgateway-me-central-1","service_name":"AWS Transit Gateway","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"verifiedaccess","service_name":"AWS Verified Access","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"verifiedpermissions-me-central-1","service_name":"Amazon Verified Permissions","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"vmimportexport-me-central-1","service_name":"VM Import/Export","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"vpc-me-central-1","service_name":"Amazon Virtual Private Cloud","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"vpclattice-me-central-1","service_name":"Amazon VPC Lattice","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"vpnvpc-me-central-1","service_name":"AWS Site-to-Site VPN","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"workspaces","service_name":"Amazon WorkSpaces","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"xray-me-central-1","service_name":"AWS X-Ray","previous_status":"0","current_status":"3","timestamp":1772369485000},{"service":"cloudfront","service_name":"Amazon CloudFront","previous_status":"1","current_status":"0","timestamp":1778054773000},{"service":"cloudwan","service_name":"AWS Cloud WAN","previous_status":"1","current_status":"0","timestamp":1778054773000},{"service":"globalaccelerator","service_name":"AWS Global Accelerator","previous_status":"1","current_status":"0","timestamp":1778054773000},{"service":"management-console","service_name":"AWS Management Console","previous_status":"3","current_status":"0","timestamp":1778054773000},{"service":"route53","service_name":"Amazon Route 53","previous_status":"2","current_status":"0","timestamp":1778054773000}]}],"multipleservices-me-south-1":[{"summary":"Increased Error Rates","arn":"arn:aws:health:me-south-1::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_E6426_01AD72B4E1E","status":"3","date":"1772430987","event_log":[{"message":"We are investigating increased API error rates in a single Availability Zone (mes1-az2) in the ME-SOUTH-1 Region.","summary":"Increased connectivity issues and API Error Rates","status":"1","timestamp":1772430987},{"message":"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 RunInstances in the remaining AZs should succeed. Existing instances in the other AZs are not affected.","summary":"Increased connectivity issues and API Error Rates","status":"1","timestamp":1772435343},{"message":"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 time we will begin recovering affected resources. Currently, we expect recovery to take many hours. We will provide an update by 2:30 AM PST, or sooner if we have additional information to share.","summary":"Increased Connectivity Issues and API Error Rates","status":"1","timestamp":1772442207},{"message":"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 parallel, we are actively working on reducing the error rates and latencies that some customers are experiencing with EC2 APIs. For now, we recommend continuing to retry any failed API requests. We will provide an update by 6:00 AM PST on March 2, or sooner if we have additional information to share.","summary":"Increased Connectivity Issues and API Error Rates","status":"1","timestamp":1772448060},{"message":"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 has not yet been restored. 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. 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 AWS Region. We will provide an update by 11:00 AM PST on March 2, or sooner if we have additional information to share.","summary":"Increased Connectivity Issues and API Error Rates","status":"1","timestamp":1772461399},{"message":"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 becomes available.","summary":"Increased Connectivity Issues and API Error Rates","status":"1","timestamp":1772477520},{"message":"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 another update by 7:00 PM PST, or sooner if we have additional information to share.","summary":"Increased Connectivity Issues and API Error Rates","status":"1","timestamp":1772490547},{"message":"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 that resulted in additional water damage. We are working closely with local authorities and prioritizing the safety of our personnel throughout our recovery efforts.\n\nIn the ME-CENTRAL-1 (UAE) Region, two of our three Availability Zones (mec1-az2 and mec1-az3) remain significantly impaired. The third Availability Zone (mec1-az1) continues to operate normally, though some services have experienced indirect impact due to dependencies on the affected zones. In the ME-SOUTH-1 (Bahrain) Region, one facility has been impacted. Across both regions, customers are experiencing elevated error rates and degraded availability for services including Amazon EC2, Amazon S3, Amazon DynamoDB, AWS Lambda, Amazon Kinesis, Amazon CloudWatch, Amazon RDS, and the AWS Management Console and CLI. We are working to restore full service availability as quickly as possible, though we expect recovery to be prolonged given the nature of the physical damage involved.\n\nIn parallel with efforts to restore the physical infrastructure at the affected sites, we are pursuing multiple software-based recovery paths that do not depend on the underlying facilities being fully brought back online. For Amazon S3 and Amazon DynamoDB, we are actively working to restore data access and service availability through software mitigations, including deploying updates to enable S3 to operate within the current infrastructure constraints and remediating impaired DynamoDB tables to restore read and write availability for dependent services. Our focus on restoring these foundational services is deliberate, as recovery of Amazon S3 and Amazon DynamoDB will in turn enable a broad range of dependent AWS services to recover. For other affected service APIs, we are deploying targeted software updates to reduce error rates and restore functionality where possible, independent of the physical recovery timeline. We are also working to restore access to the AWS Management Console and CLI through network-level changes that route traffic away from the affected infrastructure. While these software-based mitigations can address many of the service-level impacts, some recovery actions are constrained by the physical state of the affected facilities — meaning that full restoration of certain services will require the underlying infrastructure to be repaired and brought back online. Across all services, our teams are working in parallel on both the physical restoration of the affected facilities and these software-based mitigations, with the goal of restoring as much customer access as possible as quickly as possible, even ahead of full infrastructure recovery. In addition, we are prioritizing the restoration of services and tools that enable customers to back up and migrate their data and applications out of the affected regions.\n\nFinally, even as we work to restore these facilities, the ongoing conflict in the region means that the broader operating environment in the Middle East remains unpredictable. We recommend that customers with workloads running in the Middle East consider taking action now to backup data and potentially migrate your workloads to alternate AWS Regions. We recommend customers exercise their disaster recovery plans, recover from remote backups stored in other regions, and update their applications to direct traffic away from the affected regions. For customers requiring guidance on alternate regions, we recommend considering AWS Regions in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements.\n\nWe will continue to provide updates as recovery progresses and as the situation evolves. Our next update will be provided by 9:00 PM PST on March 2, 2026, or sooner if new information becomes available.","summary":"Increased Connectivity Issues and API Error Rates","status":"1","timestamp":1772497351},{"message":"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 your latency and data residency requirements. We will provide another update by March 3 at 3:00 AM PST, or sooner if new information becomes available. \n\nFor more information on Cross-Region Replication, refer [1]. For more information on S3 Batch Replication, see [2]. For a simple script to quickly set up and start S3 Replication, see [3]. If you have questions or concerns, please contact AWS Support [4].\n\n[1] <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/replication.html\">https://docs.aws.amazon.com/AmazonS3/latest/userguide/replication.html</a>\n[2] <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-batch-replication-batch.html\">https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-batch-replication-batch.html</a>\n[3] <a href=\"https://github.com/awslabs/aws-support-tools/blob/master/S3/Setup_Replication/setup_replication.py\">https://github.com/awslabs/aws-support-tools/blob/master/S3/Setup_Replication/setup_replication.py</a>\n[4] <a href=\"https://aws.amazon.com/support\">https://aws.amazon.com/support</a>","summary":"Increased Connectivity Issues and API Error Rates","status":"1","timestamp":1772519220},{"message":"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. \n\nGiven 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 in our previous update. We will continue to provide updates as recovery progresses and as the situation evolves. Our next update will be provided by 6:00 AM PST on March 3, or sooner if new information becomes available.","summary":"Increased Connectivity Issues and API Error Rates","status":"1","timestamp":1772536238},{"message":"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.\n\nGiven 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 previously. We will provide our next update by 12:00 PM PST on March 3, or sooner if conditions change.","summary":"Increased Connectivity Issues and API Error Rates","status":"1","timestamp":1772546577},{"message":"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.\n\nWe continue to strongly recommend that customers with workloads running in the Middle East take action now to migrate those workloads to alternate AWS Regions. Customers should enact their disaster recovery plans, recover from remote backups stored in other Regions, and update their applications to direct traffic away from the affected Regions. For customers requiring guidance on alternate regions, we recommend considering AWS Regions in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements.","summary":"Increased Connectivity Issues and API Error Rates","status":"1","timestamp":1772556000},{"message":"We are providing an update on the ongoing service disruption. The Middle East (Bahrain) Region (ME-SOUTH-1) has suffered damage due to the conflict in the Middle East and is currently unavailable. Customers should recover their resources in other Regions from remote backups. Relevant billing operations are currently suspended while we restore normal operations in this AWS Region. This process is expected to take several months.  ","summary":"Increased Connectivity Issues and API Error Rates","status":"3","timestamp":1777532831}],"impacted_services":{"acm-pca-me-south-1":{"service_name":"AWS Private Certificate Authority","current":"3","max":"3"},"airflow-me-south-1":{"service_name":"Amazon Managed Workflows for Apache Airflow","current":"3","max":"3"},"amplify-me-south-1":{"service_name":"AWS Amplify","current":"3","max":"3"},"amplifyadmin-me-south-1":{"service_name":"AWS Amplify Admin","current":"3","max":"3"},"apigateway-me-south-1":{"service_name":"Amazon API Gateway","current":"3","max":"3"},"appconfig-me-south-1":{"service_name":"AWS AppConfig","current":"3","max":"3"},"applicationinsights-me-south-1":{"service_name":"Amazon CloudWatch Application Insights","current":"3","max":"3"},"appmesh-me-south-1":{"service_name":"AWS App Mesh","current":"3","max":"3"},"appsync-me-south-1":{"service_name":"AWS AppSync","current":"3","max":"3"},"appwizard-me-south-1":{"service_name":"AWS Launch Wizard","current":"3","max":"3"},"athena-me-south-1":{"service_name":"Amazon Athena","current":"3","max":"3"},"autoscaling-me-south-1":{"service_name":"Auto Scaling","current":"3","max":"3"},"awsiot-me-south-1":{"service_name":"AWS IoT Core","current":"3","max":"3"},"awsiotdevicemanagement-me-south-1":{"service_name":"AWS IoT Device Management","current":"3","max":"3"},"awswaf-me-south-1":{"service_name":"AWS WAF","current":"3","max":"3"},"backup-me-south-1":{"service_name":"AWS Backup","current":"3","max":"3"},"batch-me-south-1":{"service_name":"AWS Batch","current":"3","max":"3"},"bedrock-me-south-1":{"service_name":"Amazon Bedrock","current":"3","max":"3"},"cassandra-me-south-1":{"service_name":"Amazon Keyspaces","current":"3","max":"3"},"certificatemanager-me-south-1":{"service_name":"AWS Certificate Manager","current":"3","max":"3"},"clientvpn-me-south-1":{"service_name":"AWS Client VPN","current":"3","max":"3"},"cloud9-me-south-1":{"service_name":"AWS Cloud9","current":"3","max":"3"},"cloudformation-me-south-1":{"service_name":"AWS CloudFormation","current":"3","max":"3"},"cloudfront":{"service_name":"Amazon CloudFront","current":"0","max":"1"},"cloudhsm-me-south-1":{"service_name":"AWS CloudHSM","current":"3","max":"3"},"cloudshell-me-south-1":{"service_name":"AWS CloudShell","current":"3","max":"3"},"cloudtrail-me-south-1":{"service_name":"AWS CloudTrail","current":"3","max":"3"},"cloudwan":{"service_name":"AWS Cloud WAN","current":"0","max":"1"},"cloudwatch-me-south-1":{"service_name":"Amazon CloudWatch","current":"3","max":"3"},"cloudwatchsynthetics-me-south-1":{"service_name":"Amazon CloudWatch Synthetics","current":"3","max":"3"},"codebuild-me-south-1":{"service_name":"AWS CodeBuild","current":"3","max":"3"},"codecommit-me-south-1":{"service_name":"AWS CodeCommit","current":"3","max":"3"},"codedeploy-me-south-1":{"service_name":"AWS CodeDeploy","current":"3","max":"3"},"codepipeline-me-south-1":{"service_name":"AWS CodePipeline","current":"3","max":"3"},"cognito-me-south-1":{"service_name":"Amazon Cognito","current":"3","max":"3"},"computeoptimizer-me-south-1":{"service_name":"AWS Compute Optimizer","current":"3","max":"3"},"config-me-south-1":{"service_name":"AWS Config","current":"3","max":"3"},"consolemobileapp-me-south-1":{"service_name":"AWS Console Mobile App","current":"3","max":"3"},"controlcatalog-me-south-1":{"service_name":"Control Catalog","current":"3","max":"3"},"controltower-me-south-1":{"service_name":"AWS Control Tower","current":"3","max":"3"},"datasync-me-south-1":{"service_name":"AWS DataSync","current":"3","max":"3"},"detective-me-south-1":{"service_name":"Amazon Detective","current":"3","max":"3"},"directconnect-me-south-1":{"service_name":"AWS Direct Connect","current":"3","max":"3"},"directoryservice-me-south-1":{"service_name":"AWS Directory Service","current":"3","max":"3"},"dlm-me-south-1":{"service_name":"Amazon Data Lifecycle Manager","current":"3","max":"3"},"dms-me-south-1":{"service_name":"AWS Database Migration Service","current":"3","max":"3"},"drs-me-south-1":{"service_name":"AWS Elastic Disaster Recovery","current":"3","max":"3"},"dynamodb-me-south-1":{"service_name":"Amazon DynamoDB","current":"3","max":"3"},"ec2-me-south-1":{"service_name":"Amazon Elastic Compute Cloud","current":"3","max":"3"},"ec2serialconsole-me-south-1":{"service_name":"EC2 Serial Console","current":"3","max":"3"},"ec2systemsmanager-me-south-1":{"service_name":"AWS Systems Manager","current":"3","max":"3"},"ecr-me-south-1":{"service_name":"Amazon Elastic Container Registry","current":"3","max":"3"},"ecs-me-south-1":{"service_name":"Amazon Elastic Container Service","current":"3","max":"3"},"eks-me-south-1":{"service_name":"Amazon Elastic Kubernetes Service","current":"3","max":"3"},"elasticache-me-south-1":{"service_name":"Amazon ElastiCache","current":"3","max":"3"},"elasticbeanstalk-me-south-1":{"service_name":"AWS Elastic Beanstalk","current":"3","max":"3"},"elasticfilesystem-me-south-1":{"service_name":"Amazon Elastic File System","current":"3","max":"3"},"elasticsearch-me-south-1":{"service_name":"Amazon OpenSearch Service","current":"3","max":"3"},"elb-me-south-1":{"service_name":"Amazon Elastic Load Balancing","current":"3","max":"3"},"emr-me-south-1":{"service_name":"Amazon Elastic MapReduce","current":"3","max":"3"},"emrserverless-me-south-1":{"service_name":"Amazon EMR Serverless","current":"3","max":"3"},"endusermessaging-me-south-1":{"service_name":"AWS End User Messaging","current":"3","max":"3"},"events-me-south-1":{"service_name":"Amazon EventBridge","current":"3","max":"3"},"fargate-me-south-1":{"service_name":"AWS Fargate","current":"3","max":"3"},"firehose-me-south-1":{"service_name":"Amazon Data Firehose","current":"3","max":"3"},"fis-me-south-1":{"service_name":"AWS Fault Injection Service","current":"3","max":"3"},"fms-me-south-1":{"service_name":"AWS Firewall Manager","current":"3","max":"3"},"freertos-me-south-1":{"service_name":"Amazon FreeRTOS","current":"3","max":"3"},"fsx-me-south-1":{"service_name":"Amazon FSx","current":"3","max":"3"},"gameliftstreams":{"service_name":"Amazon GameLift Streams","current":"3","max":"3"},"glacier-me-south-1":{"service_name":"Amazon Glacier","current":"3","max":"3"},"globalaccelerator":{"service_name":"AWS Global Accelerator","current":"0","max":"1"},"glue-me-south-1":{"service_name":"AWS Glue","current":"3","max":"3"},"groundstation-me-south-1":{"service_name":"AWS Ground Station","current":"3","max":"3"},"guardduty-me-south-1":{"service_name":"Amazon GuardDuty","current":"3","max":"3"},"iamidentitycenter-me-south-1":{"service_name":"AWS IAM Identity Center","current":"3","max":"3"},"iamrolesanywhere-me-south-1":{"service_name":"AWS Identity and Access Management Roles Anywhere","current":"3","max":"3"},"imagebuilder-me-south-1":{"service_name":"EC2 Image Builder","current":"3","max":"3"},"infrastructureperformance-me-south-1":{"service_name":"Infrastructure Performance","current":"3","max":"3"},"inspector-me-south-1":{"service_name":"Amazon Inspector","current":"3","max":"3"},"internetconnectivity-me-south-1":{"service_name":"AWS Internet Connectivity","current":"3","max":"3"},"internetmonitor-me-south-1":{"service_name":"Amazon CloudWatch Internet Monitor","current":"3","max":"3"},"iotdevicedefender-me-south-1":{"service_name":"AWS IoT Device Defender","current":"3","max":"3"},"ipam-me-south-1":{"service_name":"Amazon VPC IP Address Manager","current":"3","max":"3"},"kafka-me-south-1":{"service_name":"Amazon Managed Streaming for Apache Kafka","current":"3","max":"3"},"kinesis-me-south-1":{"service_name":"Amazon Kinesis Data Streams","current":"3","max":"3"},"kinesisanalytics-me-south-1":{"service_name":"Amazon Managed Service for Apache Flink","current":"3","max":"3"},"kinesisvideo-me-south-1":{"service_name":"Amazon Kinesis Video Streams","current":"3","max":"3"},"kms-me-south-1":{"service_name":"AWS Key Management Service","current":"3","max":"3"},"lakeformation-me-south-1":{"service_name":"AWS Lake Formation","current":"3","max":"3"},"lambda-me-south-1":{"service_name":"AWS Lambda","current":"3","max":"3"},"licensemanager-me-south-1":{"service_name":"AWS License Manager","current":"3","max":"3"},"macie-me-south-1":{"service_name":"Amazon Macie","current":"3","max":"3"},"managedssh-me-south-1":{"service_name":"Amazon EC2 Instance Connect","current":"3","max":"3"},"management-console":{"service_name":"AWS Management Console","current":"0","max":"2"},"mgn-me-south-1":{"service_name":"AWS Application Migration Service","current":"3","max":"3"},"mq-me-south-1":{"service_name":"Amazon MQ","current":"3","max":"3"},"natgateway-me-south-1":{"service_name":"AWS NAT Gateway","current":"3","max":"3"},"neptune-db-me-south-1":{"service_name":"Amazon Neptune","current":"3","max":"3"},"networkaccessanalyzer-me-south-1":{"service_name":"Network Access Analyzer","current":"3","max":"3"},"networkfirewall-me-south-1":{"service_name":"AWS Network Firewall","current":"3","max":"3"},"outposts-me-south-1":{"service_name":"AWS Outposts","current":"3","max":"3"},"pca-connector-scep-me-south-1":{"service_name":"AWS Private CA Connector for SCEP","current":"3","max":"3"},"pcaconnectorad-me-south-1":{"service_name":"AWS Private CA Connector for Active Directory","current":"3","max":"3"},"polly-me-south-1":{"service_name":"Amazon Polly","current":"3","max":"3"},"privatelink-me-south-1":{"service_name":"AWS VPCE PrivateLink","current":"3","max":"3"},"ram-me-south-1":{"service_name":"AWS Resource Access Manager","current":"3","max":"3"},"rds-me-south-1":{"service_name":"Amazon Relational Database Service","current":"3","max":"3"},"reachabilityanalyzer-me-south-1":{"service_name":"Reachability Analyzer","current":"3","max":"3"},"redshift-me-south-1":{"service_name":"Amazon Redshift","current":"3","max":"3"},"resiliencehub-me-south-1":{"service_name":"AWS Resilience Hub","current":"3","max":"3"},"resourceexplorer-me-south-1":{"service_name":"AWS Resource Explorer","current":"3","max":"3"},"resourcegroups-me-south-1":{"service_name":"AWS Resource Groups","current":"3","max":"3"},"resourcegroupstaggingapi-me-south-1":{"service_name":"AWS Resource Groups Tagging API","current":"3","max":"3"},"route53":{"service_name":"Amazon Route 53","current":"0","max":"1"},"route53privatedns-me-south-1":{"service_name":"Amazon Route 53 Private DNS","current":"3","max":"3"},"route53resolver-me-south-1":{"service_name":"Amazon Route 53 Resolver","current":"3","max":"3"},"rum-me-south-1":{"service_name":"Amazon CloudWatch RUM","current":"3","max":"3"},"s3-me-south-1":{"service_name":"Amazon Simple Storage Service","current":"3","max":"3"},"s3rtc-me-south-1":{"service_name":"Amazon S3 Replication Time Control","current":"3","max":"3"},"sagemaker-me-south-1":{"service_name":"Amazon SageMaker","current":"3","max":"3"},"scheduler-me-south-1":{"service_name":"Amazon EventBridge Scheduler","current":"3","max":"3"},"secretsmanager-me-south-1":{"service_name":"AWS Secrets Manager","current":"3","max":"3"},"security-ir-me-south-1":{"service_name":"AWS Security Incident Response","current":"3","max":"3"},"securityhub-me-south-1":{"service_name":"AWS Security Hub","current":"3","max":"3"},"serverlessrepo-me-south-1":{"service_name":"AWS Serverless Application Repository","current":"3","max":"3"},"servicecatalog-me-south-1":{"service_name":"AWS Service Catalog","current":"3","max":"3"},"servicediscovery-me-south-1":{"service_name":"AWS Cloud Map","current":"3","max":"3"},"servicequotas-me-south-1":{"service_name":"AWS Service Quotas","current":"3","max":"3"},"ses-me-south-1":{"service_name":"Amazon Simple Email Service","current":"3","max":"3"},"signin-me-south-1":{"service_name":"AWS Sign-In","current":"3","max":"3"},"sns-me-south-1":{"service_name":"Amazon Simple Notification Service","current":"3","max":"3"},"sqs-me-south-1":{"service_name":"Amazon Simple Queue Service","current":"3","max":"3"},"ssmsap-me-south-1":{"service_name":"AWS Systems Manager for SAP","current":"3","max":"3"},"state-me-south-1":{"service_name":"AWS Step Functions","current":"3","max":"3"},"storagegateway-me-south-1":{"service_name":"AWS Storage Gateway","current":"3","max":"3"},"sts-me-south-1":{"service_name":"AWS Security Token Service","current":"3","max":"3"},"swf-me-south-1":{"service_name":"Amazon Simple Workflow Service","current":"3","max":"3"},"trafficmirroring-me-south-1":{"service_name":"Traffic Mirroring","current":"3","max":"3"},"transcribe-me-south-1":{"service_name":"Amazon Transcribe","current":"3","max":"3"},"transfer-me-south-1":{"service_name":"AWS Transfer Family","current":"3","max":"3"},"transitgateway-me-south-1":{"service_name":"AWS Transit Gateway","current":"3","max":"3"},"verifiedpermissions-me-south-1":{"service_name":"Amazon Verified Permissions","current":"3","max":"3"},"vmimportexport-me-south-1":{"service_name":"VM Import/Export","current":"3","max":"3"},"vpc-me-south-1":{"service_name":"Amazon Virtual Private Cloud","current":"3","max":"3"},"vpclattice-me-south-1":{"service_name":"Amazon VPC Lattice","current":"3","max":"3"},"vpnvpc-me-south-1":{"service_name":"AWS Site-to-Site VPN","current":"3","max":"3"},"wellarchitected-me-south-1":{"service_name":"AWS Well-Architected Tool","current":"3","max":"3"},"xray-me-south-1":{"service_name":"AWS X-Ray","current":"3","max":"3"}},"impacted_service_status_changes":[{"service":"acm-pca-me-south-1","service_name":"AWS Private Certificate Authority","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"airflow-me-south-1","service_name":"Amazon Managed Workflows for Apache Airflow","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"amplify-me-south-1","service_name":"AWS Amplify","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"amplifyadmin-me-south-1","service_name":"AWS Amplify Admin","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"apigateway-me-south-1","service_name":"Amazon API Gateway","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"appconfig-me-south-1","service_name":"AWS AppConfig","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"applicationinsights-me-south-1","service_name":"Amazon CloudWatch Application Insights","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"appmesh-me-south-1","service_name":"AWS App Mesh","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"appsync-me-south-1","service_name":"AWS AppSync","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"appwizard-me-south-1","service_name":"AWS Launch Wizard","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"athena-me-south-1","service_name":"Amazon Athena","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"autoscaling-me-south-1","service_name":"Auto Scaling","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"awsiot-me-south-1","service_name":"AWS IoT Core","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"awsiotdevicemanagement-me-south-1","service_name":"AWS IoT Device Management","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"awswaf-me-south-1","service_name":"AWS WAF","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"backup-me-south-1","service_name":"AWS Backup","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"batch-me-south-1","service_name":"AWS Batch","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"bedrock-me-south-1","service_name":"Amazon Bedrock","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"cassandra-me-south-1","service_name":"Amazon Keyspaces","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"certificatemanager-me-south-1","service_name":"AWS Certificate Manager","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"clientvpn-me-south-1","service_name":"AWS Client VPN","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"cloud9-me-south-1","service_name":"AWS Cloud9","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"cloudformation-me-south-1","service_name":"AWS CloudFormation","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"cloudfront","service_name":"Amazon CloudFront","previous_status":"0","current_status":"1","timestamp":1772430987000},{"service":"cloudhsm-me-south-1","service_name":"AWS CloudHSM","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"cloudshell-me-south-1","service_name":"AWS CloudShell","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"cloudtrail-me-south-1","service_name":"AWS CloudTrail","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"cloudwan","service_name":"AWS Cloud WAN","previous_status":"0","current_status":"1","timestamp":1772430987000},{"service":"cloudwatch-me-south-1","service_name":"Amazon CloudWatch","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"cloudwatchsynthetics-me-south-1","service_name":"Amazon CloudWatch Synthetics","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"codebuild-me-south-1","service_name":"AWS CodeBuild","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"codecommit-me-south-1","service_name":"AWS CodeCommit","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"codedeploy-me-south-1","service_name":"AWS CodeDeploy","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"codepipeline-me-south-1","service_name":"AWS CodePipeline","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"cognito-me-south-1","service_name":"Amazon Cognito","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"computeoptimizer-me-south-1","service_name":"AWS Compute Optimizer","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"config-me-south-1","service_name":"AWS Config","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"consolemobileapp-me-south-1","service_name":"AWS Console Mobile App","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"controlcatalog-me-south-1","service_name":"Control Catalog","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"controltower-me-south-1","service_name":"AWS Control Tower","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"datasync-me-south-1","service_name":"AWS DataSync","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"detective-me-south-1","service_name":"Amazon Detective","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"directconnect-me-south-1","service_name":"AWS Direct Connect","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"directoryservice-me-south-1","service_name":"AWS Directory Service","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"dlm-me-south-1","service_name":"Amazon Data Lifecycle Manager","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"dms-me-south-1","service_name":"AWS Database Migration Service","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"drs-me-south-1","service_name":"AWS Elastic Disaster Recovery","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"dynamodb-me-south-1","service_name":"Amazon DynamoDB","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"ec2-me-south-1","service_name":"Amazon Elastic Compute Cloud","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"ec2serialconsole-me-south-1","service_name":"EC2 Serial Console","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"ec2systemsmanager-me-south-1","service_name":"AWS Systems Manager","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"ecr-me-south-1","service_name":"Amazon Elastic Container Registry","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"ecs-me-south-1","service_name":"Amazon Elastic Container Service","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"eks-me-south-1","service_name":"Amazon Elastic Kubernetes Service","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"elasticache-me-south-1","service_name":"Amazon ElastiCache","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"elasticbeanstalk-me-south-1","service_name":"AWS Elastic Beanstalk","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"elasticfilesystem-me-south-1","service_name":"Amazon Elastic File System","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"elasticsearch-me-south-1","service_name":"Amazon OpenSearch Service","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"elb-me-south-1","service_name":"Amazon Elastic Load Balancing","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"emr-me-south-1","service_name":"Amazon Elastic MapReduce","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"emrserverless-me-south-1","service_name":"Amazon EMR Serverless","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"endusermessaging-me-south-1","service_name":"AWS End User Messaging","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"events-me-south-1","service_name":"Amazon EventBridge","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"fargate-me-south-1","service_name":"AWS Fargate","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"firehose-me-south-1","service_name":"Amazon Data Firehose","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"fis-me-south-1","service_name":"AWS Fault Injection Service","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"fms-me-south-1","service_name":"AWS Firewall Manager","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"freertos-me-south-1","service_name":"Amazon FreeRTOS","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"fsx-me-south-1","service_name":"Amazon FSx","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"gameliftstreams","service_name":"Amazon GameLift Streams","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"glacier-me-south-1","service_name":"Amazon Glacier","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"globalaccelerator","service_name":"AWS Global Accelerator","previous_status":"0","current_status":"1","timestamp":1772430987000},{"service":"glue-me-south-1","service_name":"AWS Glue","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"groundstation-me-south-1","service_name":"AWS Ground Station","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"guardduty-me-south-1","service_name":"Amazon GuardDuty","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"iamidentitycenter-me-south-1","service_name":"AWS IAM Identity Center","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"iamrolesanywhere-me-south-1","service_name":"AWS Identity and Access Management Roles Anywhere","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"imagebuilder-me-south-1","service_name":"EC2 Image Builder","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"infrastructureperformance-me-south-1","service_name":"Infrastructure Performance","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"inspector-me-south-1","service_name":"Amazon Inspector","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"internetconnectivity-me-south-1","service_name":"AWS Internet Connectivity","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"internetmonitor-me-south-1","service_name":"Amazon CloudWatch Internet Monitor","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"iotdevicedefender-me-south-1","service_name":"AWS IoT Device Defender","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"ipam-me-south-1","service_name":"Amazon VPC IP Address Manager","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"kafka-me-south-1","service_name":"Amazon Managed Streaming for Apache Kafka","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"kinesis-me-south-1","service_name":"Amazon Kinesis Data Streams","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"kinesisanalytics-me-south-1","service_name":"Amazon Managed Service for Apache Flink","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"kinesisvideo-me-south-1","service_name":"Amazon Kinesis Video Streams","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"kms-me-south-1","service_name":"AWS Key Management Service","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"lakeformation-me-south-1","service_name":"AWS Lake Formation","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"lambda-me-south-1","service_name":"AWS Lambda","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"licensemanager-me-south-1","service_name":"AWS License Manager","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"macie-me-south-1","service_name":"Amazon Macie","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"managedssh-me-south-1","service_name":"Amazon EC2 Instance Connect","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"management-console","service_name":"AWS Management Console","previous_status":"0","current_status":"2","timestamp":1772430987000},{"service":"mgn-me-south-1","service_name":"AWS Application Migration Service","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"mq-me-south-1","service_name":"Amazon MQ","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"natgateway-me-south-1","service_name":"AWS NAT Gateway","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"neptune-db-me-south-1","service_name":"Amazon Neptune","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"networkaccessanalyzer-me-south-1","service_name":"Network Access Analyzer","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"networkfirewall-me-south-1","service_name":"AWS Network Firewall","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"outposts-me-south-1","service_name":"AWS Outposts","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"pca-connector-scep-me-south-1","service_name":"AWS Private CA Connector for SCEP","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"pcaconnectorad-me-south-1","service_name":"AWS Private CA Connector for Active Directory","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"polly-me-south-1","service_name":"Amazon Polly","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"privatelink-me-south-1","service_name":"AWS VPCE PrivateLink","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"ram-me-south-1","service_name":"AWS Resource Access Manager","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"rds-me-south-1","service_name":"Amazon Relational Database Service","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"reachabilityanalyzer-me-south-1","service_name":"Reachability Analyzer","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"redshift-me-south-1","service_name":"Amazon Redshift","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"resiliencehub-me-south-1","service_name":"AWS Resilience Hub","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"resourceexplorer-me-south-1","service_name":"AWS Resource Explorer","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"resourcegroups-me-south-1","service_name":"AWS Resource Groups","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"resourcegroupstaggingapi-me-south-1","service_name":"AWS Resource Groups Tagging API","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"route53","service_name":"Amazon Route 53","previous_status":"0","current_status":"1","timestamp":1772430987000},{"service":"route53privatedns-me-south-1","service_name":"Amazon Route 53 Private DNS","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"route53resolver-me-south-1","service_name":"Amazon Route 53 Resolver","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"rum-me-south-1","service_name":"Amazon CloudWatch RUM","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"s3-me-south-1","service_name":"Amazon Simple Storage Service","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"s3rtc-me-south-1","service_name":"Amazon S3 Replication Time Control","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"sagemaker-me-south-1","service_name":"Amazon SageMaker","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"scheduler-me-south-1","service_name":"Amazon EventBridge Scheduler","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"secretsmanager-me-south-1","service_name":"AWS Secrets Manager","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"security-ir-me-south-1","service_name":"AWS Security Incident Response","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"securityhub-me-south-1","service_name":"AWS Security Hub","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"serverlessrepo-me-south-1","service_name":"AWS Serverless Application Repository","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"servicecatalog-me-south-1","service_name":"AWS Service Catalog","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"servicediscovery-me-south-1","service_name":"AWS Cloud Map","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"servicequotas-me-south-1","service_name":"AWS Service Quotas","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"ses-me-south-1","service_name":"Amazon Simple Email Service","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"signin-me-south-1","service_name":"AWS Sign-In","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"sns-me-south-1","service_name":"Amazon Simple Notification Service","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"sqs-me-south-1","service_name":"Amazon Simple Queue Service","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"ssmsap-me-south-1","service_name":"AWS Systems Manager for SAP","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"state-me-south-1","service_name":"AWS Step Functions","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"storagegateway-me-south-1","service_name":"AWS Storage Gateway","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"sts-me-south-1","service_name":"AWS Security Token Service","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"swf-me-south-1","service_name":"Amazon Simple Workflow Service","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"trafficmirroring-me-south-1","service_name":"Traffic Mirroring","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"transcribe-me-south-1","service_name":"Amazon Transcribe","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"transfer-me-south-1","service_name":"AWS Transfer Family","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"transitgateway-me-south-1","service_name":"AWS Transit Gateway","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"verifiedpermissions-me-south-1","service_name":"Amazon Verified Permissions","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"vmimportexport-me-south-1","service_name":"VM Import/Export","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"vpc-me-south-1","service_name":"Amazon Virtual Private Cloud","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"vpclattice-me-south-1","service_name":"Amazon VPC Lattice","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"vpnvpc-me-south-1","service_name":"AWS Site-to-Site VPN","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"wellarchitected-me-south-1","service_name":"AWS Well-Architected Tool","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"xray-me-south-1","service_name":"AWS X-Ray","previous_status":"0","current_status":"3","timestamp":1772430987000},{"service":"cloudfront","service_name":"Amazon CloudFront","previous_status":"1","current_status":"0","timestamp":1778053812000},{"service":"cloudwan","service_name":"AWS Cloud WAN","previous_status":"1","current_status":"0","timestamp":1778053812000},{"service":"globalaccelerator","service_name":"AWS Global Accelerator","previous_status":"1","current_status":"0","timestamp":1778053812000},{"service":"management-console","service_name":"AWS Management Console","previous_status":"2","current_status":"0","timestamp":1778053812000},{"service":"route53","service_name":"Amazon Route 53","previous_status":"1","current_status":"0","timestamp":1778053812000}]}],"bedrock-us-east-1":[{"summary":"[RESOLVED] Fable 5 and Mythos 5 Access","arn":"arn:aws:health:us-east-1::event/BEDROCK/AWS_BEDROCK_OPERATIONAL_ISSUE/AWS_BEDROCK_OPERATIONAL_ISSUE_588F5_70C147423A3","status":"1","date":"1781314018","event_log":[{"message":"To support compliance with the US Government export control directive, Anthropic has asked us to revoke access to Claude Fable 5 and Claude Mythos 5 for all users in all regions. All other models, including Opus 4.8, are not affected and you can continue using them in full confidence. Please view the <a href=\"https://www.anthropic.com/news/fable-mythos-access\">Anthropic statement</a> for further details.","summary":"Fable 5 and Mythos 5 Access","status":"1","timestamp":1781314018},{"message":"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 <a href=\"https://www.anthropic.com/news/fable-mythos-access\">Anthropic statement</a>.","summary":"[RESOLVED] Fable 5 and Mythos 5 Access","status":"0","timestamp":1781547203}]}],"internetconnectivity-sa-east-1":[{"summary":"[RESOLVED] Network Connectivity","arn":"arn:aws:health:sa-east-1::event/INTERNETCONNECTIVITY/AWS_INTERNETCONNECTIVITY_OPERATIONAL_ISSUE/AWS_INTERNETCONNECTIVITY_OPERATIONAL_ISSUE_94D57_A1E513FBAE6","status":"1","date":"1770489000","event_log":[{"message":"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.","summary":"[Resolved] Network Connectivity","status":"1","timestamp":1770489000}]},{"summary":"[RESOLVED] Internet Connectivity Issues","arn":"arn:aws:health:sa-east-1::event/INTERNETCONNECTIVITY/AWS_INTERNETCONNECTIVITY_OPERATIONAL_ISSUE/AWS_INTERNETCONNECTIVITY_OPERATIONAL_ISSUE_4FB91_017AE394449","status":"1","date":"1780719878","event_log":[{"message":"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.","summary":"Internet Connectivity Issues","status":"1","timestamp":1780719878}]}],"route53":[{"summary":"[RESOLVED] Increased API Error Rates","arn":"arn:aws:health:global::event/ROUTE53/AWS_ROUTE53_OPERATIONAL_ISSUE/AWS_ROUTE53_OPERATIONAL_ISSUE_67C7D_B6C0423B023","status":"1","date":"1779493119","event_log":[{"message":"We are investigating increased error rates for Route53 API calls.","summary":"Increased API Error Rates","status":"1","timestamp":1779493119},{"message":"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 this issue to reoccur. The issue has been resolved and the service is operating normally.","summary":"[RESOLVED] Increased API Error Rates","status":"0","timestamp":1779495217}]}],"ec2-eu-west-3":[{"summary":"[RESOLVED] Increased Connectivity Issues","arn":"arn:aws:health:eu-west-3::event/EC2/AWS_EC2_OPERATIONAL_ISSUE/AWS_EC2_OPERATIONAL_ISSUE_FB70E_B77B1D343FD","status":"1","date":"1777289237","event_log":[{"message":"We are investigating instance connectivity issues in a single Availability Zone (euw3-az2) in the EU-WEST-3 Region.","summary":"Increased Connectivity Issues","status":"1","timestamp":1777289237},{"message":"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.\n\nWe 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.\n\nNo additional action is required for EC2 instances and EBS volumes that were impacted during the power loss event, as these have been fully recovered. While EC2 and EBS have recovered, some AWS services may take additional time to fully recover as they process backlogs and complete their own recovery procedures. The issue has been resolved and the service is operating normally.","summary":"[RESOLVED] Increased Connectivity Issues","status":"0","timestamp":1777291557}],"impacted_services":{"acm-pca-eu-west-3":{"service_name":"AWS Private Certificate Authority","current":"0","max":"1"},"apigateway-eu-west-3":{"service_name":"Amazon API Gateway","current":"0","max":"1"},"appconfig-eu-west-3":{"service_name":"AWS AppConfig","current":"0","max":"1"},"appstream2-eu-west-3":{"service_name":"Amazon WorkSpaces Applications","current":"0","max":"1"},"appsync-eu-west-3":{"service_name":"AWS AppSync","current":"0","max":"1"},"athena-eu-west-3":{"service_name":"Amazon Athena","current":"0","max":"1"},"awsiot-eu-west-3":{"service_name":"AWS IoT Core","current":"0","max":"1"},"awsiotdevicemanagement-eu-west-3":{"service_name":"AWS IoT Device Management","current":"0","max":"1"},"bedrock-agentcore-eu-west-3":{"service_name":"Bedrock AgentCore","current":"0","max":"1"},"certificatemanager-eu-west-3":{"service_name":"AWS Certificate Manager","current":"0","max":"1"},"clientvpn-eu-west-3":{"service_name":"AWS Client VPN","current":"0","max":"1"},"cloud9-eu-west-3":{"service_name":"AWS Cloud9","current":"0","max":"1"},"cloudformation-eu-west-3":{"service_name":"AWS CloudFormation","current":"0","max":"1"},"cloudfront":{"service_name":"Amazon CloudFront","current":"0","max":"1"},"cloudshell-eu-west-3":{"service_name":"AWS CloudShell","current":"0","max":"1"},"cloudwan":{"service_name":"AWS Cloud WAN","current":"0","max":"1"},"codeartifact-eu-west-3":{"service_name":"AWS CodeArtifact","current":"0","max":"1"},"codecommit-eu-west-3":{"service_name":"AWS CodeCommit","current":"0","max":"1"},"codedeploy-eu-west-3":{"service_name":"AWS CodeDeploy","current":"0","max":"1"},"dms-eu-west-3":{"service_name":"AWS Database Migration Service","current":"0","max":"1"},"docdb-eu-west-3":{"service_name":"Amazon DocumentDB","current":"0","max":"1"},"ecs-eu-west-3":{"service_name":"Amazon Elastic Container Service","current":"0","max":"1"},"eks-eu-west-3":{"service_name":"Amazon Elastic Kubernetes Service","current":"0","max":"1"},"elasticbeanstalk-eu-west-3":{"service_name":"AWS Elastic Beanstalk","current":"0","max":"1"},"elasticfilesystem-eu-west-3":{"service_name":"Amazon Elastic File System","current":"0","max":"1"},"elb-eu-west-3":{"service_name":"Amazon Elastic Load Balancing","current":"0","max":"1"},"emr-eu-west-3":{"service_name":"Amazon Elastic MapReduce","current":"0","max":"1"},"events-eu-west-3":{"service_name":"Amazon EventBridge","current":"0","max":"1"},"fargate-eu-west-3":{"service_name":"AWS Fargate","current":"0","max":"1"},"fsx-eu-west-3":{"service_name":"Amazon FSx","current":"0","max":"1"},"iotdevicedefender-eu-west-3":{"service_name":"AWS IoT Device Defender","current":"0","max":"1"},"ivs":{"service_name":"Amazon Interactive Video Service","current":"0","max":"1"},"kinesis-eu-west-3":{"service_name":"Amazon Kinesis Data Streams","current":"0","max":"1"},"kms-eu-west-3":{"service_name":"AWS Key Management Service","current":"0","max":"1"},"lambda-eu-west-3":{"service_name":"AWS Lambda","current":"0","max":"1"},"mq-eu-west-3":{"service_name":"Amazon MQ","current":"0","max":"1"},"natgateway-eu-west-3":{"service_name":"AWS NAT Gateway","current":"0","max":"1"},"networkaccessanalyzer-eu-west-3":{"service_name":"Network Access Analyzer","current":"0","max":"1"},"networkfirewall-eu-west-3":{"service_name":"AWS Network Firewall","current":"0","max":"1"},"paymentcryptography-eu-west-3":{"service_name":"AWS Payment Cryptography","current":"0","max":"1"},"pcs-eu-west-3":{"service_name":"AWS Parallel Computing Service","current":"0","max":"1"},"privatelink-eu-west-3":{"service_name":"AWS VPCE PrivateLink","current":"0","max":"1"},"redshift-eu-west-3":{"service_name":"Amazon Redshift","current":"0","max":"1"},"s3-eu-west-3":{"service_name":"Amazon Simple Storage Service","current":"0","max":"1"},"scheduler-eu-west-3":{"service_name":"Amazon EventBridge Scheduler","current":"0","max":"1"},"sns-eu-west-3":{"service_name":"Amazon Simple Notification Service","current":"0","max":"1"},"sqs-eu-west-3":{"service_name":"Amazon Simple Queue Service","current":"0","max":"1"},"state-eu-west-3":{"service_name":"AWS Step Functions","current":"0","max":"1"},"swf-eu-west-3":{"service_name":"Amazon Simple Workflow Service","current":"0","max":"1"},"trafficmirroring-eu-west-3":{"service_name":"Traffic Mirroring","current":"0","max":"1"},"transfer-eu-west-3":{"service_name":"AWS Transfer Family","current":"0","max":"1"},"transitgateway-eu-west-3":{"service_name":"AWS Transit Gateway","current":"0","max":"1"},"vpnvpc-eu-west-3":{"service_name":"AWS Site-to-Site VPN","current":"0","max":"1"},"workspaces-eu-west-3":{"service_name":"Amazon WorkSpaces","current":"0","max":"1"}},"impacted_service_status_changes":[{"service":"acm-pca-eu-west-3","service_name":"AWS Private Certificate Authority","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"apigateway-eu-west-3","service_name":"Amazon API Gateway","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"appconfig-eu-west-3","service_name":"AWS AppConfig","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"appstream2-eu-west-3","service_name":"Amazon WorkSpaces Applications","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"appsync-eu-west-3","service_name":"AWS AppSync","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"athena-eu-west-3","service_name":"Amazon Athena","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"awsiot-eu-west-3","service_name":"AWS IoT Core","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"awsiotdevicemanagement-eu-west-3","service_name":"AWS IoT Device Management","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"bedrock-agentcore-eu-west-3","service_name":"Bedrock AgentCore","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"certificatemanager-eu-west-3","service_name":"AWS Certificate Manager","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"clientvpn-eu-west-3","service_name":"AWS Client VPN","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"cloud9-eu-west-3","service_name":"AWS Cloud9","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"cloudformation-eu-west-3","service_name":"AWS CloudFormation","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"cloudfront","service_name":"Amazon CloudFront","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"cloudshell-eu-west-3","service_name":"AWS CloudShell","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"cloudwan","service_name":"AWS Cloud WAN","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"codeartifact-eu-west-3","service_name":"AWS CodeArtifact","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"codecommit-eu-west-3","service_name":"AWS CodeCommit","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"codedeploy-eu-west-3","service_name":"AWS CodeDeploy","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"dms-eu-west-3","service_name":"AWS Database Migration Service","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"docdb-eu-west-3","service_name":"Amazon DocumentDB","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"ecs-eu-west-3","service_name":"Amazon Elastic Container Service","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"eks-eu-west-3","service_name":"Amazon Elastic Kubernetes Service","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"elasticbeanstalk-eu-west-3","service_name":"AWS Elastic Beanstalk","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"elasticfilesystem-eu-west-3","service_name":"Amazon Elastic File System","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"elb-eu-west-3","service_name":"Amazon Elastic Load Balancing","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"emr-eu-west-3","service_name":"Amazon Elastic MapReduce","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"events-eu-west-3","service_name":"Amazon EventBridge","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"fargate-eu-west-3","service_name":"AWS Fargate","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"fsx-eu-west-3","service_name":"Amazon FSx","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"iotdevicedefender-eu-west-3","service_name":"AWS IoT Device Defender","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"ivs","service_name":"Amazon Interactive Video Service","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"kinesis-eu-west-3","service_name":"Amazon Kinesis Data Streams","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"kms-eu-west-3","service_name":"AWS Key Management Service","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"lambda-eu-west-3","service_name":"AWS Lambda","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"mq-eu-west-3","service_name":"Amazon MQ","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"natgateway-eu-west-3","service_name":"AWS NAT Gateway","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"networkaccessanalyzer-eu-west-3","service_name":"Network Access Analyzer","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"networkfirewall-eu-west-3","service_name":"AWS Network Firewall","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"paymentcryptography-eu-west-3","service_name":"AWS Payment Cryptography","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"pcs-eu-west-3","service_name":"AWS Parallel Computing Service","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"privatelink-eu-west-3","service_name":"AWS VPCE PrivateLink","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"redshift-eu-west-3","service_name":"Amazon Redshift","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"s3-eu-west-3","service_name":"Amazon Simple Storage Service","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"scheduler-eu-west-3","service_name":"Amazon EventBridge Scheduler","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"sns-eu-west-3","service_name":"Amazon Simple Notification Service","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"sqs-eu-west-3","service_name":"Amazon Simple Queue Service","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"state-eu-west-3","service_name":"AWS Step Functions","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"swf-eu-west-3","service_name":"Amazon Simple Workflow Service","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"trafficmirroring-eu-west-3","service_name":"Traffic Mirroring","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"transfer-eu-west-3","service_name":"AWS Transfer Family","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"transitgateway-eu-west-3","service_name":"AWS Transit Gateway","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"vpnvpc-eu-west-3","service_name":"AWS Site-to-Site VPN","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"workspaces-eu-west-3","service_name":"Amazon WorkSpaces","previous_status":"0","current_status":"1","timestamp":1777289237000},{"service":"acm-pca-eu-west-3","service_name":"AWS Private Certificate Authority","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"apigateway-eu-west-3","service_name":"Amazon API Gateway","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"appconfig-eu-west-3","service_name":"AWS AppConfig","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"appstream2-eu-west-3","service_name":"Amazon WorkSpaces Applications","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"appsync-eu-west-3","service_name":"AWS AppSync","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"athena-eu-west-3","service_name":"Amazon Athena","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"awsiot-eu-west-3","service_name":"AWS IoT Core","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"awsiotdevicemanagement-eu-west-3","service_name":"AWS IoT Device Management","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"bedrock-agentcore-eu-west-3","service_name":"Bedrock AgentCore","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"certificatemanager-eu-west-3","service_name":"AWS Certificate Manager","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"clientvpn-eu-west-3","service_name":"AWS Client VPN","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"cloud9-eu-west-3","service_name":"AWS Cloud9","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"cloudformation-eu-west-3","service_name":"AWS CloudFormation","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"cloudfront","service_name":"Amazon CloudFront","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"cloudshell-eu-west-3","service_name":"AWS CloudShell","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"cloudwan","service_name":"AWS Cloud WAN","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"codeartifact-eu-west-3","service_name":"AWS CodeArtifact","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"codecommit-eu-west-3","service_name":"AWS CodeCommit","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"codedeploy-eu-west-3","service_name":"AWS CodeDeploy","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"dms-eu-west-3","service_name":"AWS Database Migration Service","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"docdb-eu-west-3","service_name":"Amazon DocumentDB","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"ecs-eu-west-3","service_name":"Amazon Elastic Container Service","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"eks-eu-west-3","service_name":"Amazon Elastic Kubernetes Service","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"elasticbeanstalk-eu-west-3","service_name":"AWS Elastic Beanstalk","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"elasticfilesystem-eu-west-3","service_name":"Amazon Elastic File System","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"elb-eu-west-3","service_name":"Amazon Elastic Load Balancing","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"emr-eu-west-3","service_name":"Amazon Elastic MapReduce","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"events-eu-west-3","service_name":"Amazon EventBridge","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"fargate-eu-west-3","service_name":"AWS Fargate","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"fsx-eu-west-3","service_name":"Amazon FSx","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"iotdevicedefender-eu-west-3","service_name":"AWS IoT Device Defender","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"ivs","service_name":"Amazon Interactive Video Service","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"kinesis-eu-west-3","service_name":"Amazon Kinesis Data Streams","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"kms-eu-west-3","service_name":"AWS Key Management Service","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"lambda-eu-west-3","service_name":"AWS Lambda","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"mq-eu-west-3","service_name":"Amazon MQ","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"natgateway-eu-west-3","service_name":"AWS NAT Gateway","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"networkaccessanalyzer-eu-west-3","service_name":"Network Access Analyzer","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"networkfirewall-eu-west-3","service_name":"AWS Network Firewall","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"paymentcryptography-eu-west-3","service_name":"AWS Payment Cryptography","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"pcs-eu-west-3","service_name":"AWS Parallel Computing Service","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"privatelink-eu-west-3","service_name":"AWS VPCE PrivateLink","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"redshift-eu-west-3","service_name":"Amazon Redshift","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"s3-eu-west-3","service_name":"Amazon Simple Storage Service","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"scheduler-eu-west-3","service_name":"Amazon EventBridge Scheduler","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"sns-eu-west-3","service_name":"Amazon Simple Notification Service","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"sqs-eu-west-3","service_name":"Amazon Simple Queue Service","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"state-eu-west-3","service_name":"AWS Step Functions","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"swf-eu-west-3","service_name":"Amazon Simple Workflow Service","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"trafficmirroring-eu-west-3","service_name":"Traffic Mirroring","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"transfer-eu-west-3","service_name":"AWS Transfer Family","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"transitgateway-eu-west-3","service_name":"AWS Transit Gateway","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"vpnvpc-eu-west-3","service_name":"AWS Site-to-Site VPN","previous_status":"1","current_status":"0","timestamp":1777309806000},{"service":"workspaces-eu-west-3","service_name":"Amazon WorkSpaces","previous_status":"1","current_status":"0","timestamp":1777309806000}]}],"s3-eu-central-2":[{"summary":"[RESOLVED] Increased Error Rates","arn":"arn:aws:health:eu-central-2::event/S3/AWS_S3_OPERATIONAL_ISSUE/AWS_S3_OPERATIONAL_ISSUE_3A762_414220D2931","status":"2","date":"1772913192","event_log":[{"message":"We are investigating increased error rates in the EU-CENTRAL-2 Region.","summary":"Increased Error Rates","status":"2","timestamp":1772913192},{"message":"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. We will provide another update by 12:45 PM PST, or sooner if we have additional information to share.","summary":"Increased Error Rates","status":"2","timestamp":1772914629},{"message":"We are seeing early signs of recovery and continue to monitor and work toward full recovery.","summary":"Increased Error Rates","status":"1","timestamp":1772915319},{"message":"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.","summary":"[RESOLVED] Increased Error Rates","status":"0","timestamp":1772917444}],"impacted_services":{"airflow-eu-central-2":{"service_name":"Amazon Managed Workflows for Apache Airflow","current":"0","max":"1"},"appconfig-eu-central-2":{"service_name":"AWS AppConfig","current":"0","max":"1"},"appsync-eu-central-2":{"service_name":"AWS AppSync","current":"0","max":"1"},"athena-eu-central-2":{"service_name":"Amazon Athena","current":"0","max":"1"},"awswaf-eu-central-2":{"service_name":"AWS WAF","current":"0","max":"1"},"batch-eu-central-2":{"service_name":"AWS Batch","current":"0","max":"1"},"clientvpn-eu-central-2":{"service_name":"AWS Client VPN","current":"0","max":"1"},"cloudtrail-eu-central-2":{"service_name":"AWS CloudTrail","current":"0","max":"1"},"cloudwatch-eu-central-2":{"service_name":"Amazon CloudWatch","current":"0","max":"1"},"codedeploy-eu-central-2":{"service_name":"AWS CodeDeploy","current":"0","max":"1"},"datasync-eu-central-2":{"service_name":"AWS DataSync","current":"0","max":"1"},"ec2-eu-central-2":{"service_name":"Amazon Elastic Compute Cloud","current":"0","max":"1"},"ecr-eu-central-2":{"service_name":"Amazon Elastic Container Registry","current":"0","max":"1"},"ecs-eu-central-2":{"service_name":"Amazon Elastic Container Service","current":"0","max":"1"},"eks-eu-central-2":{"service_name":"Amazon Elastic Kubernetes Service","current":"0","max":"1"},"elasticsearch-eu-central-2":{"service_name":"Amazon OpenSearch Service","current":"0","max":"1"},"elb-eu-central-2":{"service_name":"Amazon Elastic Load Balancing","current":"0","max":"1"},"emr-eu-central-2":{"service_name":"Amazon Elastic MapReduce","current":"0","max":"1"},"fargate-eu-central-2":{"service_name":"AWS Fargate","current":"0","max":"1"},"firehose-eu-central-2":{"service_name":"Amazon Data Firehose","current":"0","max":"1"},"glacier-eu-central-2":{"service_name":"Amazon Glacier","current":"0","max":"1"},"glue-eu-central-2":{"service_name":"AWS Glue","current":"0","max":"1"},"kafka-eu-central-2":{"service_name":"Amazon Managed Streaming for Apache Kafka","current":"0","max":"1"},"kinesis-eu-central-2":{"service_name":"Amazon Kinesis Data Streams","current":"0","max":"1"},"kms-eu-central-2":{"service_name":"AWS Key Management Service","current":"0","max":"1"},"lambda-eu-central-2":{"service_name":"AWS Lambda","current":"0","max":"1"},"mgn-eu-central-2":{"service_name":"AWS Application Migration Service","current":"0","max":"1"},"privatelink-eu-central-2":{"service_name":"AWS VPCE PrivateLink","current":"0","max":"1"},"route53":{"service_name":"Amazon Route 53","current":"0","max":"1"},"sagemaker-eu-central-2":{"service_name":"Amazon SageMaker","current":"0","max":"1"},"servicediscovery-eu-central-2":{"service_name":"AWS Cloud Map","current":"0","max":"1"},"storagegateway-eu-central-2":{"service_name":"AWS Storage Gateway","current":"0","max":"1"},"transfer-eu-central-2":{"service_name":"AWS Transfer Family","current":"0","max":"1"},"transitgateway-eu-central-2":{"service_name":"AWS Transit Gateway","current":"0","max":"1"},"vpclattice-eu-central-2":{"service_name":"Amazon VPC Lattice","current":"0","max":"1"}}}],"directconnect-us-east-1":[{"summary":"[RESOLVED] AWS Direct Connect Connectivity Issues","arn":"arn:aws:health:us-east-1::event/DIRECTCONNECT/AWS_DIRECTCONNECT_OPERATIONAL_ISSUE/AWS_DIRECTCONNECT_OPERATIONAL_ISSUE_5A8A8_4B5C928EF8F","status":"1","date":"1771634280","event_log":[{"message":"We are investigating connectivity issues impacting AWS Direct Connect connectivity to the US-EAST-1 Region.","summary":"AWS Direct Connect connectivity loss","status":"1","timestamp":1771634280},{"message":"We can confirm connectivity issues for some customers using AWS Direct Connect in the US-EAST-1 Region. During this time, some customers may be missing previously advertised routes from their VPCs to their on-premise locations, resulting in connectivity issues from VPC resources in the N.Virginia (US-EAST-1) Region. We have identified the root cause and are actively working on multiple parallel paths to mitigate this issue. We will provide additional information within the next 30 minutes.","summary":"AWS Direct Connect connectivity loss","status":"1","timestamp":1771635540},{"message":"We are actively working on restoring routes that were no longer being advertised. This is resulting in connectivity issues for some customers from VPC resources in N.Virginia (US-EAST-1) Region to on-premise locations. We have identified the root cause and are actively trending towards recovery. While we work toward restoring all affected routes, some customers may see intermittent recovery while others may experience impact until we have fully mitigated the issue. We expect full recovery in approximately 90 minutes, but we are actively working on ways to increase the velocity of recovery. We will continue to provide updates as we have additional information to share, or within the next 45 minutes.","summary":"AWS Direct Connect connectivity issues","status":"1","timestamp":1771636955},{"message":"We are seeing early signs of recovery, and continue to work toward full recovery. ","summary":"AWS Direct Connect Connectivity Issues","status":"1","timestamp":1771637610},{"message":"We are seeing significant signs of recovery and continue to monitor to ensure full recovery. ","summary":"AWS Direct Connect Connectivity Issues","status":"1","timestamp":1771638632},{"message":"Between 11:41 AM PST and 5:45 PM PST, we experienced connectivity issues for some AWS Direct Connect Customers in the US-EAST-1 Region. While the issue was introduced at 11:41 AM PST, impact was limited until approximately 1:30 PM PST when impact grew as a result of a subsystem deployment. Our automated deployment takes approximately 12 hours so impact stayed limited to a subset of customers until we began observing broader impact at approximately 3:00 PM PST.  Engineers were engaged and began identifying the root cause. By 4:45 PM PST, we had identified the root cause and began mitigating affected routes. At 5:45 PM PST, all affected routes had been re-advertised and the issue was fully mitigated. During this time, customers may have experienced issues routing between their AWS VPC resources in N.Virginia (US-EAST-1) and their on-premise environments. We do not expect this issue to reoccur. The issue has been resolved and the service is operating normally. ","summary":"[RESOLVED] AWS Direct Connect Connectivity Issues","status":"0","timestamp":1771640002}]}],"ec2-eu-west-1":[{"summary":"[RESOLVED] Elevated latencies for network change propagation","arn":"arn:aws:health:eu-west-1::event/EC2/AWS_EC2_OPERATIONAL_ISSUE/AWS_EC2_OPERATIONAL_ISSUE_BB3D2_61B6325B9E6","status":"1","date":"1769620440","event_log":[{"message":"We are investigating elevated latencies for network change propagation in the EU-WEST-1 Region. This is resulting in impact to other services, such as timeouts when pulling images. We will provide you with further information shortly.","summary":"Elevated latencies for network change propagation","status":"1","timestamp":1769620440},{"message":"We can confirm elevated latencies for network change propagation in the EU-WEST-1 Region. This causes delays when attempting to connect to newly launched instances using their assigned public IPs, as well as delays in establishing new VPC Peering connections. Other AWS Services are also impacted by this issue and may be impacted by delayed or stuck workflows such as pulling container images. Engineers were automatically engaged and we are actively working on mitigating this issue. We plan to provide an update within the next 60 minutes.","summary":"Elevated latencies for network change propagation","status":"1","timestamp":1769621791},{"message":"We are seeing early signs of progressive recovery. We continue to work toward full recovery and will continue to provide updates as we work toward full mitigation. We recommend customers continue to retry failed requests. As recovery progresses, additional requests will succeed.","summary":"Elevated latencies for network change propagation","status":"1","timestamp":1769622440},{"message":"We continue to work toward fully mitigating the issue that is resulting in elevated latencies for network change propagation delays in the EU-WEST-1 Region. We have a high degree of confidence that our current mitigation efforts will fully mitigate the issue. Our current estimation is that these mitigations will complete within the next 60 to 120 minutes. We recommend customers continue to retry failed requests. We will provide additional information as recovery continues to progress.","summary":"Elevated latencies for network change propagation","status":"1","timestamp":1769625951},{"message":"We are seeing significant signs of recovery. We continue to work toward full resolution.","summary":"Elevated latencies for network change propagation","status":"1","timestamp":1769626261},{"message":"Between 7:08 AM and 10:48 AM PST, we experienced elevated latencies for network change propagation in the EU-WEST-1 Region. This was due to a delay in propagation of configuration updates on a sub-system which supports external and cross account connectivity. Customers experienced delays when attempting to connect to newly launched instances using their assigned public IPs, as well as delays in establishing new VPC Peering connections. Other AWS Services were also impacted by this issue and were impacted by delayed or stuck workflows such as pulling container images.\n\nEngineers were automatically engaged at 6:29 AM, prior to customer impact beginning. At 7:20 AM, root cause was identified. By 9:20 AM we began observing early signs of recovery. Our mitigation efforts completed at 10:43 AM and full recovery was observed at 10:48 AM. We recommend customers retry any failed requests. The issue has been resolved and all services are operating normally. ","summary":"[RESOLVED] Elevated latencies for network change propagation","status":"0","timestamp":1769628120}],"impacted_services":{"apigateway-eu-west-1":{"service_name":"Amazon API Gateway","current":"0","max":"1"},"athena-eu-west-1":{"service_name":"Amazon Athena","current":"0","max":"1"},"awswaf-eu-west-1":{"service_name":"AWS WAF","current":"0","max":"1"},"cognito-eu-west-1":{"service_name":"Amazon Cognito","current":"0","max":"1"},"deadline-eu-west-1":{"service_name":"AWS Deadline Cloud","current":"0","max":"1"},"dynamodb-eu-west-1":{"service_name":"Amazon DynamoDB","current":"0","max":"1"},"ecr-eu-west-1":{"service_name":"Amazon Elastic Container Registry","current":"0","max":"1"},"ecs-eu-west-1":{"service_name":"Amazon Elastic Container Service","current":"0","max":"1"},"eks-eu-west-1":{"service_name":"Amazon Elastic Kubernetes Service","current":"0","max":"1"},"elasticache-eu-west-1":{"service_name":"Amazon ElastiCache","current":"0","max":"1"},"elasticsearch-eu-west-1":{"service_name":"Amazon OpenSearch Service","current":"0","max":"1"},"elb-eu-west-1":{"service_name":"Amazon Elastic Load Balancing","current":"0","max":"1"},"elemental-eu-west-1":{"service_name":"AWS Elemental","current":"0","max":"1"},"emr-eu-west-1":{"service_name":"Amazon Elastic MapReduce","current":"0","max":"1"},"emrserverless-eu-west-1":{"service_name":"Amazon EMR Serverless","current":"0","max":"1"},"fargate-eu-west-1":{"service_name":"AWS Fargate","current":"0","max":"1"},"globalaccelerator":{"service_name":"AWS Global Accelerator","current":"0","max":"1"},"natgateway-eu-west-1":{"service_name":"AWS NAT Gateway","current":"0","max":"1"},"personalize-eu-west-1":{"service_name":"Amazon Personalize","current":"0","max":"1"},"rds-eu-west-1":{"service_name":"Amazon Relational Database Service","current":"0","max":"1"},"s3-eu-west-1":{"service_name":"Amazon Simple Storage Service","current":"0","max":"1"},"sagemaker-eu-west-1":{"service_name":"Amazon SageMaker","current":"0","max":"1"}}}],"multipleservices-us-east-1":[{"summary":"[RESOLVED] Increased Error Rates and Latencies","arn":"arn:aws:health:us-east-1::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_BA540_514A652BE1A","status":"3","date":"1760944260","event_log":[{"message":"We are investigating increased error rates and latencies for multiple AWS services in the US-EAST-1 Region. We will provide another update in the next 30-45 minutes.","summary":"Increased Error Rates and Latencies","status":"1","timestamp":1760944260},{"message":"We can confirm increased error rates and latencies for multiple AWS Services in the US-EAST-1 Region. This issue may also be affecting Case Creation through the AWS Support Center or the Support API. We are actively engaged and working to both mitigate the issue and understand root cause. We will provide an update in 45 minutes, or sooner if we have additional information to share. ","summary":"Increased Error Rates and Latencies","status":"2","timestamp":1760946669},{"message":"We can confirm significant error rates for requests made to the DynamoDB endpoint in the US-EAST-1 Region. This issue also affects other AWS Services in the US-EAST-1 Region as well. During this time, customers may be unable to create or update Support Cases. Engineers were immediately engaged and are actively working on both mitigating the issue, and fully understanding the root cause. We will continue to provide updates as we have more information to share, or by 2:00 AM. ","summary":"Increased Error Rates and Latencies","status":"3","timestamp":1760948801},{"message":"We have identified a potential root cause for error rates for the DynamoDB APIs in the US-EAST-1 Region. Based on our investigation, the issue appears to be related to DNS resolution of the DynamoDB API endpoint in US-EAST-1. We are working on multiple parallel paths to accelerate recovery. This issue also affects other AWS Services in the US-EAST-1 Region. Global services or features that rely on US-EAST-1 endpoints such as IAM updates and DynamoDB Global tables may also be experiencing issues. During this time, customers may be unable to create or update Support Cases. We recommend customers continue to retry any failed requests. We will continue to provide updates as we have more information to share, or by 2:45 AM. ","summary":"Increased Error Rates and Latencies","status":"3","timestamp":1760950861},{"message":"We have applied initial mitigations and we are observing early signs of recovery for some impacted AWS Services. During this time, requests may continue to fail as we work toward full resolution. We recommend customers retry failed requests. While requests begin succeeding, there may be additional latency and some services will have a backlog of work to work through, which may take additional time to fully process. We will continue to provide updates as we have more information to share, or by 3:15 AM.","summary":"Increased Error Rates and Latencies","status":"3","timestamp":1760952168},{"message":"We are seeing significant signs of recovery. Most requests should now be succeeding. We continue to work through a backlog of queued requests. We will continue to provide additional information. ","summary":"Increased Error Rates and Latencies","status":"2","timestamp":1760952453},{"message":"We continue to observe recovery across most of the affected AWS Services. We can confirm global services and features that rely on US-EAST-1 have also recovered. We continue to work towards full resolution and will provide updates as we have more information to share. ","summary":"Increased Error Rates and Latencies","status":"1","timestamp":1760954629},{"message":"The underlying DNS issue has been fully mitigated, and most AWS Service operations are succeeding normally now. Some requests may be throttled while we work toward full resolution. Additionally, some services are continuing to work through a backlog of events such as Cloudtrail and Lambda. While most operations are recovered, requests to launch new EC2 instances (or services that launch EC2 instances such as ECS) in the US-EAST-1 Region are still experiencing increased error rates. We continue to work toward full resolution. If you are still experiencing an issue resolving the DynamoDB service endpoints in US-EAST-1, we recommend flushing your DNS caches. We will provide an update by 4:15 AM, or sooner if we have additional information to share.","summary":"Increased Error Rates and Latencies","status":"1","timestamp":1760956537},{"message":"We are continuing to work towards full recovery for EC2 launch errors, which may manifest as an Insufficient Capacity Error. Additionally, we continue to work toward mitigation for elevated polling delays for Lambda, specifically for Lambda Event Source Mappings for SQS. We will provide an update by 5:00 AM PDT.","summary":"Increased Error Rates and Latencies","status":"1","timestamp":1760958480},{"message":"We continue to work to fully restore new EC2 launches in US-EAST-1. We recommend EC2 Instance launches that are not targeted to a specific Availability Zone (AZ) so that EC2 has flexibility in selecting the appropriate AZ. The impairment in new EC2 launches also affects services such as RDS, ECS, and Glue. We also recommend that Auto Scaling Groups are configured to use multiple AZs so that Auto Scaling can manage EC2 instance launches automatically. \n\nWe are pursuing further mitigation steps to recover Lambda’s polling delays for Event Source Mappings for SQS. AWS features that depend on Lambda’s SQS polling capabilities such as Organization policy updates are also experiencing elevated processing times. We will provide an update by 5:30 AM PDT. ","summary":"Increased Error Rates and Latencies","status":"1","timestamp":1760960925},{"message":"We confirm that we have now recovered processing of SQS queues via Lambda Event Source Mappings. We are now working through processing the backlog of SQS messages in Lambda queues. ","summary":"Increased Error Rates and Latencies","status":"1","timestamp":1760962238},{"message":"We are making progress on resolving the issue with new EC2 instance launches in the US-EAST-1 Region and are now able to successfully launch new instances in some Availability Zones. We are applying similar mitigations to the remaining impacted Availability Zones to restore new instance launches. As we continue to make progress, customers will see an increasing number of successful new EC2 launches. We continue to recommend that customers launch new EC2 Instance launches that are not targeted to a specific Availability Zone (AZ) so that EC2 has flexibility in selecting the appropriate AZ. \n\nWe also wanted to share that we are continuing to successfully process the backlog of events for both EventBridge and Cloudtrail. New events published to these services are being delivered normally and are not experiencing elevated delivery latencies. \n\nWe will provide an update by 6:30 AM PDT or sooner if we have additional information to share.","summary":"Increased Error Rates and Latencies","status":"1","timestamp":1760964535},{"message":"We have applied multiple mitigations across multiple Availability Zones (AZs) in US-EAST-1 and are still experiencing elevated errors for new EC2 instance launches. We are rate limiting new instance launches to aid recovery. We will provide an update at 7:30 AM PDT or sooner if we have additional information. ","summary":"Increased Error Rates and Latencies","status":"1","timestamp":1760967726},{"message":"We can confirm significant API errors and connectivity issues across multiple services in the US-EAST-1 Region. We are investigating and will provide further update in 30 minutes or soon if we have additional information.","summary":"Increased Error Rates and Latencies","status":"2","timestamp":1760969640},{"message":"We have confirmed multiple AWS services experienced network connectivity issues in the US-EAST-1 Region. We are seeing early signs of recovery for the connectivity issues and are continuing to investigate the root cause. ","summary":"Increased Error Rates and Latencies","status":"2","timestamp":1760970579},{"message":"We continue to investigate the root cause for the network connectivity issues that are impacting AWS services such as DynamoDB, SQS, and Amazon Connect in the US-EAST-1 Region. We have identified that the issue originated from within the EC2 internal network. We continue to investigate and identify mitigations. ","summary":"Increased Error Rates and Latencies","status":"2","timestamp":1760972684},{"message":"We have narrowed down the source of the network connectivity issues that impacted AWS Services. The root cause is an underlying internal subsystem responsible for monitoring the health of our network load balancers. We are throttling requests for new EC2 instance launches to aid recovery and actively working on mitigations.","summary":"Increased Error Rates and Latencies","status":"2","timestamp":1760974980},{"message":"We have taken additional mitigation steps to aid the recovery of the underlying internal subsystem responsible for monitoring the health of our network load balancers and are now seeing connectivity and API recovery for AWS services. We have also identified and are applying next steps to mitigate throttling of new EC2 instance launches. We will provide an update by 10:00 AM PDT.","summary":"Increased Error Rates and Latencies","status":"2","timestamp":1760976827},{"message":"We continue to apply mitigation steps for network load balancer health and recovering connectivity for most AWS services. Lambda is experiencing function invocation errors because an internal subsystem was impacted by the network load balancer health checks. We are taking steps to recover this internal Lambda system. For EC2 launch instance failures, we are in the process of validating a fix and will deploy to the first AZ as soon as we have confidence we can do so safely.  We will provide an update by 10:45 AM PDT.","summary":"Increased Error Rates and Latencies","status":"2","timestamp":1760979785},{"message":"Our mitigations to resolve launch failures for new EC2 instances are progressing and the internal subsystems of EC2 are now showing early signs of recovering in a few Availability Zones (AZs) in the US-EAST-1 Region. We are applying mitigations to the remaining AZs at which point we expect launch errors and network connectivity issues to subside. We will provide an update by 11:30 AM PDT.","summary":"Increased Error Rates and Latencies","status":"2","timestamp":1760981880},{"message":"Our mitigations to resolve launch failures for new EC2 instances continue to progress and we are seeing increased launches of new EC2 instances and decreasing networking connectivity issues in the US-EAST-1 Region. We are also experiencing significant improvements to Lambda invocation errors, especially when creating new execution environments (including for Lambda@Edge invocations). We will provide an update by 12:00 PM PDT. ","summary":"Increased Error Rates and Latencies","status":"2","timestamp":1760984548},{"message":"We continue to observe recovery across all AWS services, and instance launches are succeeding across multiple Availability Zones in the US-EAST-1 Regions. For Lambda, customers may face intermittent function errors for functions making network requests to other services or systems as we work to address residual network connectivity issues. To recover Lambda’s invocation errors, we slowed down the rate of SQS polling via Lambda Event Source Mappings. We are now increasing the rate of SQS polling as we experience more successful invocations and reduced function errors. We will provide another update by 1:00 PM PDT. ","summary":"Increased Error Rates and Latencies","status":"1","timestamp":1760987706},{"message":"Service recovery across all AWS services continues to improve. We continue to reduce throttles for new EC2 Instance launches in the US-EAST-1 Region that were put in place to help mitigate impact. Lambda invocation errors have fully recovered and function errors continue to improve. We have scaled up the rate of polling SQS queues via Lambda Event Source Mappings to pre-event levels. We will provide another update by 1:45 PM PDT. ","summary":"Increased Error Rates and Latencies","status":"1","timestamp":1760990582},{"message":"We have continued to reduce throttles for EC2 instance launches in the US-EAST-1 Region and we continue to make progress toward pre-event levels in all Availability Zones (AZs). AWS services such as ECS and Glue, which rely on EC2 instance launches will recover as the successful instance launch rate improves. We see full recovery for Lambda invocations and are working through the backlog of queued events which we expect to be full processed in approximately in the next two hours. We will provide another update by 2:30 PM PDT. ","summary":"Increased Error Rates and Latencies","status":"1","timestamp":1760993553},{"message":"We have restored EC2 instance launch throttles to pre-event levels and EC2 launch failures have recovered across all Availability Zones in the US-EAST-1 Regions. AWS services which rely on EC2 instance launches such as Redshift are working through their backlog of EC2 instance launches successfully and we anticipate full recovery of the backlog over the next two hours. We can confirm that Connect is handling new voice and chat sessions normally. There is a backlog of analytics and reporting data that we must process and anticipate that we will have worked through the backlog over the next two hours. We will provide an update by 3:30 PM PDT.","summary":"Increased Error Rates and Latencies","status":"1","timestamp":1760996894},{"message":"Between 11:49 PM  PDT on October 19 and 2:24 AM PDT on October 20, we experienced increased error rates and latencies for AWS Services in the US-EAST-1 Region. Additionally, services or features that rely on US-EAST-1 endpoints such as IAM and DynamoDB Global Tables also experienced issues during this time. At 12:26 AM on October 20, we identified the trigger of the event as DNS resolution issues for the regional DynamoDB service endpoints. After resolving the DynamoDB DNS issue at 2:24 AM, services began recovering but we had a subsequent impairment in the internal subsystem of EC2 that is responsible for launching EC2 instances due to its dependency on DynamoDB. As we continued to work through EC2 instance launch impairments, Network Load Balancer health checks also became impaired, resulting in network connectivity issues in multiple services such as Lambda, DynamoDB, and CloudWatch. We recovered the Network Load Balancer health checks at 9:38 AM. As part of the recovery effort, we temporarily throttled some operations such as EC2 instance launches, processing of SQS queues via Lambda Event Source Mappings, and asynchronous Lambda invocations. Over time we reduced throttling of operations and worked in parallel to resolve network connectivity issues until the services fully recovered. By 3:01 PM, all AWS services returned to normal operations. Some services such as AWS Config, Redshift, and Connect continue to have a backlog of messages that they will finish processing over the next few hours. Additional details regarding this event are available <a href=\"https://aws.amazon.com/message/101925/\">here.</a>","summary":"[RESOLVED] Increased Error Rates and Latencies","status":"0","timestamp":1761000780}],"impacted_services":{"account":{"service_name":"AWS Account Management","current":"0","max":"1"},"acm-pca-us-east-1":{"service_name":"AWS Private Certificate Authority","current":"0","max":"1"},"kinesisvideo-us-east-1":{"service_name":"Amazon Kinesis Video Streams","current":"0","max":"1"},"airflow-us-east-1":{"service_name":"Amazon Managed Workflows for Apache Airflow","current":"0","max":"1"},"amplify-us-east-1":{"service_name":"AWS Amplify","current":"0","max":"1"},"apigateway-us-east-1":{"service_name":"Amazon API Gateway","current":"0","max":"1"},"appconfig-us-east-1":{"service_name":"AWS AppConfig","current":"0","max":"1"},"appflow-us-east-1":{"service_name":"Amazon AppFlow","current":"0","max":"1"},"applicationinsights-us-east-1":{"service_name":"Amazon CloudWatch Application Insights","current":"0","max":"1"},"appstream2-us-east-1":{"service_name":"Amazon WorkSpaces Applications","current":"0","max":"1"},"appsync-us-east-1":{"service_name":"AWS AppSync","current":"0","max":"1"},"appwizard-us-east-1":{"service_name":"AWS Launch Wizard","current":"0","max":"1"},"aps-us-east-1":{"service_name":"Amazon Managed Service for Prometheus","current":"0","max":"1"},"athena-us-east-1":{"service_name":"Amazon Athena","current":"0","max":"1"},"aws-partner-central":{"service_name":"AWS Partner Central","current":"0","max":"1"},"awsgreengrass-us-east-1":{"service_name":"AWS IoT Greengrass","current":"0","max":"1"},"awsiot-us-east-1":{"service_name":"AWS IoT Core","current":"0","max":"1"},"awsiotdevicemanagement-us-east-1":{"service_name":"AWS IoT Device Management","current":"0","max":"1"},"awswaf-us-east-1":{"service_name":"AWS WAF","current":"0","max":"1"},"b2bi-us-east-1":{"service_name":"AWS B2B Data Interchange","current":"0","max":"1"},"batch-us-east-1":{"service_name":"AWS Batch","current":"0","max":"1"},"bedrock-us-east-1":{"service_name":"Amazon Bedrock","current":"0","max":"1"},"billingconsole":{"service_name":"AWS Billing Console","current":"0","max":"1"},"chime":{"service_name":"Amazon Chime","current":"0","max":"1"},"clientvpn-us-east-1":{"service_name":"AWS Client VPN","current":"0","max":"1"},"cloudformation-us-east-1":{"service_name":"AWS CloudFormation","current":"0","max":"1"},"cloudfront":{"service_name":"Amazon CloudFront","current":"0","max":"1"},"cloudhsm-us-east-1":{"service_name":"AWS CloudHSM","current":"0","max":"1"},"cloudtrail-us-east-1":{"service_name":"AWS CloudTrail","current":"0","max":"1"},"cloudwan":{"service_name":"AWS Cloud WAN","current":"0","max":"1"},"cloudwatch-us-east-1":{"service_name":"Amazon CloudWatch","current":"0","max":"1"},"codebuild-us-east-1":{"service_name":"AWS CodeBuild","current":"0","max":"1"},"cognito-us-east-1":{"service_name":"Amazon Cognito","current":"0","max":"1"},"comprehend-us-east-1":{"service_name":"Amazon Comprehend","current":"0","max":"1"},"config-us-east-1":{"service_name":"AWS Config","current":"0","max":"1"},"connect-us-east-1":{"service_name":"Amazon Connect","current":"0","max":"1"},"controltower-us-east-1":{"service_name":"AWS Control Tower","current":"0","max":"1"},"datasync-us-east-1":{"service_name":"AWS DataSync","current":"0","max":"1"},"datazone-us-east-1":{"service_name":"Amazon DataZone","current":"0","max":"1"},"deadline-us-east-1":{"service_name":"AWS Deadline Cloud","current":"0","max":"1"},"directconnect-us-east-1":{"service_name":"AWS Direct Connect","current":"0","max":"1"},"directoryservice-us-east-1":{"service_name":"AWS Directory Service","current":"0","max":"1"},"dms-us-east-1":{"service_name":"AWS Database Migration Service","current":"0","max":"1"},"docdb-us-east-1":{"service_name":"Amazon DocumentDB","current":"0","max":"1"},"drs-us-east-1":{"service_name":"AWS Elastic Disaster Recovery","current":"0","max":"1"},"dsql-us-east-1":{"service_name":"Amazon Aurora DSQL Service","current":"0","max":"1"},"dynamodb-us-east-1":{"service_name":"Amazon DynamoDB","current":"0","max":"3"},"ec2-us-east-1":{"service_name":"Amazon Elastic Compute Cloud","current":"0","max":"1"},"ec2systemsmanager-us-east-1":{"service_name":"AWS Systems Manager","current":"0","max":"1"},"ecr-us-east-1":{"service_name":"Amazon Elastic Container Registry","current":"0","max":"1"},"ecs-us-east-1":{"service_name":"Amazon Elastic Container Service","current":"0","max":"1"},"eks-us-east-1":{"service_name":"Amazon Elastic Kubernetes Service","current":"0","max":"1"},"elasticache-us-east-1":{"service_name":"Amazon ElastiCache","current":"0","max":"1"},"elasticbeanstalk-us-east-1":{"service_name":"AWS Elastic Beanstalk","current":"0","max":"1"},"elasticfilesystem-us-east-1":{"service_name":"Amazon Elastic File System","current":"0","max":"1"},"elasticsearch-us-east-1":{"service_name":"Amazon OpenSearch Service","current":"0","max":"1"},"elb-us-east-1":{"service_name":"Amazon Elastic Load Balancing","current":"0","max":"1"},"elemental-us-east-1":{"service_name":"AWS Elemental","current":"0","max":"1"},"emr-us-east-1":{"service_name":"Amazon Elastic MapReduce","current":"0","max":"1"},"emrserverless-us-east-1":{"service_name":"Amazon EMR Serverless","current":"0","max":"1"},"endusermessaging-us-east-1":{"service_name":"AWS End User Messaging","current":"0","max":"1"},"events-us-east-1":{"service_name":"Amazon EventBridge","current":"0","max":"1"},"firehose-us-east-1":{"service_name":"Amazon Kinesis Firehose","current":"0","max":"1"},"fms-us-east-1":{"service_name":"AWS Firewall Manager","current":"0","max":"1"},"fsx-us-east-1":{"service_name":"Amazon FSx","current":"0","max":"1"},"gamelift-us-east-1":{"service_name":"Amazon GameLift Servers","current":"0","max":"1"},"gameliftstreams":{"service_name":"Amazon GameLift Streams","current":"0","max":"1"},"globalaccelerator":{"service_name":"AWS Global Accelerator","current":"0","max":"1"},"glue-us-east-1":{"service_name":"AWS Glue","current":"0","max":"1"},"grafana-us-east-1":{"service_name":"Amazon Managed Grafana","current":"0","max":"1"},"guardduty-us-east-1":{"service_name":"Amazon GuardDuty","current":"0","max":"1"},"healthimaging-us-east-1":{"service_name":"AWS HealthImaging","current":"0","max":"1"},"healthlake-us-east-1":{"service_name":"AWS HealthLake","current":"0","max":"1"},"iam":{"service_name":"AWS Identity and Access Management","current":"0","max":"1"},"iamidentitycenter-us-east-1":{"service_name":"AWS IAM Identity Center","current":"0","max":"1"},"imagebuilder-us-east-1":{"service_name":"EC2 Image Builder","current":"0","max":"1"},"security-ir-us-east-1":{"service_name":"AWS Security Incident Response","current":"0","max":"1"},"iotanalytics-us-east-1":{"service_name":"AWS IoT Analytics","current":"0","max":"1"},"iotevents-us-east-1":{"service_name":"AWS IoT Events","current":"0","max":"1"},"iotfleetwise-us-east-1":{"service_name":"AWS IoT FleetWise","current":"0","max":"1"},"iotsitewise-us-east-1":{"service_name":"AWS IoT SiteWise","current":"0","max":"1"},"ipam-us-east-1":{"service_name":"Amazon VPC IP Address Manager","current":"0","max":"1"},"ivs-us-east-1":{"service_name":"Amazon Interactive Video Service","current":"0","max":"1"},"kafka-us-east-1":{"service_name":"Amazon Managed Streaming for Apache Kafka","current":"0","max":"1"},"kendra-us-east-1":{"service_name":"Amazon Kendra","current":"0","max":"1"},"kinesis-us-east-1":{"service_name":"Amazon Kinesis Data Streams","current":"0","max":"1"},"kinesisanalytics-us-east-1":{"service_name":"Amazon Managed Service for Apache Flink","current":"0","max":"1"},"lakeformation-us-east-1":{"service_name":"AWS Lake Formation","current":"0","max":"1"},"lambda-us-east-1":{"service_name":"AWS Lambda","current":"0","max":"1"},"licensemanager-us-east-1":{"service_name":"AWS License Manager","current":"0","max":"1"},"locationservice-us-east-1":{"service_name":"Amazon Location Service","current":"0","max":"1"},"managedssh-us-east-1":{"service_name":"Amazon EC2 Instance Connect","current":"0","max":"1"},"mgn-us-east-1":{"service_name":"AWS Application Migration Service","current":"0","max":"1"},"mq-us-east-1":{"service_name":"Amazon MQ","current":"0","max":"1"},"natgateway-us-east-1":{"service_name":"AWS NAT Gateway","current":"0","max":"1"},"neptune-db-us-east-1":{"service_name":"Amazon Neptune","current":"0","max":"1"},"networkfirewall-us-east-1":{"service_name":"AWS Network Firewall","current":"0","max":"1"},"omics-us-east-1":{"service_name":"AWS HealthOmics","current":"0","max":"1"},"organizations":{"service_name":"AWS Organizations","current":"0","max":"1"},"outposts-us-east-1":{"service_name":"AWS Outposts","current":"0","max":"1"},"paymentcryptography-us-east-1":{"service_name":"AWS Payment Cryptography","current":"0","max":"1"},"pcs-us-east-1":{"service_name":"AWS Parallel Computing Service","current":"0","max":"1"},"pinpoint-us-east-1":{"service_name":"Amazon Pinpoint","current":"0","max":"1"},"polly-us-east-1":{"service_name":"Amazon Polly","current":"0","max":"1"},"privatelink-us-east-1":{"service_name":"AWS VPCE PrivateLink","current":"0","max":"1"},"evs-us-east-1":{"service_name":"AWS Elastic VMWare Service","current":"0","max":"1"},"qbusiness-us-east-1":{"service_name":"Amazon Q Business","current":"0","max":"1"},"quicksight-us-east-1":{"service_name":"Amazon Quick Suite","current":"0","max":"1"},"rds-us-east-1":{"service_name":"Amazon Relational Database Service","current":"0","max":"1"},"redshift-us-east-1":{"service_name":"Amazon Redshift","current":"0","max":"1"},"rekognition-us-east-1":{"service_name":"Amazon Rekognition","current":"0","max":"1"},"resourcegroups":{"service_name":"AWS Resource Groups","current":"0","max":"1"},"s3-us-east-1":{"service_name":"Amazon Simple Storage Service","current":"0","max":"1"},"sagemaker-us-east-1":{"service_name":"Amazon SageMaker","current":"0","max":"1"},"scheduler-us-east-1":{"service_name":"Amazon EventBridge Scheduler","current":"0","max":"1"},"secretsmanager-us-east-1":{"service_name":"AWS Secrets Manager","current":"0","max":"1"},"securitylake-us-east-1":{"service_name":"Amazon Security Lake","current":"0","max":"1"},"ses-us-east-1":{"service_name":"Amazon Simple Email Service","current":"0","max":"1"},"sns-us-east-1":{"service_name":"Amazon Simple Notification Service","current":"0","max":"1"},"sqs-us-east-1":{"service_name":"Amazon Simple Queue Service","current":"0","max":"1"},"ssmsap-us-east-1":{"service_name":"AWS Systems Manager for SAP","current":"0","max":"1"},"state-us-east-1":{"service_name":"AWS Step Functions","current":"0","max":"1"},"storagegateway-us-east-1":{"service_name":"AWS Storage Gateway","current":"0","max":"1"},"sts-us-east-1":{"service_name":"AWS Security Token Service","current":"0","max":"1"},"supportapi":{"service_name":"AWS Support API","current":"0","max":"1"},"supportcenter":{"service_name":"AWS Support Center","current":"0","max":"1"},"swf-us-east-1":{"service_name":"Amazon Simple Workflow Service","current":"0","max":"1"},"textract-us-east-1":{"service_name":"Amazon Textract","current":"0","max":"1"},"thinclient-us-east-1":{"service_name":"Amazon WorkSpaces Thin Client","current":"0","max":"1"},"timestream-us-east-1":{"service_name":"Amazon Timestream","current":"0","max":"1"},"trafficmirroring-us-east-1":{"service_name":"Traffic Mirroring","current":"0","max":"1"},"transcribe-us-east-1":{"service_name":"Amazon Transcribe","current":"0","max":"1"},"transfer-us-east-1":{"service_name":"AWS Transfer Family","current":"0","max":"1"},"transform-us-east-1":{"service_name":"AWS Transform","current":"0","max":"1"},"transitgateway-us-east-1":{"service_name":"AWS Transit Gateway","current":"0","max":"1"},"translate-us-east-1":{"service_name":"Amazon Translate","current":"0","max":"1"},"verifiedaccess-us-east-1":{"service_name":"AWS Verified Access","current":"0","max":"1"},"vpclattice-us-east-1":{"service_name":"Amazon VPC Lattice","current":"0","max":"1"},"vpnvpc-us-east-1":{"service_name":"AWS Site-to-Site VPN","current":"0","max":"1"},"wickr-us-east-1":{"service_name":"AWS Wickr","current":"0","max":"1"},"workmail-us-east-1":{"service_name":"Amazon WorkMail","current":"0","max":"1"},"workspaces-us-east-1":{"service_name":"Amazon WorkSpaces","current":"0","max":"1"}}},{"summary":"[RESOLVED] Increased Error Rates and Latencies","arn":"arn:aws:health:us-east-1::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_30422_580368C1278","status":"1","date":"1761691002","event_log":[{"message":"Earlier today some EC2 launches within the use1-az2 Availability Zone (AZ) experienced increased latencies for EC2 instance launches. We communicated with affected customers via the AWS Personal Health Dashboard shortly after the issue began. This issue has been resolved and EC2 instance launches are operating normally, however some request throttles are currently in place for the use1-az2 Availability Zone (AZ), which are gradually being removed. Customers may experience “request limit exceeded” in this AZ while these throttles are in place; retries should resolve the issue.\n\nCurrently we are investigating task launch failure rates for ECS tasks for both EC2 and Fargate for a subset of customers in the US-EAST-1 Region. Customers may also see their container instances disconnect from ECS which can cause tasks to stop in some circumstances. ECS operates cells in the Region and a small number of these cells are currently experiencing elevated error rates launching new tasks and existing tasks may stop unexpectedly. When creating an ECS cluster to run tasks, the cluster is assigned to a specific cell. Customers with a cluster in impacted cells are seeing impact across all Availability Zones in the Region. At this time, we recommend customers who can, create new clusters to ensure that the cluster is assigned to a healthy cell. Existing clusters in the remaining healthy cells are not affected. We have identified actions to restore the impacted cells to full service but do not have an estimated time of recovery. Customers who use EMR Serverless are also affected by this issue. We will provide an update by 4:15 PM PDT or as soon as more information becomes available.","summary":"Increased Error Rates and Latencies","status":"1","timestamp":1761691002},{"message":"For EMR Serverless, some jobs continue to experience increased execution delays or failures. For EC2, we continue to throttle some requests (new instance launches and other networking related mutating API calls) in a single Availability Zone (use1-az2) in the US-EAST-1 Region. These throttles will remain until we have fully mitigated all issues, and have a high degree of confidence that the issue will not reoccur. Existing instances are unaffected by this issue. For ECS, we are continuing to make progress toward recovering the impacted ECS cells, but this has not yet resulted in customer visible improvements. Customers that are experiencing task launch errors and latencies in the impacted ECS cells are not yet observing improvement. While we do not have a firm ETA, we expect full recovery is 2-3 hours away. As we make additional progress, success rates for affected operations will improve. We will continue to provide updates as we have additional information available, or by 5:30 PM.","summary":"Increased Error Rates and Latencies","status":"1","timestamp":1761694317},{"message":"We want to provide an update on EMR Serverless. EMR Serverless maintains a warm pool of ECS clusters to support customer requests, and some of these clusters are operating in the impacted ECS cells. In order to reduce EMR Serverless error rates, we are actively working on refreshing these warm pools with healthy clusters. For ECS, we continue to make progress on recovering impacted ECS cells, but progress is not visible externally. ECS has stopped new launches and tasks on the affected clusters. Some services (such as Glue) are observing recovery for error rates, but may still be experiencing increased latency. Our current best estimate of an ETA is 2-3 hours away. As we make additional progress, success rates for affected operations will improve. We will continue to provide updates as we have additional information available, or by 6:30 PM.","summary":"Increased Error Rates and Latencies","status":"1","timestamp":1761697898},{"message":"We continue to make additional progress towards ongoing mitigation efforts. While we have not fully recovered, we can confirm we are seeing positive signs of improvement for ECS clusters task launches on the impacted cells in the US-EAST-1 Region. For customers who need immediate recovery, we recommend recreating impacted ECS Clusters using a different identifier for clusterName. We continue to work toward full recovery.  For EKS, impact is limited to Fargate launches only. \n\nFor MWAA environments that are stuck in an unhealthy state, or that are impaired, we recommend customers <a href=\"https://docs.aws.amazon.com/mwaa/latest/userguide/update-environment.html#update-environment-resources\">perform an update to the environment without changing the current configuration</a>.\n\nFor EMR serverless, we have made substantial progress to refresh the warm pool with healthy clusters and continue to work toward full recovery. Once we have fully refreshed these warm pools we will provide additional guidance for required action to mitigate impact. \n\nOur current best estimate of an ETA to full recovery is an additional 2-4 hours away. As we make additional progress, success rates for affected operations will improve. We will continue to provide updates as we have additional information available, or by 7:45 PM.","summary":"Increased Error Rates and Latencies","status":"1","timestamp":1761702600},{"message":"We have made additional progress. For EMR Serverless, we have completed refreshing the warm pool with healthy clusters. We recommend customers restart their existing applications. We are also observing ECS task launches are beginning to succeed. While we work toward full resolution of the underlying issue, some requests will be throttled. Our current best estimate of an ETA to full recovery is an additional 1-2 hours away. As we make additional progress, success rates for affected operations are continuing to improve. We will continue to provide updates as we have additional information available, or by 9:05 PM.","summary":"Increased Error Rates and Latencies","status":"1","timestamp":1761707280},{"message":"We are seeing significant signs of recovery and continue to work toward full resolution.","summary":"Increased Error Rates and Latencies","status":"1","timestamp":1761710052},{"message":"We are observing significant recovery for services impacted by ECS. For ECS itself, we have recovered two of the three impacted cells and continue to work towards recovering the remaining cell. We have lifted throttles for the two recovered cells but throttling remains in effect for the third cell. The vast majority of customer applications should be recovered. We will continue to provide updates as we have additional information available, or by 11:00 PM. ","summary":"Increased Error Rates and Latencies","status":"1","timestamp":1761713565},{"message":"Between 9:00 AM and 10:43 PM PDT, we experienced increased latencies for EC2 instance launches within the use1-az2 Availability Zone (AZ) in the US-EAST-1 Region. In addition we experienced increased ECS task and pod launch failure rates. This impacted services that depend on ECS, including Fargate, EMR Serverless, MWAA, CodeBuild, EKS, Glue, AppRunner, DataSync, MWAA and AWS Batch. As part of the recovery effort, we temporarily throttled ECS operations in three impacted cells. At 10:43 PM, we had fully mitigated the issue. The issue has been resolved and the service is operating normally.","summary":"[RESOLVED] Increased Error Rates and Latencies","status":"0","timestamp":1761717423}],"impacted_services":{"airflow-us-east-1":{"service_name":"Amazon Managed Workflows for Apache Airflow","current":"0","max":"1"},"apprunner-us-east-1":{"service_name":"AWS App Runner","current":"0","max":"1"},"batch-us-east-1":{"service_name":"AWS Batch","current":"0","max":"1"},"codebuild-us-east-1":{"service_name":"AWS CodeBuild","current":"0","max":"1"},"datasync-us-east-1":{"service_name":"AWS DataSync","current":"0","max":"1"},"ec2-us-east-1":{"service_name":"Amazon Elastic Compute Cloud","current":"0","max":"1"},"ecs-us-east-1":{"service_name":"Amazon Elastic Container Service","current":"0","max":"1"},"eks-us-east-1":{"service_name":"Amazon Elastic Kubernetes Service","current":"0","max":"1"},"emrserverless-us-east-1":{"service_name":"Amazon EMR Serverless","current":"0","max":"1"},"fargate-us-east-1":{"service_name":"AWS Fargate","current":"0","max":"1"},"glue-us-east-1":{"service_name":"AWS Glue","current":"0","max":"1"}}}],"iam":[{"summary":"[RESOLVED] Increased Error Rates and Latencies","arn":"arn:aws:health:global::event/IAM/AWS_IAM_OPERATIONAL_ISSUE/AWS_IAM_OPERATIONAL_ISSUE_38AEE_C340609D4FD","status":"1","date":"1758943527","event_log":[{"message":"We are investigating increased error rates and latencies for the IAM APIs.","summary":"Increased Error Rates and Latencies","status":"1","timestamp":1758943527},{"message":"Between 7:59 PM and 8:32 PM PDT we experienced increased error rates and latencies for IAM API requests. Engineers were engaged at 8:02 PM and immediately began working on both mitigation and identification of root cause. Mitigations were applied by 8:28 PM and full recovery was observed by 8:32 PM. Authentication and authorization based on existing users, credentials, roles, and policies were not impacted during this time. Other AWS Services were also affected during this time. We do not expect this issue to reoccur. We recommend customers retry failed requests. The issue has been resolved and all AWS services are operating normally.","summary":"[RESOLVED] Increased Error Rates and Latencies","status":"0","timestamp":1758945492}]}],"sqs-eu-north-1":[{"summary":"[RESOLVED] SQS Increased API Error Rates","arn":"arn:aws:health:eu-north-1::event/SQS/AWS_SQS_OPERATIONAL_ISSUE/AWS_SQS_OPERATIONAL_ISSUE_828FE_F0D185B279D","status":"1","date":"1758837397","event_log":[{"message":"We are investigating increased API error rates &amp; latencies for SQS requests in the EU-NORTH-1 Region.","summary":"SQS Increased API Error Rates ","status":"1","timestamp":1758837397},{"message":"Beginning at 1:25 PM PDT we began experiencing increased API error rates &amp; latencies for SQS requests in the EU-NORTH-1 Region. Engineers were automatically engaged and immediately began investigating. We are actively working on mitigating this issue. In parallel are working to identify the root cause. This issue is impacting SQS RecieveMessage API for queues that are configured using Server Side Encryption. This issue is also affecting some APIs and workflows for other AWS Services. We will provide another update by 4:00 PM.","summary":"SQS Increased API Error Rates","status":"1","timestamp":1758839147},{"message":" We continue to investigate increased API error rates &amp; latencies for SQS ReceiveMessage APIs configured with Server Side Encryption in the EU-NORTH-1 Region. We are actively working on multiple paths to mitigate and root-cause the issue. While we have not yet seen recovery on SQS ReceiveMessage API Requests, some AWS Services have seen full recovery for their impacted operations and workflows. We continue to work toward full recovery and will provide an update by 4:45 PM.","summary":"SQS Increased API Error Rates","status":"1","timestamp":1758841333},{"message":"We continue all efforts to fully mitigate and root cause the increased API error rates &amp; latencies for SQS ReceiveMessage APIs configured with server-side encryption in the EU-NORTH-1 Region. We are making slower progress than we initially anticipated. Some AWS Services have seen full recovery for their impacted operations and workflows. We have not yet established an ETA for full recovery and will continue to provide regular updates while the team continues to work on multiple parallel paths. We will provide our next update by 5:45 PM PDT.","summary":"SQS Increased API Error Rates","status":"1","timestamp":1758844779},{"message":"We are making steady progress in our ongoing efforts to fully mitigate the increased API error rates &amp; latencies for SQS ReceiveMessage APIs configured with server-side encryption in the EU-NORTH-1 Region. We have identified the root cause to be related to an issue with a subsystem responsible for SQS metadata. We are pursuing multiple parallel paths and are rolling out changes to address the issue. Our current expectation for recovery is approximately two hours away. We will continue to provide updates as the changes make progress. Some AWS Services have fully recovered for their impacted operations and workflows. We will provide our next update by 7:30 PM PDT.","summary":"SQS Increased API Error Rates","status":"1","timestamp":1758849000},{"message":"We continue to make steady progress in our ongoing efforts to fully mitigate the increased API error rates &amp; latencies for SQS ReceiveMessage APIs configured with server-side encryption in the EU-NORTH-1 Region. The mitigation efforts are taking longer than expected and we are currently monitoring the progress of a change that was initiated to address the underlying issue. Some AWS Services have fully recovered for their impacted operations and workflows. We will continue to monitor the progress and will provide our next update by 9:30 PM PDT.","summary":"SQS Increased API Error Rates","status":"1","timestamp":1758853937},{"message":"We continue to make steady progress in our ongoing efforts to fully mitigate the increased API error rates &amp; latencies for SQS ReceiveMessage APIs configured with server-side encryption in the EU-NORTH-1 Region. While the investigation into the issue was started immediately, it took us longer to determine a path to recovery. We are continuing to monitor the progress of the change that we made and we are seeing some early signs of recovery. Some AWS Services have fully recovered for their impacted operations and workflows. We will continue to monitor the progress and will provide our next update by 10:30 PM PDT.","summary":"SQS Increased API Error Rates","status":"1","timestamp":1758861759},{"message":"Between 1:28 PM and 9:27 PM PDT we experienced increased API error rates and latencies for SQS ReceiveMessage APIs configured with server-side encryption in the EU-NORTH-1 Region. Engineers were automatically engaged at 1:31 PM and immediately began working on mitigation while simultaneously investigating the root cause of this impact. We identified the root cause to be related to an issue with a subsystem responsible for SQS metadata. We applied mitigations to address the underlying issue with the metadata subsystem. Once the change was successful, we observed initial signs of recovery and continued to monitor until full recovery at 9:27 PM. We recommend customers that have a queue with a dead-letter queue configured redrive affected messages to the source queue or a custom destination for processing [1]. Other AWS Services that were affected by this event have also fully recovered for their impacted operations and workflows. We do not expect this issue to reoccur. The issue has been resolved and all AWS Services are operating normally.\n\n[1] <a href=\"https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-configure-dead-letter-queue-redrive.html\">https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-configure-dead-letter-queue-redrive.html</a>","summary":"[RESOLVED] SQS Increased API Error Rates","status":"0","timestamp":1758864300}],"impacted_services":{"awsiot-eu-north-1":{"service_name":"AWS IoT Core","current":"0","max":"1"},"awswaf-eu-north-1":{"service_name":"AWS WAF","current":"0","max":"1"},"cloudtrail-eu-north-1":{"service_name":"AWS CloudTrail","current":"0","max":"1"},"dynamodb-eu-north-1":{"service_name":"Amazon DynamoDB","current":"0","max":"1"},"events-eu-north-1":{"service_name":"Amazon EventBridge","current":"0","max":"1"},"firehose-eu-north-1":{"service_name":"Amazon Kinesis Firehose","current":"0","max":"1"},"groundstation-eu-north-1":{"service_name":"AWS Ground Station","current":"0","max":"1"},"kafka-eu-north-1":{"service_name":"Amazon Managed Streaming for Apache Kafka","current":"0","max":"1"},"lakeformation-eu-north-1":{"service_name":"AWS Lake Formation","current":"0","max":"1"},"lambda-eu-north-1":{"service_name":"AWS Lambda","current":"0","max":"1"},"sagemaker-eu-north-1":{"service_name":"Amazon SageMaker","current":"0","max":"1"},"state-eu-north-1":{"service_name":"AWS Step Functions","current":"0","max":"1"}}}],"glue-us-east-1":[{"summary":"[RESOLVED] Increased error rates","arn":"arn:aws:health:us-east-1::event/GLUE/AWS_GLUE_OPERATIONAL_ISSUE/AWS_GLUE_OPERATIONAL_ISSUE_3A92B_7824AB2D84B","status":"1","date":"1758057619","event_log":[{"message":"We are investigating increased failure rates for Glue Job runs in the US-EAST-1 Region.","summary":"Increased error rates","status":"1","timestamp":1758057619},{"message":"We are seeing initial signs of recovery and continue to work toward full recovery.","summary":"Increased error rates","status":"1","timestamp":1758058622},{"message":"Between 1:37 PM and 2:28 PM PDT, we experienced increased failure rates for Glue Job runs in the US-EAST-1 Region. We were automatically engaged to investigate this at 2:00 PM. We identified the root cause as a recent configuration change that was rolled back at 2:28 PM which brought full recovery. We recommend customers to retry any failed Glue Jobs that were experienced during this issue. We do not expect this issue to reoccur. The issue has been resolved and the service is operating normally.","summary":"[RESOLVED] Increased error rates","status":"0","timestamp":1758060059}],"impacted_services":{"events-us-east-1":{"service_name":"Amazon EventBridge","current":"0","max":"1"}}}],"management-console":[],"iamidentitycenter-ap-southeast-2":[],"internetconnectivity-us-east-1":[],"dynamodb-us-gov-west-1":[],"dynamodb-us-gov-east-1":[],"ec2-ca-central-1":[],"glue-ap-northeast-1":[],"lambda-eu-central-2":[],"apprunner-ap-southeast-1":[],"athena-us-west-2":[],"internetconnectivity-us-east-2":[],"ec2-ap-northeast-1":[],"multipleservices-ap-south-2":[],"emr-us-east-1":[],"bedrock-us-east-2":[],"bedrock-us-west-2":[],"ec2-sa-east-1":[],"ec2-ap-northeast-3":[],"multipleservices-eu-north-1":[],"cognito-us-east-1":[],"ec2-us-east-2":[],"ec2-us-gov-west-1":[],"connect-us-east-1":[],"kinesis-us-east-1":[],"internetconnectivity-ap-southeast-2":[],"servicecatalog-us-west-1":[],"sqs-us-east-1":[],"supportcenter-us-gov-west-1":[],"multipleservices-eu-south-1":[],"multipleservices-us-east-2":[],"quicksight-us-east-1":[],"aws-partner-central":[],"ec2-ap-northeast-2":[]}