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 45 min ago. Last stored result reached it in 313 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 409 ms | 0 |
| Nov 7 | 0 | 0.0 | 262 ms | 0 |
| Nov 7 | 0 | 0.0 | 243 ms | 0 |
| Nov 7 | 0 | 0.0 | 194 ms | 0 |
| Nov 7 | 0 | 0.0 | 414 ms | 0 |
| Nov 8 | 0 | 0.0 | 298 ms | 0 |
| Nov 8 | 0 | 0.0 | 282 ms | 0 |
| Nov 8 | 0 | 0.0 | 227 ms | 0 |
| Nov 8 | 0 | 0.0 | 322 ms | 0 |
| Nov 9 | 0 | 0.0 | 342 ms | 0 |
| Nov 9 | 0 | 0.0 | 348 ms | 0 |
| Nov 9 | 0 | 0.0 | 333 ms | 0 |
| Nov 9 | 0 | 0.0 | 386 ms | 0 |
| Nov 10 | 0 | 0.0 | 281 ms | 0 |
| Nov 10 | 0 | 0.0 | 206 ms | 0 |
| Nov 10 | 0 | 0.0 | 264 ms | 0 |
| Nov 10 | 0 | 0.0 | 361 ms | 0 |
| Nov 11 | 0 | 0.0 | 351 ms | 0 |
| Nov 11 | 0 | 0.0 | 229 ms | 0 |
| Nov 11 | 0 | 0.0 | 258 ms | 0 |
| Nov 11 | 0 | 0.0 | 247 ms | 0 |
| Nov 12 | 0 | 0.0 | 265 ms | 0 |
| Nov 12 | 0 | 0.0 | 260 ms | 0 |
| Nov 12 | 0 | 0.0 | 327 ms | 0 |
| Nov 12 | 0 | 0.0 | 309 ms | 0 |
| Nov 13 | 0 | 0.0 | 327 ms | 0 |
| Nov 13 | 0 | 0.0 | 209 ms | 0 |
| Nov 13 | 0 | 0.0 | 202 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.