when has aws lost s3 in a region

AWS has had region-level S3-impacting incidents in 2026 , including disruptions in the Middle East region when infrastructure in the UAE was hit and AWS reported connectivity loss for an Availability Zone and related regional effects. A later report also said the AWS Bahrain region was disrupted following drone activity, marking another regional AWS incident in that same period.

What happened

• In early March 2026, AWS reported a UAE data center outage after “objects” struck the facility and caused a fire, with broader regional connectivity effects.
• Around late March 2026, AWS Bahrain was reported as disrupted following drone activity.

• These were not “S3 only” incidents in the narrow sense; they were regional infrastructure disruptions that could affect S3 access depending on where workloads and replicas were deployed.

How to read this

• S3 is designed for high durability, so a complete “loss” of S3 in a region is rare.
• What users usually experience is one of these:
  • control-plane/API issues,
  • access latency or partial outages,
  • region-specific connectivity problems,
  • application-level failure because dependencies were all in one region.

Practical takeaway

If you mean “when has AWS completely lost S3 in a region,” the better answer is: public reports show regional disruptions that impacted AWS services , not a well-known permanent loss of S3 itself. If you want, I can turn this into a short incident timeline or a region-by-region table.