User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
cradlepoint.com · Productivity
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 3439 ms · 6 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 07:00 | 0 | 0.0 | 1224 ms | 0 |
| 07:15 | 0 | 0.0 | 1197 ms | 0 |
| 07:30 | 0 | 0.0 | 948 ms | 0 |
| 07:45 | 0 | 0.0 | 837 ms | 0 |
| 08:00 | 0 | 0.0 | 1227 ms | 0 |
| 08:15 | 0 | 0.0 | 1332 ms | 0 |
| 08:30 | 0 | 0.0 | 907 ms | 0 |
| 08:45 | 0 | 0.0 | 1483 ms | 0 |
| 09:00 | 0 | 0.0 | 1096 ms | 0 |
| 09:15 | 0 | 0.0 | 563 ms | 0 |
| 09:30 | 0 | 0.0 | 343 ms | 0 |
| 09:45 | 0 | 0.0 | 1343 ms | 0 |
| 10:00 | 0 | 0.0 | 1112 ms | 0 |
| 10:15 | 0 | 0.0 | 1011 ms | 0 |
| 10:30 | 0 | 0.0 | 1035 ms | 0 |
| 10:45 | 0 | 0.0 | 637 ms | 0 |
| 11:00 | 0 | 0.0 | 986 ms | 0 |
| 11:15 | 0 | 0.0 | 858 ms | 0 |
| 11:30 | 0 | 0.0 | 980 ms | 0 |
| 11:45 | 0 | 0.0 | 685 ms | 0 |
| 12:00 | 0 | 0.0 | 1175 ms | 0 |
| 12:15 | 0 | 0.0 | 1207 ms | 0 |
| 12:30 | 0 | 0.0 | 2149 ms | 0 |
| 12:45 | 0 | 0.0 | 506 ms | 0 |
| 13:00 | 0 | 0.0 | 887 ms | 0 |
| 13:15 | 0 | 0.0 | 1280 ms | 0 |
| 13:30 | 0 | 0.0 | 1064 ms | 0 |
| 13:45 | 0 | 0.0 | 948 ms | 0 |
| 14:00 | 0 | 0.0 | 780 ms | 0 |
| 14:15 | 0 | 0.0 | 1043 ms | 0 |
| 14:30 | 0 | 0.0 | 865 ms | 0 |
| 14:45 | 0 | 0.0 | 1145 ms | 0 |
| 15:00 | 0 | 0.0 | 996 ms | 0 |
| 15:15 | 0 | 0.0 | 1222 ms | 0 |
| 15:30 | 0 | 0.0 | 633 ms | 0 |
| 15:45 | 0 | 0.0 | 1261 ms | 0 |
| 16:00 | 0 | 0.0 | 1260 ms | 0 |
| 16:15 | 0 | 0.0 | 514 ms | 0 |
| 16:30 | 0 | 0.0 | 616 ms | 0 |
| 16:45 | 0 | 0.0 | 1096 ms | 0 |
| 17:00 | 0 | 0.0 | 1255 ms | 0 |
| 17:15 | 0 | 0.0 | 842 ms | 0 |
| 17:30 | 0 | 0.0 | 632 ms | 0 |
| 17:45 | 0 | 0.0 | 1108 ms | 0 |
| 18:00 | 0 | 0.0 | 1386 ms | 0 |
| 18:15 | 0 | 0.0 | 1293 ms | 0 |
| 18:30 | 0 | 0.0 | 1372 ms | 0 |
| 18:45 | 0 | 0.0 | 2099 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 Cradlepoint 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 Cradlepoint goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Cradlepoint 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 Cradlepoint 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 Cradlepoint'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.