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 19 min ago. Last stored result reached it in 162 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 388 ms | 0 |
| Mon 17 | 0 | 0.0 | 333 ms | 0 |
| Mon 19 | 0 | 0.0 | 578 ms | 0 |
| Mon 21 | 0 | 0.0 | 339 ms | 0 |
| Mon 23 | 0 | 0.0 | 386 ms | 0 |
| Tue 01 | 0 | 0.0 | 306 ms | 0 |
| Tue 03 | 0 | 0.0 | 255 ms | 0 |
| Tue 06 | 0 | 0.0 | 441 ms | 0 |
| Tue 08 | 0 | 0.0 | 184 ms | 0 |
| Tue 10 | 0 | 0.0 | 206 ms | 0 |
| Tue 12 | 0 | 0.0 | 276 ms | 0 |
| Tue 14 | 0 | 0.0 | 252 ms | 0 |
| Tue 16 | 0 | 0.0 | 261 ms | 0 |
| Tue 19 | 0 | 0.0 | 275 ms | 0 |
| Tue 21 | 0 | 0.0 | 427 ms | 0 |
| Tue 23 | 0 | 0.0 | 393 ms | 0 |
| Wed 01 | 0 | 0.0 | 461 ms | 0 |
| Wed 04 | 0 | 0.0 | 241 ms | 0 |
| Wed 06 | 0 | 0.0 | 472 ms | 0 |
| Wed 08 | 0 | 0.0 | 196 ms | 0 |
| Wed 10 | 0 | 0.0 | 229 ms | 0 |
| Wed 13 | 0 | 0.0 | 227 ms | 0 |
| Wed 15 | 0 | 0.0 | 258 ms | 0 |
| Wed 17 | 0 | 0.0 | 493 ms | 0 |
| Wed 19 | 0 | 0.0 | 247 ms | 0 |
| Wed 21 | 0 | 0.0 | 195 ms | 0 |
| Wed 23 | 0 | 0.0 | 371 ms | 0 |
| Thu 01 | 0 | 0.0 | 247 ms | 0 |
| Thu 04 | 0 | 0.0 | 283 ms | 0 |
| Thu 06 | 0 | 0.0 | 183 ms | 0 |
| Thu 08 | 0 | 0.0 | 522 ms | 0 |
| Thu 10 | 0 | 0.0 | 260 ms | 0 |
| Thu 12 | 0 | 0.0 | 191 ms | 0 |
| Thu 14 | 0 | 0.0 | 327 ms | 0 |
| Thu 16 | 0 | 0.0 | 379 ms | 0 |
| Thu 18 | 0 | 0.0 | 309 ms | 0 |
| Thu 20 | 0 | 0.0 | 367 ms | 0 |
| Thu 22 | 0 | 0.0 | 300 ms | 0 |
| Fri 00 | 0 | 0.0 | 422 ms | 0 |
| Fri 01 | 0 | 0.0 | 270 ms | 0 |
| Fri 03 | 0 | 0.0 | 384 ms | 0 |
| Fri 05 | 0 | 0.0 | 205 ms | 0 |
| Fri 08 | 0 | 0.0 | 213 ms | 0 |
| Fri 10 | 0 | 0.0 | 192 ms | 0 |
| Fri 11 | 0 | 0.0 | 221 ms | 0 |
| Fri 13 | 0 | 0.0 | 202 ms | 0 |
| Fri 15 | 0 | 0.0 | 162 ms | 0 |
| Fri 17 | 0 | 0.0 | 313 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 iSpot 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 iSpot goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send iSpot alerts to Slack, Discord or a webhook — free.
We track iSpot (ispot.tv) as part of the Entertainment group. Struggling to prove and optimize TV ad performance? Fast, accurate and actionable measurement across linear and streaming is the key to TV advertising success. Say hello to the new standard for TV ad measurement.
iSpot publishes an official status page at status.ispot.tv; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong 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: 264 ms average, 162–422 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public iSpot incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
264 ms on average over the last 24 hours (162–422 ms).
Yes, at https://status.ispot.tv.
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 iSpot here at once, the problem is on iSpot'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 iSpot. 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.