User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Shopping
14ip.com · Shopping
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 3999 ms · 8 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:00 | 0 | 0.0 | 3789 ms | 0 |
| 03:15 | 0 | 0.0 | 3551 ms | 0 |
| 03:30 | 0 | 0.0 | 4083 ms | 0 |
| 03:45 | 0 | 0.0 | 3859 ms | 0 |
| 04:00 | 0 | 0.0 | 3924 ms | 0 |
| 04:15 | 0 | 0.0 | 3665 ms | 0 |
| 04:30 | 0 | 0.0 | 1225 ms | 0 |
| 04:45 | 0 | 0.0 | 1575 ms | 0 |
| 05:00 | 0 | 0.0 | 1688 ms | 0 |
| 05:15 | 0 | 0.0 | 1320 ms | 0 |
| 05:30 | 0 | 0.0 | 2609 ms | 0 |
| 05:45 | 0 | 0.0 | 1082 ms | 0 |
| 06:00 | 0 | 0.0 | 2861 ms | 0 |
| 06:15 | 0 | 0.0 | 2079 ms | 0 |
| 06:30 | 0 | 0.0 | 1321 ms | 0 |
| 06:45 | 0 | 0.0 | 2604 ms | 0 |
| 07:00 | 0 | 0.0 | 3938 ms | 0 |
| 07:15 | 0 | 0.0 | 1441 ms | 0 |
| 07:30 | 0 | 0.0 | 2303 ms | 0 |
| 07:45 | 0 | 0.0 | 3720 ms | 0 |
| 08:00 | 0 | 0.0 | 1724 ms | 0 |
| 08:15 | 0 | 0.0 | 1377 ms | 0 |
| 08:30 | 0 | 0.0 | 1335 ms | 0 |
| 08:45 | 0 | 0.0 | 1760 ms | 0 |
| 09:00 | 0 | 0.0 | 4062 ms | 0 |
| 09:15 | 0 | 0.0 | 2308 ms | 0 |
| 09:30 | 0 | 0.0 | 138 ms | 0 |
| 09:45 | 0 | 0.0 | 2791 ms | 0 |
| 10:00 | 0 | 0.0 | 2431 ms | 0 |
| 10:15 | 0 | 0.0 | 4177 ms | 0 |
| 10:30 | 0 | 0.0 | 2732 ms | 0 |
| 10:45 | 0 | 0.0 | 672 ms | 0 |
| 11:00 | 0 | 0.0 | 3494 ms | 0 |
| 11:15 | 0 | 0.0 | 3695 ms | 0 |
| 11:30 | 0 | 0.0 | 3568 ms | 0 |
| 11:45 | 0 | 0.0 | 3537 ms | 0 |
| 12:00 | 0 | 0.0 | 1253 ms | 0 |
| 12:15 | 0 | 0.0 | 2771 ms | 0 |
| 12:30 | 0 | 0.0 | 1329 ms | 0 |
| 12:45 | 0 | 0.0 | 1187 ms | 0 |
| 13:00 | 0 | 0.0 | 1262 ms | 0 |
| 13:15 | 0 | 0.0 | 3769 ms | 0 |
| 13:30 | 0 | 0.0 | 3960 ms | 0 |
| 13:45 | 0 | 0.0 | 2480 ms | 0 |
| 14:00 | 0 | 0.0 | 3491 ms | 0 |
| 14:15 | 0 | 0.0 | 3759 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.
No outages on record for ClearlyIP 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 ClearlyIP goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send ClearlyIP alerts to Slack, Discord or a webhook — free.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
If ClearlyIP is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on ClearlyIP's side.
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.