Amazon Web Services status · Cloud & Infrastructure · checked (2m ago)
Also searched as AWS, Amazon AWS.
Operational
No — Amazon Web Services is not down. All Amazon Web Services systems are reported operational.
According to Amazon Web Services's official status page, Amazon Web Services was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, Amazon Web Services's feed reported no outage in 93.22% of our checks.
No outage reported (30d)
93.22%
Share of our checks where Amazon Web Services's feed reported no outage. Degraded counts as no-outage. Not an SLA.
Response time
699 ms
How long the last status check took
Reported by
Operational
All Systems Operational
Is Amazon Web Services down for you right now?
Everything above is read from Amazon Web Services's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Amazon Web Services in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
What Amazon Web Services is
Amazon Web Services is the largest cloud provider, running EC2, S3, Lambda, RDS, DynamoDB, CloudFront, Route 53 and several hundred other services across dozens of regions. AWS incidents are almost always regional: us-east-1 can be in serious trouble while eu-west-1 is completely unaffected.
What Amazon Web Services's status feed covers
AWS does not publish a Statuspage-style JSON summary. It publishes an RSS feed of service events, where each entry is one service in one region — “Service disruption: Amazon EC2 (us-east-1)”. isuptime parses that feed and treats entries from the last 48 hours as current, which is why AWS's reading here is derived from recent events rather than a live indicator. AWS has a long-standing reputation for updating this feed conservatively and late, and the Personal Health Dashboard often shows account-specific impact that never reaches the public feed at all.
One bar per day. Each shows the share of that day's checks where Amazon Web Services's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Amazon Web Services was down.
2026-08-2530 of 30 days recorded · lowest day 0%Today
No outage reported (99%+)
95–99%
80–95%
Under 80%
No data
Other services reporting problems right now
9 other services isuptime tracks were also reporting a problem as of the same check, 2m ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of Amazon Web Services's status endpoint.
Which Amazon Web Services features are affected?
multipleservices (ME-CENTRAL-1) — Disruption
multipleservices (ME-SOUTH-1) — Disruption
Amazon Web Services outage history
Amazon Web Services has published 38 incidents in the last 12 months, the 20 most recent shown here. Only what Amazon Web Services posted itself — not every problem users hit.
No — Amazon Web Services is not down. All Amazon Web Services systems are reported operational. Checked (2m ago).
What is Amazon Web Services's status right now?
Amazon Web Services is reporting “All Systems Operational” on its official status page — Operational — as of . That status feed answered our last check in 699 ms. isuptime reads this from Amazon Web Services's own published feed and does not test Amazon Web Services independently.
When did Amazon Web Services last go down?
The most recent incident Amazon Web Services published was “Service disruption: Increased Error Rates”, opened Sep 15, 10:27 AM UTC (8d ago), and still open. That is the latest entry in Amazon Web Services's own incident feed, not every problem users experienced.
What is Amazon Web Services's uptime?
isuptime does not measure Amazon Web Services's uptime directly — it reads Amazon Web Services's own published status feed. Over the last 30 days, Amazon Web Services's own status feed reported no outage in 93.22% of isuptime's checks. Periods the provider called degraded count as no-outage, and this is isuptime's own measurement, not a contractual SLA.
Is it just me, or is Amazon Web Services down for everyone?
Amazon Web Services reports all systems operational, so the problem is likely local to your network, browser or account. Try a different network or device.
Amazon Web Services says operational but it is not working for me
Check your Personal Health Dashboard — it is account-scoped and routinely shows problems the public feed does not. Confirm which region you are actually calling; a service that is fine in your console region may be degraded in the one your code targets. Throttling exceptions, expired credentials and IAM permission changes all produce errors that feel like an outage and are not one.
