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 4 min ago. Last stored result reached it in 696 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 04 | 0 | 0.0 | 788 ms | 0 |
| Tue 06 | 0 | 0.0 | 969 ms | 0 |
| Tue 08 | 0 | 0.0 | 814 ms | 0 |
| Tue 10 | 0 | 0.0 | 900 ms | 0 |
| Tue 12 | 0 | 0.0 | 898 ms | 0 |
| Tue 14 | 0 | 0.0 | 889 ms | 0 |
| Tue 17 | 0 | 0.0 | 1043 ms | 0 |
| Tue 19 | 0 | 0.0 | 938 ms | 0 |
| Tue 21 | 0 | 0.0 | 1525 ms | 0 |
| Tue 23 | 0 | 0.0 | 1066 ms | 0 |
| Wed 02 | 0 | 0.0 | 937 ms | 0 |
| Wed 04 | 0 | 0.0 | 913 ms | 0 |
| Wed 06 | 0 | 0.0 | 842 ms | 0 |
| Wed 08 | 0 | 0.0 | 940 ms | 0 |
| Wed 11 | 0 | 0.0 | 737 ms | 0 |
| Wed 13 | 0 | 0.0 | 1046 ms | 0 |
| Wed 15 | 0 | 0.0 | 1000 ms | 0 |
| Wed 17 | 0 | 0.0 | 756 ms | 0 |
| Wed 19 | 0 | 0.0 | 773 ms | 0 |
| Wed 21 | 0 | 0.0 | 969 ms | 0 |
| Thu 00 | 0 | 0.0 | 775 ms | 0 |
| Thu 02 | 0 | 0.0 | 785 ms | 0 |
| Thu 04 | 0 | 0.0 | 832 ms | 0 |
| Thu 06 | 0 | 0.0 | 801 ms | 0 |
| Thu 08 | 0 | 0.0 | 974 ms | 0 |
| Thu 10 | 0 | 0.0 | 889 ms | 0 |
| Thu 12 | 0 | 0.0 | 837 ms | 0 |
| Thu 14 | 0 | 0.0 | 959 ms | 0 |
| Thu 16 | 0 | 0.0 | 1315 ms | 0 |
| Thu 18 | 0 | 0.0 | 821 ms | 0 |
| Thu 20 | 0 | 0.0 | 1129 ms | 0 |
| Thu 22 | 0 | 0.0 | 907 ms | 0 |
| Fri 01 | 0 | 0.0 | 920 ms | 0 |
| Fri 03 | 0 | 0.0 | 975 ms | 0 |
| Fri 05 | 0 | 0.0 | 767 ms | 0 |
| Fri 07 | 0 | 0.0 | 900 ms | 0 |
| Fri 08 | 0 | 0.0 | 929 ms | 0 |
| Fri 10 | 0 | 0.0 | 827 ms | 0 |
| Fri 11 | 0 | 0.0 | 1138 ms | 0 |
| Fri 13 | 0 | 0.0 | 842 ms | 0 |
| Fri 15 | 0 | 0.0 | 1008 ms | 0 |
| Fri 17 | 0 | 0.0 | 1070 ms | 0 |
| Fri 18 | 0 | 0.0 | 857 ms | 0 |
| Fri 20 | 0 | 0.0 | 960 ms | 0 |
| Fri 21 | 0 | 0.0 | 835 ms | 0 |
| Fri 23 | 0 | 0.0 | 919 ms | 0 |
| Sat 00 | 0 | 0.0 | 858 ms | 0 |
| Sat 02 | 0 | 0.0 | 696 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 Wipster 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 Wipster goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Wipster alerts to Slack, Discord or a webhook — free.
We track Wipster (wipster.io) as part of the Entertainment group. Quickly and easily share and get feedback on video projects. Share media, collect feedback, manage reviews, and deliver finished work faster.
Wipster publishes an official status page at status.wipster.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: 901 ms average, 696–1138 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 Wipster incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
901 ms on average over the last 24 hours (696–1138 ms).
Yes, at https://status.wipster.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 Wipster here at once, the problem is on Wipster'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 Wipster. 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.