Amazon Web Services status history
Current state: partial outage — “2 open events on the AWS Health Dashboard (Bahrain, UAE)” per https://status.aws.amazon.com (vendor's own feed (hand-written parser)), checked 2026-09-16 12:28 UTC.
0incidents, last 30 days
0incidents, last 90 days
2incidents on record
vendor's own feed (hand-written parser) only exposes incidents that are open right now, so this history starts on 2026-09-04, the day we first watched Amazon Web Services. It fills in from here.
Incidents on record (2)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-03-02 05:56 UTC | Multiple services (Bahrain): Region Availability | active | operational issue | open |
| 2026-03-01 12:51 UTC | Multiple services (UAE): Region Availability | active | operational issue | open |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Amazon Web Services with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"amazon-web-services"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}