User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
aws.amazon.com · Cloud & developer
Checks are succeeding and user reports are near the baseline.
Live diagnosis
Tests aws.amazon.com from your browser and compares it with our checks, the official status, and user reports.
Press Run testNothing leaves your browser except a request to the site and to us.
Reachable from all 4 regions we check from.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 126 ms · 5 min ago.
No status feed
AWS does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 12:00 | 0 | 0.0 | 170 ms | 0 |
| 12:15 | 0 | 0.0 | 62 ms | 0 |
| 12:30 | 0 | 0.0 | 125 ms | 0 |
| 12:45 | 0 | 0.0 | 162 ms | 0 |
| 13:00 | 0 | 0.0 | 233 ms | 0 |
| 13:15 | 0 | 0.0 | 166 ms | 0 |
| 13:30 | 0 | 0.0 | 266 ms | 0 |
| 13:45 | 0 | 0.0 | 166 ms | 0 |
| 14:00 | 0 | 0.0 | 95 ms | 0 |
One report per service every 10 minutes from this network. No account.
Get an email when AWS goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
When AWS has trouble, these services often do too.
Checks are succeeding and user reports are near the baseline.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.