BLACKOUT.NETWORK › Network Status › Providers › AWS

BLACKOUT.NETWORK · NETWORK STATUS

AWS status right now

The largest cloud platform: servers, storage, databases and networking behind a large share of apps and websites.

Minor issue2 active incident(s)Our check: 0 new, 2 long-running event(s)
2active incidents now
2incidents in the last 90 days (official feed)
66.56%of our 5-minute checks with no degraded or major status, last 7 days

Live status

From AWS Health public events, AWS status RSS. Times in Eastern (ET).

Multiple services: Region Availability

Mar 1, 7:51 AM EST · long-running, still open · Major outage · source: AWS Health Dashboard
UAE (me-central-1)AWS AmplifyAWS AppConfigAWS AppSyncAWS Application Migration ServiceAWS BackupAWS BatchAWS Certificate ManagerAWS Client VPN+52 more services

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). …

Multiple services: Region Availability

Mar 2, 12:56 AM EST · long-running, still open · Major outage · source: AWS Health Dashboard
Bahrain (me-south-1)AWS AmplifyAWS Amplify AdminAWS App MeshAWS AppConfigAWS AppSyncAWS Application Migration ServiceAWS BackupAWS Batch+52 more services

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 Availab…

Regions with active problems

UAE (me-central-1)active event
Bahrain (me-south-1)active event

Our 5-minute checks · last 7 days

We read AWS's official status every 5 minutes. Each sliver is one hour, colored by the worst status seen; the daily figure is the share of checks with no degraded or major status. Stored since Nov 11, 9:48 PM EST.

7 days agonow
0%Wed 11/11
0%Thu 11/12
96%Fri 11/13
100%Sat 11/14
32%Sun 11/15
59%Mon 11/16
100%Tue 11/17
100%Wed 11/18

Periods flagged by our checks

  • Nov 11, 9:48 PM EST → ongoing

    1 new, 2 long-running event(s)

    Amazon Elastic Compute Cloud (Tokyo): [RESOLVED] Elevated API issues and Launch Failures; Multiple services (UAE): Region Availability (open since Mar 01); Multiple services (Bahrain): Region Availability (open since Mar 02)

Incident history

Incidents per month from the official feed, by severity. AWS's public RSS keeps recent status posts only; account-specific events are in your AWS Health Dashboard. History is short: dashed boxes and empty months before the feed's first entry mean no published data, not a clean record.

No data: before the feed historyDecNo data: before the feed historyJanNo data: before the feed historyFebMar 2026: 2 major outage2No data: before the feed historyMarApr 2026: 2 major outage2AprMayJunJulAugSep 2026: 2 major outage2SepOctNov
JunJulAugSep 2026: 2 major outage2SepOctNov

Last 13 weeks

0 incident(s)0 incident(s)0 incident(s)2 incident(s)20 incident(s)0 incident(s)0 incident(s)0 incident(s)0 incident(s)0 incident(s)0 incident(s)0 incident(s)0 incident(s)13 weeks agothis week
0 incident(s)0 incident(s)0 incident(s)2 incident(s)20 incident(s)0 incident(s)0 incident(s)0 incident(s)0 incident(s)0 incident(s)0 incident(s)0 incident(s)0 incident(s)13 weeks agothis week
OperationalMinorDegradedMajorNo data

Root causes: hack, AI, config error or something else?

For each incident in the past year we show a cause only when AWS's own report states one, quoting the sentence. The category is our label for that sentence; anything else is marked Unconfirmed / not yet disclosed.

Hardware / power: 4Unconfirmed / not yet disclosed: 26incidents
Hardware / power: 4
Unconfirmed / not yet disclosed: 2
  • Sep 15, 6:27 AM EDT

    Service disruption: Increased Error Rates

    Unconfirmed / not yet disclosed

    No cause stated in the official record yet.

    Official incident page

  • Sep 15, 6:22 AM EDT

    Service disruption: Increased Error Rates

    Unconfirmed / not yet disclosed

    No cause stated in the official record yet.

    Official incident page

  • Apr 30, 3:25 AM EDT

    Service disruption: Increased Error Rates

    Hardware / power

    “The Middle East (UAE) Region (ME-CENTRAL-1) has suffered damage as a result of the conflict in the Middle East and is currently unable to reliably support customer applications.” — AWS

    Official incident report

  • Apr 30, 3:07 AM EDT

    Service disruption: Increased Connectivity Issues and API Error Rates

    Hardware / power

    “The Middle East (Bahrain) Region (ME-SOUTH-1) has suffered damage due to the conflict in the Middle East and is currently unavailable.” — AWS

    Official incident report

  • Mar 2, 12:56 AM EST · ongoing

    Multiple services: Region Availability

    Hardware / power

    “We are investigating connectivity and power issues affecting APIs and instances in a single Availability Zone (mes1-az2) in the ME-SOUTH-1 Region due to a localized power issue.” — AWS

    Official incident report

  • Mar 1, 7:51 AM EST · ongoing

    Multiple services: Region Availability

    Hardware / power

    “We are investigating connectivity and power issues affecting APIs and instances in a single Availability Zone (mec1-az2) in the ME-CENTRAL-1 Region due to a localized power issue.” — AWS

    Official incident report

Notable past outages

The big ones, with the cause in the official write-up's own words.

Oct 19–20, 2025

US-EAST-1 DynamoDB DNS failure

Network / BGP / DNS

“The root cause of this issue was a latent race condition in the DynamoDB DNS management system that resulted in an incorrect empty DNS record for the service's regional endpoint.”

Impact: DynamoDB, EC2 launches and Network Load Balancer errors in N. Virginia, rippling into many apps that depend on them.

AWS post-event summary
Mar 1, 2026 onward

Middle East regions (UAE ME-CENTRAL-1, Bahrain ME-SOUTH-1)

Hardware / power

“Due to the ongoing conflict in the Middle East, both affected regions have experienced physical impacts to infrastructure as a result of drone strikes.”

Impact: Power and connectivity loss in several Availability Zones; AWS later said it could not restore resources hosted only in one UAE zone (mec1-az2).

AWS Health Dashboard posts
Dec 7, 2021

US-EAST-1 internal network congestion

AI / automation

“An automated activity to scale capacity of one of the AWS services hosted in the main AWS network triggered an unexpected behavior from a large number of clients inside the internal network.”

Impact: Widespread errors in N. Virginia for hours, including AWS's own dashboard and support tools.

AWS post-event summary
Feb 28, 2017

S3 outage in US-EAST-1

Config / deploy error

“An authorized S3 team member using an established playbook executed a command which was intended to remove a small number of servers… one of the inputs to the command was entered incorrectly.”

Impact: S3 in N. Virginia went down, taking many websites and AWS services with it.

AWS post-event summary
Know about the next big outage first
The free BLACKOUT.NETWORK newsletter: major outages, threats and what to do. Follow us on YouTube and X too.
Get the free newsletter

If your business runs on AWS

A short playbook. Tick items as you go (saved on this device only).

1 · Confirm the impact

2 · Fail over and limit the damage

3 · Monitor and get alerts

4 · Communication templates

Customer heads-up (incident open)

Status update ({time} ET): Some of our services are slow or unavailable because of an outage at AWS, a provider we use. Your data is safe. We're working around it and will update you by {next} ET. Live status: {your_status_page}

Internal alert

AWS incident affecting {services} in {region} since {time} ET. Impact on us: {impact}. Owner: {name}. Failover: {yes_no}. Next check-in {next} ET.

All clear

Resolved ({time} ET): AWS has recovered and our services are back to normal. If anything still looks wrong, reply here or contact {support}. Thank you for your patience.

Fill in the {curly} parts. Post updates somewhere not hosted on the affected provider.

Official links, contacts and alerts

Every link checked before publishing. Phone numbers only where AWS publishes them.

Other providers: Microsoft Azure · Microsoft 365 · Google Cloud · Google Workspace · Cloudflare · Akamai · Starlink · Networks near me · All network checks. Research only; not affiliated with Amazon Web Services (AWS). Names identify services only.