Live / Amazon Web Services / Incident
Amazon Web Services: Region Availability — UAE
Amazon Web Services · aws.amazon.comResolved2026-09-15 10:27 UTC
Public — what happened
Summary
Amazon Web Services reported problems with its services in the ME-CENTRAL-1 Region in the UAE beginning on 2026-03-01 at 12:51 UTC, centered on one Availability Zone (mec1-az2) where servers, storage volumes, databases and related resources became unreachable. AWS said the zone lost power after objects struck the data center and caused sparks and a fire, prompting the fire department to cut power to the facility and its generators; customers running across multiple zones were not affected. Over the following hours AWS shifted traffic away from the zone and restored several networking functions, including the ability to create and move network addresses, while saying it had no estimate for when power would return. The incident was marked resolved on 2026-09-15.
Timeline
- Started — 2026-03-01 12:51 UTC
- Investigating — 2026-03-01 12:51 UTC (3 updates)
- Monitoring — 2026-03-01 15:09 UTC (2 updates)
- Resolved — 2026-09-15 10:27 UTC · 198 days after it started
With SquidGrid — where it starts on the route
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 seeCustomers 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