Live  /  Amazon Web Services  /  Incident

Amazon Web Services: Region Availability — Bahrain

Amazon Web Services · aws.amazon.comResolved2026-09-15 10:22 UTC
Public — what happened

Summary

Amazon Web Services reported problems starting March 2, 2026 at 05:56 UTC in one Availability Zone (mes1-az2) of its Bahrain region (ME-SOUTH-1), first seen as higher API error rates and then as loss of power and connectivity affecting servers, storage volumes, databases and other services there. AWS said a drone strike near one of its facilities physically damaged infrastructure and disrupted power, and it warned that recovery would take at least a day because facilities, cooling and power systems needed repair. While work went on, AWS moved traffic to the region's other zones, restored server and networking APIs in those zones, and advised customers to relaunch resources elsewhere, restore from snapshots, or back up data outside the region. The incident is marked resolved as of September 15, 2026 at 10:22.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Amazon Web Services against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Amazon Web Services: paths off baseline right now, where on the route conditions change, and its full incident track record.

Included with any paid plan.

Open the Amazon Web Services report →

More from Amazon Web Services

The full archive is on the Amazon Web Services status & history page.

Related: Amazon Web Services status & history. SquidGrid is not affiliated with Amazon Web Services.