Datacenter region
AWS Middle East (Bahrain)
me-south-1 · 26.07, 50.59
2 open incidents name AWS me-south-1 as affected in official updates.
This page covers incidents whose official updates name this region as affected. It is not a citywide status report, and the overall AWS status does not tell whether this region works normally.
Incidents affecting AWS me-south-1
- Service disruption: Increased Error Rates
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 goal.
- Service disruption: Increased Error Rates
We are providing an update on the disruption affecting the Middle East (Bahrain) (me-south-1) Region. The damage to our infrastructure spanned multiple Availability Zones and exceeded what our regional and multi-AZ services are designed to withstand. After a thorough assessment, we have determined that we are unable to restore access to the resources and data hosted exclusively in this Region. When the first Availability Zone was damaged in March, we began recommending that customers migrate their workloads to other Regions, and most did so before the Region became unavailable following the disruption of a second Availability Zone in April. Since then, we have supported the remaining customers in re-establishing their operations in alternate Regions, using backups where available or implementing alternative solutions to mitigate the impact of inaccessible data. In parallel, we assessed all affected infrastructure and exhausted every option for restoring data and resources that had not been migrated before the Region became unavailable. We remain committed to supporting our customers in Bahrain in the long term and will share a further update in early 2027. We have notified the relevant authorities and continue to work with them toward that goal.
About this region
me-south-1 is AWS's code for Middle East (Bahrain). Other providers may operate in the same area under different region codes. Problems with shared cloud infrastructure can affect apps hosted there, but a report about one provider does not establish a problem at another.
Physically located in Bahrain. See all outages in Bahrain for the full country view.
FAQ - AWS me-south-1
What is the me-south-1 region?
me-south-1 is AWS's code for Middle East (Bahrain), a cloud datacenter region in Bahrain. Other cloud providers use different region codes, even in the same city.
Is AWS me-south-1 having problems right now?
2 open incidents name me-south-1 as affected in official updates. Check the provider's official status for the latest update.
Why do unrelated apps fail when one region goes down?
Many SaaS products host their backend infrastructure in shared cloud regions. A single region outage can cascade across hundreds of apps that look unrelated to end users.
Where can I find the official AWS status page?
Check AWS Health Dashboard for official region updates. GlobalOutageMap is an independent signal aggregator, not the provider's status authority.