AWS says it's working everywhere apart from problems in 2 of its regions (UAE and Bahrain).
Multiple services in UAE: Region Availability
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…
Multiple services in Bahrain: Region Availability
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…
From AWS's official status page, read again when you open this page. This page updates by itself.
Email us and we'll tell you when AWS reports a major outage, and when it's working again.
You sign up by sending one email, so nobody else can use your address. Every alert has a stop link. Add "all problems" to the subject to hear about small problems too.
Uptime and history
Not counted above: 9 problems that affected only one region or a few customers. They're listed under recent problems.
Recent
AWS in Spain: Elevated packet loss
AWS in N. Virginia: Increased Error Rates
AWS in Oregon: Increased API Error Rates
AWS in Tokyo: Increased Error Rates
AWS in London: Increased Error Rates
AWS in Frankfurt: Increased Packet loss
AWS in Mumbai: Elevated Packet Loss
AWS in Oregon: Connectivity Issues
Parts
AWS's status page doesn't list separate parts, so we show one status for the whole service.
Alternatives
Other apps that do the same job, ranked by their own record over the last 90 days.
| App | Now | Problems, last 90 days | Time with problems | Website |
|---|---|---|---|---|
 Netlify | Some problems | 16 | 21 h 9 min | Visit Netlify |
 Vercel | Working normally | 22 | 26 h 25 min | Visit Vercel |
 DigitalOcean | Working normally | 19 | 4 days 18 h | Visit DigitalOcean |
 Supabase | Working normally | 25* | 12 days 7 h | Visit Supabase |
 Cloudflare | Some problems | 54* | 55 days 6 h | Visit Cloudflare |
Ranked by their own reported problems over the last 90 days. * The record for this app is still filling in.
Safety
Facts from its own public records, checked every day.
Checked 22 Oct 2026 from amazon.com's public records. Breach data from Have I Been Pwned (CC BY 4.0).
Follow
No sign-up needed: a feed for your reader or team channel, or a live badge for your own site.
Every problem AWS reports, as it happens, in your feed reader or a team channel.
appys.com/status/aws/feed/
/feed subscribe https://appys.com/status/aws/feed/Shows AWS's status, updated every few minutes. Copy the code into a web page, an intranet or a README.
For the uptime badge, change the address to appys.com/badge/aws/uptime/.
About
Amazon Web Services, the cloud that runs a large share of the internet's apps and websites.
Appys is independent and isn’t connected with the apps it lists. Statuses come from each app’s own status page. How Appys checks apps.