← Front pageReports · Watch · Archive
DRASKER

DRASKER REPORT

published · Updated October 27, 2026

AWS says Bahrain data cannot be restored

The company said damage across multiple Bahrain sites exceeded what its services were designed to withstand. Its separate update described a different status in the UAE: data in one availability zone remained unrecovered, with restoration work continuing in two others.2

Gadget Review, citing Reuters, reported a second Bahrain disruption on March 24 and said AWS listed dozens of core services as disrupted by April 30, with recovery expected to take months.1

KEY POINTS
  • Amazon said in March that drones directly struck two UAE data centers and that a nearby strike damaged a Bahrain facility.2
  • AWS said Sept. 15 that it could not restore data hosted exclusively in Bahrain, citing damage at multiple sites beyond what its services were designed to withstand.2
  • For the UAE, AWS said it had been unable to recover resources and data in one zone and was continuing restoration work in two other affected zones.2
  • The IRGC claimed it targeted the Bahrain facility over Amazon’s support of the U.S. military; that is the group’s stated rationale for the attack.2
  • AWS’s Sept. 15 statement described ongoing work in two affected UAE zones but did not say when restoration would be complete.2
WHAT WE KNOW

AWS said on Sept. 15 that it could not restore resources and data hosted exclusively in its Bahrain region after damage at multiple sites there exceeded what its services were designed to withstand.2

The company’s account of the UAE was not identical: it said one availability zone remained unrecovered, while it was still working on two other affected zones.2

Strikes and the first reported disruptions

Amazon said in March that two of its data centers in the UAE had been directly struck by drones and that a Bahrain facility was damaged by a nearby strike. The company also said the IRGC claimed responsibility and said it targeted the Bahrain facility because of Amazon’s support for the U.S. military.2

Gadget Review, citing Reuters, reported that Iranian drone strikes began March 1, 2026, and that a UAE data center was hit, causing a fire and power cut. The same report said AWS confirmed strike damage in the UAE and Bahrain on March 2 and that Bahrain experienced a second disruption on March 24.1

Service disruption and AWS’s recovery statements

Gadget Review, citing Reuters, reported that by April 30 AWS listed dozens of core services—including EC2, S3, DynamoDB, Lambda and RDS—as disrupted, with recovery expected to take months.1

In its Sept. 15 dashboard update, AWS said it was unable to restore access to resources and data hosted exclusively in Bahrain. It attributed that condition to damage at multiple Bahrain-based sites that exceeded what its services were designed to withstand.2

AWS described the UAE separately: it said it had not recovered resources and data in one availability zone and was continuing work to restore two other affected zones. The update did not give a completion date.2

Gadget Review quoted AWS as saying the infrastructure damage spanned multiple availability zones and exceeded what its regional and multi-zone services were designed to withstand. AWS’s Sept. 15 Bahrain update, as reported by CNBC, said damage at multiple sites exceeded what its services were designed to withstand.1,2

What remains unclear

AWS’s Sept. 15 statement described damage at multiple Bahrain sites but did not specify the buildings or precise technical failure modes.2

TIMELINE
  1. Gadget Review, citing Reuters, said Iranian drone strikes began and a UAE data center was hit, causing a fire and power cut.1

  2. Gadget Review, citing Reuters, said AWS confirmed drone-strike damage in the UAE and Bahrain.1

  3. Gadget Review, citing Reuters, said a second disruption hit Bahrain.1

  4. Gadget Review, citing Reuters, said AWS listed dozens of core services as disrupted and expected recovery to take months.1

  5. AWS said it could not restore access to resources and data hosted exclusively in Bahrain; in a separate post, it said one UAE zone remained unrecovered while work continued on two others.2

WHAT WE STILL DON'T KNOW
  • The specific physical infrastructure damaged (e.g., building names, exact locations) and the precise technical failure modes (e.g., power, cooling, network) are not detailed.
  • Independent technical assessments of the damage (e.g., from infrastructure engineers, satellite imagery analysts) are absent in the reporting Drasker has located.
  • The full scope of impacted customers (beyond generic 'government, healthcare, financial services') and specific examples of critical services disrupted are not provided.
  • The exact timeline of the strikes and the subsequent service degradation (beyond the March and September milestones) lacks granular, independently verified detail.
  • Alternative explanations for the outage (e.g., cascading failures unrelated to direct strikes) are not explored or presented in the evidence.
  • The current status of recovery efforts in the two UAE zones AWS is still 'working to restore' is not specified beyond the September 15 statement.
  • The specific physical infrastructure damaged, including building names and exact locations, and the precise technical failure modes, such as power, cooling or network problems, are not detailed in AWS’s statements.
  • Independent technical assessments of the damage, such as assessments by infrastructure engineers or satellite imagery analysts, are not available in the material reviewed for this report.
  • The full scope of impacted customers and specific examples of critical services disrupted are not provided in the cited accounts.
  • The exact timeline of the strikes and subsequent service degradation, beyond the March and September milestones, lacks granular, independently verified detail.
  • The cited accounts do not explore alternative explanations for the outage, such as cascading failures unrelated to direct strikes.
  • AWS’s Sept. 15 statement does not specify the current status or completion timetable for recovery efforts in the two UAE zones it said it was still working to restore.
SOURCES
  1. 1.
  2. 2.