Amazon Web Services est-il en panne ?
EC2, S3, RDS, Lambda : le socle d'une grande partie d'Internet.
Gravité sur 90 jours
Sur les incidents publiés par le fournisseur. Maintenances exclues.
Interruptions sur 90 jours
Que faire si Amazon Web Services est en panne
Vérifier que ça ne vient pas de chez vous
Ouvrez un autre site. S'il se charge, votre connexion va bien.
Lire la source officielle
La page de statut de Amazon Web Services fait foi. C'est elle que nous relevons toutes les 5 minutes.
Page de statut officielle →Voir ce qui se dit en direct
Une panne apparaît souvent sur X avant que Amazon Web Services ne la publie.
Signalements « Amazon Web Services down » sur X →Savoir quand c'est rétabli
Plutôt que de recharger cette page, laissez votre adresse : l'alerte part dès la mise à jour.
Historique des incidents
Publié par Amazon Web Services
Service impact: Increased invoke error rates
Between 7:27 AM and 8:47 AM PDT, and between 10:47 AM and 4:15 PM PDT, we experienced intermittent invoke error rates and latencies for HTTP APIs in the US-WEST-2 Region. During this time, customers would have observed increased latency or errors when invoking HTTP APIs, with elevated errors occurring between 3:12 PM and 3:45 PM PDT. This represented the period of highest customer impact with the
Service is operating normally: [RESOLVED] Elevated packet loss
Between 8:48 AM and 11:28 AM PDT, we experienced elevated packet loss within a single Availability Zone (eus2-az1) in the EU-SOUTH-2 Region. This issue resulted in elevated API latencies and error rates for multiple workflows and AWS Services. We were automatically alerted to the issue at 8:54 AM, and immediately began work to identify the root cause while taking multiple parallel paths to mitigat
Service impact: Elevated packet loss
We are seeing early signs of recovery. We will provide you with another update by 12:00 PM PDT.
Service impact: Elevated packet loss
We have identified the root cause and are currently focusing our mitigation efforts to drive full recovery. While we don't have an exact estimate for how long our current efforts will take, we do expect to see incremental improvements as our efforts proceed. We will provide you with another update by 11:45 AM PDT, or sooner if new information becomes available.
Service impact: Elevated packet loss
Our efforts to mitigate the elevated packet loss with a single Availability Zone (eus2-az1) in the EU-SOUTH-2 Region is still underway. We are seeing some signs of improvement as a result of multiple parallel efforts. We continue to work to confirm root cause and fully mitigate the issue. While we currently do not have an estimate for how long our actions will take, we will keep you informed of ou
Service impact: Elevated packet loss
We are experiencing elevated packet loss with a single Availability Zone (eus2-az1) in the EU-SOUTH-2 Region. This issue is also resulting in elevated API latencies and error rates for other workflows and AWS Services. Engineers were automatically engaged and are working to identify the root cause and to mitigate the issue. We will provide you with another update by 10:15 AM PDT or sooner as new i
Service impact: Elevated packet loss
We are investigating elevated packet loss in the EU-SOUTH-2 Region.
Service disruption: Increased Error Rates
We are providing an update on the disruption affecting the Middle East (UAE) (me-central-1) Region. After a thorough assessment, we have determined that we are unable to restore access to the resources and data hosted exclusively in the mec1-az2 Availability Zone. We continue to work on recovering regional resources, as well as zonal resources hosted in the other affected Availability Zones (mec1-
Service disruption: Increased Error Rates
We are providing an update on the disruption affecting the Middle East (Bahrain) (me-south-1) Region. The damage to our infrastructure spanned multiple Availability Zones and exceeded what our regional and multi-AZ services are designed to withstand. After a thorough assessment, we have determined that we are unable to restore access to the resources and data hosted exclusively in this Region. Wh
Service disruption: Increased Error Rates
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 r
Service disruption: Increased Connectivity Issues and API Error Rates
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 e
Service impact: Increased Connectivity Issues and API Error Rates
We are providing an update on the ongoing service disruptions affecting the AWS Middle East (Bahrain) Region (ME-SOUTH-1). We continue to make progress on recovery efforts across multiple workstreams. With the immediate phase of this event now better understood, we are moving to a more targeted communication model. Going forward, updates will be delivered directly to affected customers through the
Service disruption: Increased Error Rates
We are providing an update on the ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1). We continue to make progress on recovery efforts across multiple workstreams. For Amazon S3, we are seeing continued improvement in PUT and LIST availability. Newly written objects are now able to be successfully retrieved, and we continue to work on reducing GET error rates fo
Service impact: Increased Connectivity Issues and API Error Rates
Recovery efforts in the affected Availability Zone (mes1-az2) in the ME-SOUTH-1 Region are ongoing, with the situation remaining consistent with our last update. We have no change to expected timelines for fully restoring power and connectivity. While progress is being made, significant work remains before full restoration is complete. We continue to recommend customers launch replacement resource
Service disruption: Increased Error Rates
We are providing an update on the ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1). The overall state of the region remains largely unchanged, though our teams continue to make progress on recovery efforts across multiple workstreams. For Amazon S3, we are seeing continued improvement in PUT and LIST availability. Newly written objects are now able to be succ
Service impact: Increased Connectivity Issues and API Error Rates
We continue to work toward restoring power in the affected Availability Zone (mes1-az2) in the ME-SOUTH-1 Region. The overall state of the region remains largely unchanged from our previous update. At this time, we have no updated guidance on expected timelines for fully restoring power and connectivity. We are taking all necessary steps to support the recovery process. While progress is being mad
Service disruption: Increased Error Rates
We are providing an update on the ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1). The overall state of the region remains largely unchanged from our previous update. We continue to work closely with local authorities and are prioritizing the safety of our personnel throughout our recovery efforts. Teams continue to assess the damage to the affected facilities
Service impact: Increased Connectivity Issues and API Error Rates
We continue to work towards restoring power in the affected Availability Zone (mes1-az2) in the ME-SOUTH-1 Region. We have no updated guidance on expected recovery times, and still expect this to take at least a day to fully restore power and connectivity. AWS infrastructure is designed to be highly resilient, but given the uncertainty of the current situation, we encourage our customers to replic
Service disruption: Increased Error Rates
We continue to work towards recovery of the two impaired Availability Zones (mec1-az2 and mec1-az3) in the ME-CENTRAL-1 Region with a focus on restoring functionality to foundational services. Since our last update we have made incremental progress in recovering the DynamoDB control plane which will not be visible to external customers but are required for the restoration of service. Similarly we
Service impact: Increased Connectivity Issues and API Error Rates
We are providing an update on the ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1) and the AWS Middle East (Bahrain) Region (ME-SOUTH-1). Due to the ongoing conflict in the Middle East, both affected regions have experienced physical impacts to infrastructure as a result of drone strikes. In the UAE, two of our facilities were directly struck, while in Bahrain,
Service disruption: Increased Error Rates
We are providing an update on the ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1) and the AWS Middle East (Bahrain) Region (ME-SOUTH-1). Due to the ongoing conflict in the Middle East, both affected regions have experienced physical impacts to infrastructure as a result of drone strikes. In the UAE, two of our facilities were directly struck, while in Bahrain,
Service impact: Increased Connectivity Issues and API Error Rates
We continue to work towards restoring power in the affected Availability Zone (mes1-az2) in the ME-SOUTH-1 Region. We have no updated guidance on expected recovery times, and still expect this to take at least a day to fully restore power and connectivity. We continue to advise customers to launch replacement resources in one of the unaffected Availability Zones or an alternate AWS Region. At this
Service disruption: Increased Error Rates
We continue to work towards recovery of the two impaired Availability Zones (mec1-az2 and mec1-az3) in the ME-CENTRAL-1 Region. We have partially restored access to the AWS Management Console, however, some pages will continue to load unsuccessfully until we have recovered core services and power. In parallel to the power and recovery efforts, we are working to restore access to tools and utilitie
Service impact: Increased Connectivity Issues and API Error Rates
We continue to work towards restoring power in the affected Availability Zone (mes1-az2) in the ME-SOUTH-1 Region. We currently expect our recovery efforts to take at least a day. Our current guidance regarding immediate recovery remains unchanged from our previous update. Customers are able to disassociate Elastic IP addresses from resources in the affected Availability Zone and associate those w
Service disruption: Increased Error Rates
We continue to work towards recovery of the two impaired Availability Zones (mec1-az2 and mec1-az3) in the ME-CENTRAL-1 Region. The impact is causing elevated errors rates for both the Management Console and CLI. Our current expectation is that recovery will take at least a day to complete. We continue to recommend customers enact their disaster recovery plans and recover from remote backups into
Source officielle
Données issues de la page de statut publique de Amazon Web Services.
Page de statut officielleBadge pour votre site
Affichez le statut de Amazon Web Services chez vous. Mis à jour automatiquement, même adresse que cette page.
<a href="https://www.upstreamstatus.com/status/aws"><img src="https://www.upstreamstatus.com/badge/aws" width="280" height="64" alt="Amazon Web Services status" /></a>
Autres services Cloud & infrastructure
Questions fréquentes
Amazon Web Services est-il en panne actuellement ?
Au dernier relevé (2026-10-31 19:44 UTC), Amazon Web Services est en état « Opérationnel » d'après sa page de statut officielle. 5 incidents en cours : Service impact: Elevated packet loss.
Quelle est la disponibilité de Amazon Web Services sur 90 jours ?
L'historique de Amazon Web Services est en cours de constitution sur Upstream Status.
Comment être prévenu automatiquement d'une panne de Amazon Web Services ?
Créez une alerte gratuite sur Upstream Status : dès qu'un incident est publié sur la status page de Amazon Web Services, vous recevez un email (ou une notification Slack/webhook avec un plan payant).