User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Entertainment
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps 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. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 22 min ago. Last stored result reached it in 180 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 22 | 0 | 0.0 | 103 ms | 0 |
| Tue 00 | 0 | 0.0 | 85 ms | 0 |
| Tue 02 | 0 | 0.0 | 100 ms | 0 |
| Tue 04 | 0 | 0.0 | 79 ms | 0 |
| Tue 06 | 0 | 0.0 | 139 ms | 0 |
| Tue 08 | 0 | 0.0 | 85 ms | 0 |
| Tue 10 | 0 | 0.0 | 131 ms | 0 |
| Tue 12 | 0 | 0.0 | 116 ms | 0 |
| Tue 15 | 0 | 0.0 | 98 ms | 0 |
| Tue 17 | 0 | 0.0 | 67 ms | 0 |
| Tue 19 | 0 | 0.0 | 58 ms | 0 |
| Tue 21 | 0 | 0.0 | 55 ms | 0 |
| Wed 00 | 0 | 0.0 | 40 ms | 0 |
| Wed 02 | 0 | 0.0 | 150 ms | 0 |
| Wed 04 | 0 | 0.0 | 81 ms | 0 |
| Wed 06 | 0 | 0.0 | 49 ms | 0 |
| Wed 08 | 0 | 0.0 | 40 ms | 0 |
| Wed 11 | 0 | 0.0 | 52 ms | 0 |
| Wed 13 | 0 | 0.0 | 117 ms | 0 |
| Wed 15 | 0 | 0.0 | 96 ms | 0 |
| Wed 17 | 0 | 0.0 | 133 ms | 0 |
| Wed 19 | 0 | 0.0 | 139 ms | 0 |
| Wed 21 | 0 | 0.0 | 203 ms | 0 |
| Wed 22 | 0 | 0.0 | 16 ms | 0 |
| Thu 00 | 0 | 0.0 | 89 ms | 0 |
| Thu 02 | 0 | 0.0 | 141 ms | 0 |
| Thu 04 | 0 | 0.0 | 132 ms | 0 |
| Thu 06 | 0 | 0.0 | 110 ms | 0 |
| Thu 08 | 0 | 0.0 | 149 ms | 0 |
| Thu 10 | 0 | 0.0 | 100 ms | 0 |
| Thu 12 | 0 | 0.0 | 69 ms | 0 |
| Thu 14 | 0 | 0.0 | 104 ms | 0 |
| Thu 16 | 0 | 0.0 | 113 ms | 0 |
| Thu 18 | 0 | 0.0 | 38 ms | 0 |
| Thu 20 | 0 | 0.0 | 109 ms | 0 |
| Thu 22 | 0 | 0.0 | 112 ms | 0 |
| Fri 00 | 0 | 0.0 | 114 ms | 0 |
| Fri 03 | 0 | 0.0 | 91 ms | 0 |
| Fri 05 | 0 | 0.0 | 123 ms | 0 |
| Fri 07 | 0 | 0.0 | 55 ms | 0 |
| Fri 09 | 0 | 0.0 | 120 ms | 0 |
| Fri 10 | 0 | 0.0 | 189 ms | 0 |
| Fri 11 | 0 | 0.0 | 42 ms | 0 |
| Fri 13 | 0 | 0.0 | 108 ms | 0 |
| Fri 14 | 0 | 0.0 | 117 ms | 0 |
| Fri 16 | 0 | 0.0 | 56 ms | 0 |
| Fri 17 | 0 | 0.0 | 98 ms | 0 |
| Fri 18 | 0 | 0.0 | 180 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for CHeKT 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 CHeKT goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send CHeKT alerts to Slack, Discord or a webhook — free.
CHeKT, at chekt.com, is one of the Entertainment services we monitor. Detect, deter, and stop crime before it happens. CHeKT is leading the way with Proactive Visual Security. LEARN MORE FIND A PROVIDER Goodbye passive video systems.Hello, proactive visual security. With CHeKT, video isn’t an afterthought — it’s the frontline. Traditional video systems are reactive by design. Video footage is reviewed after the fact — too […]
CHeKT publishes an official status page at status.chekt.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with entertainment services: streams buffering or not starting, playback errors, and app sign-in problems.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 108 ms average, 42–189 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public CHeKT incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
108 ms on average over the last 24 hours (42–189 ms).
Yes, at https://status.chekt.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For entertainment services, watch for streams buffering or not starting, playback errors, and app sign-in problems. If many people report CHeKT here at once, the problem is on CHeKT's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with CHeKT. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.