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 55 min ago. Last stored result reached it in 51 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 114 ms | 0 |
| Nov 7 | 0 | 0.0 | 739 ms | 0 |
| Nov 7 | 0 | 0.0 | 740 ms | 0 |
| Nov 7 | 0 | 0.0 | 764 ms | 0 |
| Nov 7 | 0 | 0.0 | 766 ms | 0 |
| Nov 8 | 0 | 0.0 | 873 ms | 0 |
| Nov 8 | 0 | 0.0 | 143 ms | 0 |
| Nov 8 | 0 | 0.0 | 706 ms | 0 |
| Nov 8 | 0 | 0.0 | 410 ms | 0 |
| Nov 9 | 0 | 0.0 | 234 ms | 0 |
| Nov 9 | 0 | 0.0 | 121 ms | 0 |
| Nov 9 | 0 | 0.0 | 356 ms | 0 |
| Nov 9 | 0 | 0.0 | 788 ms | 0 |
| Nov 10 | 0 | 0.0 | 53 ms | 0 |
| Nov 10 | 0 | 0.0 | 400 ms | 0 |
| Nov 10 | 0 | 0.0 | 118 ms | 0 |
| Nov 10 | 0 | 0.0 | 132 ms | 0 |
| Nov 11 | 0 | 0.0 | 419 ms | 0 |
| Nov 11 | 0 | 0.0 | 191 ms | 0 |
| Nov 11 | 0 | 0.0 | 124 ms | 0 |
| Nov 11 | 0 | 0.0 | 128 ms | 0 |
| Nov 12 | 0 | 0.0 | 86 ms | 0 |
| Nov 12 | 0 | 0.0 | 130 ms | 0 |
| Nov 12 | 0 | 0.0 | 118 ms | 0 |
| Nov 12 | 0 | 0.0 | 755 ms | 0 |
| Nov 13 | 0 | 0.0 | 90 ms | 0 |
| Nov 13 | 0 | 0.0 | 259 ms | 0 |
| Nov 13 | 0 | 0.0 | 516 ms | 0 |
| Nov 13 | 0 | 0.0 | 449 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 Hubhopper 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 Hubhopper goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Hubhopper alerts to Slack, Discord or a webhook — free.
We track Hubhopper (hubhopper.com) as part of the Entertainment group. Launch your podcast with free podcast application from Hubhopper, the best website to create podcast for streaming. Use our free podcast player to host on your website and reach 10000+ listeners. Monetize your content seamlessly.
Hubhopper publishes an official status page at status.hubhopper.com; 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: 397 ms average, 49–922 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Hubhopper incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
397 ms on average over the last 24 hours (49–922 ms).
Yes, at https://status.hubhopper.com.
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 Hubhopper here at once, the problem is on Hubhopper'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 Hubhopper. 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.