User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
pingplotter.cloud · Cloud & developer
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 1029 ms · 9 min ago.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 05:00 | 0 | 0.0 | 451 ms | 0 |
| 05:15 | 0 | 0.0 | 359 ms | 0 |
| 05:30 | 0 | 0.0 | 74 ms | 0 |
| 05:45 | 0 | 0.0 | 707 ms | 0 |
| 06:00 | 0 | 0.0 | 434 ms | 0 |
| 06:15 | 0 | 0.0 | 746 ms | 0 |
| 06:30 | 0 | 0.0 | 163 ms | 0 |
| 06:45 | 0 | 0.0 | 291 ms | 0 |
| 07:00 | 0 | 0.0 | 128 ms | 0 |
| 07:15 | 0 | 0.0 | 275 ms | 0 |
| 07:30 | 0 | 0.0 | 1176 ms | 0 |
| 07:45 | 0 | 0.0 | 507 ms | 0 |
| 08:00 | 0 | 0.0 | 353 ms | 0 |
| 08:15 | 0 | 0.0 | 937 ms | 0 |
| 08:30 | 0 | 0.0 | 618 ms | 0 |
| 08:45 | 0 | 0.0 | 542 ms | 0 |
| 09:00 | 0 | 0.0 | 202 ms | 0 |
| 09:15 | 0 | 0.0 | 598 ms | 0 |
| 09:30 | 0 | 0.0 | 496 ms | 0 |
| 09:45 | 0 | 0.0 | 418 ms | 0 |
| 10:00 | 0 | 0.0 | 237 ms | 0 |
| 10:15 | 0 | 0.0 | 800 ms | 0 |
| 10:30 | 0 | 0.0 | 1061 ms | 0 |
| 10:45 | 0 | 0.0 | 677 ms | 0 |
| 11:00 | 0 | 0.0 | 1151 ms | 0 |
| 11:15 | 0 | 0.0 | 1063 ms | 0 |
| 11:30 | 0 | 0.0 | 478 ms | 0 |
| 11:45 | 0 | 0.0 | 1277 ms | 0 |
| 12:00 | 0 | 0.0 | 1196 ms | 0 |
| 12:15 | 0 | 0.0 | 804 ms | 0 |
| 12:30 | 0 | 0.0 | 459 ms | 0 |
| 12:45 | 0 | 0.0 | 543 ms | 0 |
| 13:00 | 0 | 0.0 | 121 ms | 0 |
| 13:15 | 0 | 0.0 | 557 ms | 0 |
| 13:30 | 0 | 0.0 | 649 ms | 0 |
| 13:45 | 0 | 0.0 | 657 ms | 0 |
| 14:00 | 0 | 0.0 | 686 ms | 0 |
| 14:15 | 0 | 0.0 | 1094 ms | 0 |
| 14:30 | 0 | 0.0 | 186 ms | 0 |
| 14:45 | 0 | 0.0 | 530 ms | 0 |
| 15:00 | 0 | 0.0 | 625 ms | 0 |
| 15:15 | 0 | 0.0 | 507 ms | 0 |
| 15:30 | 0 | 0.0 | 930 ms | 0 |
| 15:45 | 0 | 0.0 | 558 ms | 0 |
| 16:00 | 0 | 0.0 | 476 ms | 0 |
| 16:15 | 0 | 0.0 | 225 ms | 0 |
| 16:30 | 0 | 0.0 | 261 ms | 0 |
| 16:45 | 0 | 0.0 | 1029 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 Pingplotter Cloud 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 Pingplotter Cloud goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Pingplotter Cloud 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 Pingplotter Cloud 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 Pingplotter Cloud'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.