Region Availability (UAE)
AWS services do not work in the Middle East (UAE) Region (me-central-1). This affects many components, including Amazon S3 Replication Time Control, Amazon Relational Database Service, AWS Sign-In, and AWS Direct Connect. AWS reports that resources in the mec1-az2 Availability Zone cannot be restored. AWS continues to recover other regional and zonal resources. The incident is active.
State
Active
Started
245 d ago
2026-03-01 12:51 UTC
Ongoing for
245 days
Worst impact
Major outage
Timeline
1 updateActive
245 days 100%
Updates
Times in UTCAs posted by AWS
We are providing an update on the disruption affecting the Middle East (UAE) (me-central-1) Region. After a thorough assessment, we have determined that we are unable to restore access to the resources and data hosted exclusively in the mec1-az2 Availability Zone. We continue to work on recovering regional resources, as well as zonal resources hosted in the other affected Availability Zones (mec1-az1 and mec1-az3). Since the disruption began in March, most customers have been able to re-establish their operations in other Regions by restoring backups or copying data that remained accessible. AWS Support remains available to help customers who need assistance moving their applications to alternate Regions. We remain committed to supporting our customers in the UAE. We are working on replacing the affected infrastructure and will provide an update on the restoration of our services in the coming months. We have notified the relevant authorities and continue to work with them toward that
Affected components
135AWS in the last 90 days
Full historyIncidents in 90 days
2
Days with an incident
90
Median duration
Not enough data
This incident
Not comparable
Other AWS incidents
All incidentsFollow AWS
Your coding agent knows when AWS is down, and tells you when a failure is theirs, not yours. You can also get AWS incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "aws" and tell me if AWS has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=aws/feed subscribe https://outages.live/feed.xml?providers=awsFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane