AWS is up
OperationalNo known problems: AWS's status page says operational
Reports count in aggregate against normal levels; one alone never makes a claim.
Open incidents
What AWS has posted and not resolved.
AWS has no open incidents.
Minor or regional issues (2)
Open issues confined to one country, region, site, carrier route, asset or slice of customers. AWS's state, uptime and the Down Index leave them out.
- Multiple services (Bahrain): Region Availability
The provider says it is unable to restore access to resources and data hosted exclusively in the Middle East (Bahrain) Region (me-south-1), where damage spanned multiple Availability Zones. It will share a further update in early 2027.
- Multiple services (UAE): Region Availability
AWS says it cannot restore access to resources and data hosted exclusively in mec1-az2 in the ME-CENTRAL-1 (UAE) Region. It continues recovering regional resources and zonal resources in mec1-az1 and mec1-az3. Most customers have moved to other Regions.
Daily history
Worst impact each day, from the provider's own incidents.
No per-component history yet.
Last 90 days in numbers
From the provider's own posts, including history read from its archive.
- Uptime
- 100.00%since Jan 28
- Incidents
- 10on 0 days
- Median duration
- 2h 20m
- Longest
- 3d
- Postmortem rate
- n/apartial and major outages
People reporting problems
Hourly counts, last 24 hours.
No reports in the last 24 hours.
Follow AWS incidents
Following several providers? Check your stack to get one feed for all of them.
https://down.guide/feed?provider=aws
In Slack, install the RSS app and run /feed subscribe https://down.guide/feed?provider=aws in a channel. In Discord, add a feed bot such as MonitoRSS and give it this URL. Or paste it into Feedly or any RSS reader.
https://down.guide/feed?provider=aws&format=atom
The same entries as Atom, for readers that prefer it.
https://down.guide/feed?provider=aws&format=json
The same entries as JSON Feed 1.1, each with the full incident under _down_guide, for scripts.
https://down.guide/api/v1/incidents?provider=aws
Pages of 30 incidents, newest first. Pass the response's next_cursor as cursor for the next page.
Recent incidents
The last 90 days.
- Amazon Elastic Compute Cloud (Oregon): Elevated Launch Failures
The provider says EC2 instance launch failures affected all AZs in US-WEST-2 from 2:35 PM to 4:21 PM PST, caused by a subsystem supporting EBS Volumes. The issue is resolved, running instances were not impacted, and retrying failed requests is recommended.
- AWSDegradedAPIGATEWAY (us-west-2): Increased invoke error rates
- AWSDegradedINTERNETCONNECTIVITY (eu-south-2): Elevated packet loss
- AWSPartial outageEC2 (us-east-1): Increased Error Rates
- AWSDegradedMULTIPLESERVICES (us-west-2): Increased API Error Rates
- AWSPartial outageCONNECT (ap-northeast-1): Increased Error Rates
- AWSPartial outageEC2 (eu-west-2): Increased Error Rates
- AWSDegradedDIRECTCONNECT (eu-central-1): Increased Packet loss
AWS status: questions
Is AWS down right now?
No known problems: AWS's status page says operational (checked 2026-11-11 01:20 UTC from AWS's official status page).
What is AWS's uptime?
100.00% over the last 90 days, from the incidents AWS posted on its own status page. A major outage counts in full and a partial outage as 30% of its time, per component.
When was AWS's last outage?
Amazon Elastic Compute Cloud (Oregon): Elevated Launch Failures, starting 2026-11-06 22:51 UTC and lasting 2h 21m: https://down.guide/DWN-89ef96e280
How do I get alerts when AWS goes down?
Subscribe to https://down.guide/feed?provider=aws (RSS; add format=atom or format=json). In Slack, install the RSS app and run /feed subscribe with that URL; in Discord, give it to a feed bot such as MonitoRSS. No account needed.
Where does down.guide get AWS's status?
From AWS's official status page, https://health.aws.amazon.com/health/status, read every minute. AWS's words are quoted verbatim and linked.