User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Shopping
nike.com · Shopping
Checks are succeeding and user reports are near the baseline.
Live diagnosis
Tests nike.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 930 ms · 4 min ago.
No status feed
Nike does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 11:30 | 0 | 0.0 | 1040 ms | 0 |
| 11:45 | 0 | 0.0 | 802 ms | 0 |
| 12:00 | 0 | 0.0 | 572 ms | 0 |
| 12:15 | 0 | 0.0 | 422 ms | 0 |
| 12:30 | 0 | 0.0 | 886 ms | 0 |
| 12:45 | 0 | 0.0 | 772 ms | 0 |
| 13:00 | 0 | 0.0 | 296 ms | 0 |
| 13:15 | 0 | 0.0 | 1302 ms | 0 |
| 13:30 | 0 | 0.0 | 618 ms | 0 |
| 13:45 | 0 | 0.0 | 358 ms | 0 |
| 14:00 | 0 | 0.0 | 448 ms | 0 |
| 14:15 | 0 | 0.0 | 897 ms | 0 |
| 14:30 | 0 | 0.0 | 458 ms | 0 |
| 14:45 | 0 | 0.0 | 496 ms | 0 |
| 15:00 | 0 | 0.0 | 715 ms | 0 |
| 15:15 | 0 | 0.0 | 534 ms | 0 |
| 15:30 | 0 | 0.0 | 702 ms | 0 |
| 15:45 | 0 | 0.0 | 647 ms | 0 |
| 16:00 | 0 | 0.0 | 328 ms | 0 |
| 16:15 | 0 | 0.0 | 793 ms | 0 |
| 16:30 | 0 | 0.0 | 1014 ms | 0 |
| 16:45 | 0 | 0.0 | 539 ms | 0 |
| 17:00 | 0 | 0.0 | 587 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
Embed this status badge · JSON
No outages on record for Nike 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 Nike goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
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.