User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Telecom
sitespect.com · Telecom
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 401 ms · 2 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:15 | 0 | 0.0 | 433 ms | 0 |
| 03:30 | 0 | 0.0 | 1093 ms | 0 |
| 03:45 | 0 | 0.0 | 657 ms | 0 |
| 04:00 | 0 | 0.0 | 508 ms | 0 |
| 04:15 | 0 | 0.0 | 952 ms | 0 |
| 04:30 | 0 | 0.0 | 1799 ms | 0 |
| 04:45 | 0 | 0.0 | 406 ms | 0 |
| 05:00 | 0 | 0.0 | 303 ms | 0 |
| 05:15 | 0 | 0.0 | 902 ms | 0 |
| 05:30 | 0 | 0.0 | 412 ms | 0 |
| 05:45 | 0 | 0.0 | 772 ms | 0 |
| 06:00 | 0 | 0.0 | 338 ms | 0 |
| 06:15 | 0 | 0.0 | 529 ms | 0 |
| 06:30 | 0 | 0.0 | 830 ms | 0 |
| 06:45 | 0 | 0.0 | 654 ms | 0 |
| 07:00 | 0 | 0.0 | 307 ms | 0 |
| 07:15 | 0 | 0.0 | 1029 ms | 0 |
| 07:30 | 0 | 0.0 | 715 ms | 0 |
| 07:45 | 0 | 0.0 | 508 ms | 0 |
| 08:00 | 0 | 0.0 | 735 ms | 0 |
| 08:15 | 0 | 0.0 | 281 ms | 0 |
| 08:30 | 0 | 0.0 | 1172 ms | 0 |
| 08:45 | 0 | 0.0 | 844 ms | 0 |
| 09:00 | 0 | 0.0 | 334 ms | 0 |
| 09:15 | 0 | 0.0 | 1072 ms | 0 |
| 09:30 | 0 | 0.0 | 571 ms | 0 |
| 09:45 | 0 | 0.0 | 544 ms | 0 |
| 10:00 | 0 | 0.0 | 844 ms | 0 |
| 10:15 | 0 | 0.0 | 434 ms | 0 |
| 10:30 | 0 | 0.0 | 319 ms | 0 |
| 10:45 | 0 | 0.0 | 335 ms | 0 |
| 11:00 | 0 | 0.0 | 449 ms | 0 |
| 11:15 | 0 | 0.0 | 641 ms | 0 |
| 11:30 | 0 | 0.0 | 543 ms | 0 |
| 11:45 | 0 | 0.0 | 478 ms | 0 |
| 12:00 | 0 | 0.0 | 557 ms | 0 |
| 12:15 | 0 | 0.0 | 775 ms | 0 |
| 12:30 | 0 | 0.0 | 1240 ms | 0 |
| 12:45 | 0 | 0.0 | 541 ms | 0 |
| 13:00 | 0 | 0.0 | 309 ms | 0 |
| 13:15 | 0 | 0.0 | 304 ms | 0 |
| 13:30 | 0 | 0.0 | 2056 ms | 0 |
| 13:45 | 0 | 0.0 | 1098 ms | 0 |
| 14:00 | 0 | 0.0 | 827 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 SiteSpect 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 SiteSpect goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send SiteSpect 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 SiteSpect 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 SiteSpect'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.