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 2 hr ago. Last stored result reached it in 86 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 17 | 0 | 0.0 | 125 ms | 0 |
| Tue 20 | 0 | 0.0 | 193 ms | 0 |
| Tue 22 | 0 | 0.0 | 89 ms | 0 |
| Wed 00 | 0 | 0.0 | 71 ms | 0 |
| Wed 02 | 0 | 0.0 | 118 ms | 0 |
| Wed 05 | 0 | 0.0 | 85 ms | 0 |
| Wed 07 | 0 | 0.0 | 124 ms | 0 |
| Wed 09 | 0 | 0.0 | 162 ms | 0 |
| Wed 12 | 0 | 0.0 | 79 ms | 0 |
| Wed 14 | 0 | 0.0 | 95 ms | 0 |
| Wed 16 | 0 | 0.0 | 241 ms | 0 |
| Wed 18 | 0 | 0.0 | 481 ms | 0 |
| Wed 20 | 0 | 0.0 | 100 ms | 0 |
| Wed 22 | 0 | 0.0 | 75 ms | 0 |
| Thu 00 | 0 | 0.0 | 121 ms | 0 |
| Thu 03 | 0 | 0.0 | 109 ms | 0 |
| Thu 05 | 0 | 0.0 | 216 ms | 0 |
| Thu 07 | 0 | 0.0 | 85 ms | 0 |
| Thu 09 | 0 | 0.0 | 177 ms | 0 |
| Thu 11 | 0 | 0.0 | 56 ms | 0 |
| Thu 13 | 0 | 0.0 | 207 ms | 0 |
| Thu 15 | 0 | 0.0 | 265 ms | 0 |
| Thu 17 | 0 | 0.0 | 139 ms | 0 |
| Thu 19 | 0 | 0.0 | 395 ms | 0 |
| Thu 21 | 0 | 0.0 | 83 ms | 0 |
| Thu 23 | 0 | 0.0 | 94 ms | 0 |
| Fri 00 | 0 | 0.0 | 79 ms | 0 |
| Fri 02 | 0 | 0.0 | 120 ms | 0 |
| Fri 04 | 0 | 0.0 | 198 ms | 0 |
| Fri 06 | 0 | 0.0 | 258 ms | 0 |
| Fri 08 | 0 | 0.0 | 72 ms | 0 |
| Fri 10 | 0 | 0.0 | 117 ms | 0 |
| Fri 12 | 0 | 0.0 | 97 ms | 0 |
| Fri 14 | 0 | 0.0 | 67 ms | 0 |
| Fri 16 | 0 | 0.0 | 81 ms | 0 |
| Fri 17 | 0 | 0.0 | 122 ms | 0 |
| Fri 18 | 0 | 0.0 | 28 ms | 0 |
| Fri 19 | 0 | 0.0 | 318 ms | 0 |
| Fri 20 | 0 | 0.0 | 78 ms | 0 |
| Fri 22 | 0 | 0.0 | 106 ms | 0 |
| Sat 00 | 0 | 0.0 | 223 ms | 0 |
| Sat 02 | 0 | 0.0 | 105 ms | 0 |
| Sat 04 | 0 | 0.0 | 56 ms | 0 |
| Sat 06 | 0 | 0.0 | 73 ms | 0 |
| Sat 07 | 0 | 0.0 | 72 ms | 0 |
| Sat 08 | 0 | 0.0 | 68 ms | 0 |
| Sat 10 | 0 | 0.0 | 55 ms | 0 |
| Sat 13 | 0 | 0.0 | 86 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 Screendesk 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 Screendesk goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Screendesk alerts to Slack, Discord or a webhook — free.
Screendesk, at screendesk.io, is one of the Entertainment services we monitor. Request customer screen recordings, share video walkthroughs, and join live calls from your helpdesk. Built for support, customer success, QA, and engineering.
Screendesk publishes an official status page at status.screendesk.io; 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: 100 ms average, 28–318 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Screendesk incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
100 ms on average over the last 24 hours (28–318 ms).
Yes, at https://status.screendesk.io.
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 Screendesk here at once, the problem is on Screendesk'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 Screendesk. 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.