Skip to content- Watching for: A restoration timeline and confirmation of any data-loss scope; whether AWS publishes a post-incident summary; independent verification of the cause; whether other providers' Middle East regions are affected; whether the billing-suspension and migration guidance change.
Notes
- 2026-08-30: ['2026-08-30: [\'2026-08-30: [\\\'2026-08-30: Compacted from a longer entry that carried its own superseded framing. AWS Middle East (Bahrain) region me-south-1, opened July 2019 as AWS\\\\\\\'s first Middle East region, is listed unavailable on the AWS Health Dashboard. Per the Health Dashboard event JSON, the event log opens 2026-03-02 05:56 UTC with a power issue in mes1-az2, the 2026-03-03 update attributes damage in both me-south-1 and me-central-1 (UAE) to drone strikes, and a 2026-04-30 update states the region is unavailable and billing suspended. The region has therefore been down since March 2026. An earlier "started ~2026-07-21" framing was corrected on 2026-07-25: the July HN wave was renewed attention plus the IRGC claim, not the start of the outage. The AWS newsroom states the region was disrupted by the ongoing regional conflict, that AWS is working with local authorities, that many customers have relocated, and advises migrating workloads to alternate regions, recovering from remote backups in other regions, and enacting DR plans. Reporting on the Health Dashboard states in-region billing is suspended and restoration is expected to take months. Iran\\\\\\\'s IRGC claimed via state media that a 2026-07-21 cruise-missile strike destroyed the infrastructure in response to alleged US strikes on a nuclear site; that destruction claim is not independently verified (Tom\\\\\\\'s Hardware, The Register, Betanews). Covered 2026-07-24 Top stories (lead, Outage, confirmed outage with attributed cause) and corrected 2026-07-25.\\\']\']']
Stories