Region Availability (Bahrain)
AWS services do not work in the Middle East (Bahrain) me-south-1 Region. The affected components include Amazon Simple Storage Service, Amazon API Gateway, AWS WAF, and AWS Internet Connectivity. AWS reports that the damage exceeded the design limits of its regional and multi-AZ services. AWS states that it cannot restore access to resources and data hosted only in this Region.
A language model wrote this summary from the updates of AWS.
State
Active
Started
244 d ago
2026-03-02 05:56 UTC
Ongoing for
244 days
Worst impact
Major outage
Timeline
1 updateActive
244 days 100%
Updates
Times in UTCAs posted by AWS
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
Affected components
144AWS 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.cc/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.cc/feed.xml?providers=aws/feed subscribe https://outages.cc/feed.xml?providers=awsFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane