User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Shopping
amazon.com · Shopping
Checks are succeeding and user reports are near the baseline.
Live diagnosis
Tests 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.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 48 ms · 4 min ago.
No status feed
Amazon does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 12:00 | 0 | 0.0 | 94 ms | 0 |
| 12:15 | 0 | 0.0 | 165 ms | 0 |
| 12:30 | 0 | 0.0 | 89 ms | 0 |
| 12:45 | 0 | 0.0 | 69 ms | 0 |
| 13:00 | 0 | 0.0 | 279 ms | 0 |
| 13:15 | 0 | 0.0 | 163 ms | 0 |
| 13:30 | 0 | 0.0 | 153 ms | 0 |
| 13:45 | 0 | 0.0 | 146 ms | 0 |
| 14:00 | 0 | 0.0 | 69 ms | 0 |
| 14:15 | 0 | 0.0 | 158 ms | 0 |
| 14:30 | 0 | 0.0 | 184 ms | 0 |
| 14:45 | 0 | 0.0 | 94 ms | 0 |
No outages on record for Amazon yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Amazon goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Runs on: AWS
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.