AWS incident history

Right now: clear, by AWS's own status page, mirrored every five minutes.

6
incidents kept since 1 Mar 2026
2
in the last 30 days
0s
median time to resolve, once posted
67%
resolved within an hour

How far back this goes: AWS's feed exposed its 50 most recent incidents when we began mirroring on 25 September 2026, so this page covers 208 days so far and grows from here. Impact labels (5 major or critical) are AWS's own. We don't compare providers on this page; the windows aren't equal yet.

What our probes saw

No monitor that declares AWS as a dependency was evaluated during these incidents, so there's nothing to add from our side yet. This fills in as more sites behind AWS are watched.

Which parts of AWS the incidents touched

Multiple services (me-central-1)
3
Multiple services (me-south-1)
3

Every incident we hold, newest first

Source: AWS's public status page at status.aws.amazon.com, mirrored every five minutes. Data as JSON: /upstream/aws/incidents.json. CC BY 4.0.

If your site depends on AWS, Repose holds the page when the cause is upstream. How the hold decision works →