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 1 hr ago. Last stored result reached it in 262 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 21 | 0 | 0.0 | 380 ms | 0 |
| Mon 23 | 0 | 0.0 | 273 ms | 0 |
| Tue 01 | 0 | 0.0 | 330 ms | 0 |
| Tue 03 | 0 | 0.0 | 381 ms | 0 |
| Tue 06 | 0 | 0.0 | 475 ms | 0 |
| Tue 08 | 0 | 0.0 | 490 ms | 0 |
| Tue 10 | 0 | 0.0 | 348 ms | 0 |
| Tue 12 | 0 | 0.0 | 360 ms | 0 |
| Tue 14 | 0 | 0.0 | 436 ms | 0 |
| Tue 17 | 0 | 0.0 | 353 ms | 0 |
| Tue 19 | 0 | 0.0 | 317 ms | 0 |
| Tue 21 | 0 | 0.0 | 301 ms | 0 |
| Tue 23 | 0 | 0.0 | 437 ms | 0 |
| Wed 01 | 0 | 0.0 | 379 ms | 0 |
| Wed 04 | 0 | 0.0 | 339 ms | 0 |
| Wed 06 | 0 | 0.0 | 420 ms | 0 |
| Wed 08 | 0 | 0.0 | 373 ms | 0 |
| Wed 11 | 0 | 0.0 | 315 ms | 0 |
| Wed 13 | 0 | 0.0 | 359 ms | 0 |
| Wed 15 | 0 | 0.0 | 306 ms | 0 |
| Wed 17 | 0 | 0.0 | 320 ms | 0 |
| Wed 19 | 0 | 0.0 | 355 ms | 0 |
| Wed 21 | 0 | 0.0 | 196 ms | 0 |
| Thu 00 | 0 | 0.0 | 422 ms | 0 |
| Thu 02 | 0 | 0.0 | 351 ms | 0 |
| Thu 04 | 0 | 0.0 | 387 ms | 0 |
| Thu 06 | 0 | 0.0 | 229 ms | 0 |
| Thu 08 | 0 | 0.0 | 414 ms | 0 |
| Thu 10 | 0 | 0.0 | 395 ms | 0 |
| Thu 12 | 0 | 0.0 | 390 ms | 0 |
| Thu 14 | 0 | 0.0 | 342 ms | 0 |
| Thu 16 | 0 | 0.0 | 430 ms | 0 |
| Thu 17 | 0 | 0.0 | 368 ms | 0 |
| Thu 19 | 0 | 0.0 | 422 ms | 0 |
| Thu 21 | 0 | 0.0 | 381 ms | 0 |
| Fri 00 | 0 | 0.0 | 376 ms | 0 |
| Fri 02 | 0 | 0.0 | 298 ms | 0 |
| Fri 04 | 0 | 0.0 | 227 ms | 0 |
| Fri 06 | 0 | 0.0 | 298 ms | 0 |
| Fri 08 | 0 | 0.0 | 391 ms | 0 |
| Fri 10 | 0 | 0.0 | 363 ms | 0 |
| Fri 11 | 0 | 0.0 | 327 ms | 0 |
| Fri 13 | 0 | 0.0 | 331 ms | 0 |
| Fri 15 | 0 | 0.0 | 328 ms | 0 |
| Fri 17 | 0 | 0.0 | 374 ms | 0 |
| Fri 18 | 0 | 0.0 | 319 ms | 0 |
| Fri 19 | 0 | 0.0 | 638 ms | 0 |
| Fri 21 | 0 | 0.0 | 262 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 Vidow 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 Vidow goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Vidow alerts to Slack, Discord or a webhook — free.
Vidow, at vidow.io, is one of the Entertainment services we monitor. Video Downloader Plus is the best video downloader Chrome extension. Detect and download videos from any website in 4K, convert m3u8 streams to MP4, and cast to Chromecast. Free Chrome extension with 1M+ users.
Vidow publishes an official status page at status.vidow.io; when we can read it, its incident level is folded into the status shown here.
Common problems for 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: 339 ms average, 224–638 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 Vidow incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
339 ms on average over the last 24 hours (224–638 ms).
Yes, at https://status.vidow.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 Vidow here at once, the problem is on Vidow'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 Vidow. 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.