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 17 min ago. Last stored result reached it in 159 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 135 ms | 0 |
| Mon 17 | 0 | 0.0 | 83 ms | 0 |
| Mon 19 | 0 | 0.0 | 137 ms | 0 |
| Mon 21 | 0 | 0.0 | 71 ms | 0 |
| Mon 23 | 0 | 0.0 | 197 ms | 0 |
| Tue 01 | 0 | 0.0 | 128 ms | 0 |
| Tue 03 | 0 | 0.0 | 91 ms | 0 |
| Tue 06 | 0 | 0.0 | 127 ms | 0 |
| Tue 08 | 0 | 0.0 | 137 ms | 0 |
| Tue 10 | 0 | 0.0 | 123 ms | 0 |
| Tue 12 | 0 | 0.0 | 92 ms | 0 |
| Tue 14 | 0 | 0.0 | 100 ms | 0 |
| Tue 17 | 0 | 0.0 | 158 ms | 0 |
| Tue 19 | 0 | 0.0 | 91 ms | 0 |
| Tue 21 | 0 | 0.0 | 115 ms | 0 |
| Tue 23 | 0 | 0.0 | 199 ms | 0 |
| Wed 01 | 0 | 0.0 | 76 ms | 0 |
| Wed 04 | 0 | 0.0 | 180 ms | 0 |
| Wed 06 | 0 | 0.0 | 102 ms | 0 |
| Wed 08 | 0 | 0.0 | 90 ms | 0 |
| Wed 11 | 0 | 0.0 | 76 ms | 0 |
| Wed 13 | 0 | 0.0 | 175 ms | 0 |
| Wed 15 | 0 | 0.0 | 75 ms | 0 |
| Wed 17 | 0 | 0.0 | 82 ms | 0 |
| Wed 19 | 0 | 0.0 | 167 ms | 0 |
| Wed 21 | 0 | 0.0 | 139 ms | 0 |
| Wed 23 | 0 | 0.0 | 259 ms | 0 |
| Thu 02 | 0 | 0.0 | 31 ms | 0 |
| Thu 04 | 0 | 0.0 | 176 ms | 0 |
| Thu 06 | 0 | 0.0 | 211 ms | 0 |
| Thu 08 | 0 | 0.0 | 93 ms | 0 |
| Thu 10 | 0 | 0.0 | 183 ms | 0 |
| Thu 12 | 0 | 0.0 | 122 ms | 0 |
| Thu 14 | 0 | 0.0 | 88 ms | 0 |
| Thu 16 | 0 | 0.0 | 152 ms | 0 |
| Thu 18 | 0 | 0.0 | 70 ms | 0 |
| Thu 20 | 0 | 0.0 | 143 ms | 0 |
| Thu 21 | 0 | 0.0 | 206 ms | 0 |
| Thu 23 | 0 | 0.0 | 144 ms | 0 |
| Fri 01 | 0 | 0.0 | 173 ms | 0 |
| Fri 03 | 0 | 0.0 | 179 ms | 0 |
| Fri 05 | 0 | 0.0 | 81 ms | 0 |
| Fri 08 | 0 | 0.0 | 80 ms | 0 |
| Fri 10 | 0 | 0.0 | 94 ms | 0 |
| Fri 12 | 0 | 0.0 | 91 ms | 0 |
| Fri 14 | 0 | 0.0 | 129 ms | 0 |
| Fri 16 | 0 | 0.0 | 159 ms | 0 |
| Fri 17 | 0 | 0.0 | 147 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 SightCall 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 SightCall goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send SightCall alerts to Slack, Discord or a webhook — free.
SightCall, at sightcall.com, is one of the Entertainment services we monitor. SightCall’s video intelligence platform helps service teams solve issues, capture expert knowledge and turn data into operational insights.
SightCall publishes an official status page at status.sightcall.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: 128 ms average, 70–206 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 SightCall incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
128 ms on average over the last 24 hours (70–206 ms).
Yes, at https://status.sightcall.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 SightCall here at once, the problem is on SightCall'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 SightCall. 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.