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 33 min ago. Last stored result reached it in 141 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 06 | 0 | 0.0 | 75 ms | 0 |
| Mon 08 | 0 | 0.0 | 200 ms | 0 |
| Mon 10 | 0 | 0.0 | 118 ms | 0 |
| Mon 12 | 0 | 0.0 | 70 ms | 0 |
| Mon 14 | 0 | 0.0 | 93 ms | 0 |
| Mon 16 | 0 | 0.0 | 156 ms | 0 |
| Mon 19 | 0 | 0.0 | 226 ms | 0 |
| Mon 21 | 0 | 0.0 | 234 ms | 0 |
| Mon 23 | 0 | 0.0 | 98 ms | 0 |
| Tue 01 | 0 | 0.0 | 195 ms | 0 |
| Tue 03 | 0 | 0.0 | 119 ms | 0 |
| Tue 05 | 0 | 0.0 | 89 ms | 0 |
| Tue 07 | 0 | 0.0 | 242 ms | 0 |
| Tue 09 | 0 | 0.0 | 81 ms | 0 |
| Tue 11 | 0 | 0.0 | 92 ms | 0 |
| Tue 14 | 0 | 0.0 | 117 ms | 0 |
| Tue 16 | 0 | 0.0 | 187 ms | 0 |
| Tue 18 | 0 | 0.0 | 112 ms | 0 |
| Tue 20 | 0 | 0.0 | 113 ms | 0 |
| Tue 23 | 0 | 0.0 | 175 ms | 0 |
| Wed 01 | 0 | 0.0 | 267 ms | 0 |
| Wed 03 | 0 | 0.0 | 76 ms | 0 |
| Wed 05 | 0 | 0.0 | 56 ms | 0 |
| Wed 08 | 0 | 0.0 | 79 ms | 0 |
| Wed 10 | 0 | 0.0 | 67 ms | 0 |
| Wed 12 | 0 | 0.0 | 99 ms | 0 |
| Wed 14 | 0 | 0.0 | 121 ms | 0 |
| Wed 16 | 0 | 0.0 | 114 ms | 0 |
| Wed 18 | 0 | 0.0 | 186 ms | 0 |
| Wed 21 | 0 | 0.0 | 189 ms | 0 |
| Wed 23 | 0 | 0.0 | 97 ms | 0 |
| Thu 01 | 0 | 0.0 | 152 ms | 0 |
| Thu 03 | 0 | 0.0 | 60 ms | 0 |
| Thu 05 | 0 | 0.0 | 121 ms | 0 |
| Thu 07 | 0 | 0.0 | 68 ms | 0 |
| Thu 09 | 0 | 0.0 | 105 ms | 0 |
| Thu 11 | 0 | 0.0 | 99 ms | 0 |
| Thu 13 | 0 | 0.0 | 105 ms | 0 |
| Thu 15 | 0 | 0.0 | 89 ms | 0 |
| Thu 17 | 0 | 0.0 | 114 ms | 0 |
| Thu 19 | 0 | 0.0 | 123 ms | 0 |
| Thu 21 | 0 | 0.0 | 108 ms | 0 |
| Thu 23 | 0 | 0.0 | 98 ms | 0 |
| Fri 00 | 0 | 0.0 | 144 ms | 0 |
| Fri 02 | 0 | 0.0 | 184 ms | 0 |
| Fri 04 | 0 | 0.0 | 70 ms | 0 |
| Fri 06 | 0 | 0.0 | 227 ms | 0 |
| Fri 08 | 0 | 0.0 | 141 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for ByteSize 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 ByteSize goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send ByteSize alerts to Slack, Discord or a webhook — free.
We track ByteSize (bytesize.me) as part of the Entertainment group. Create a link-in-bio page that embeds your videos, music, posts, products, and links so fans can explore everything you make in one place.
ByteSize publishes an official status page at status.bytesize.me; 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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 124 ms average, 70–227 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public ByteSize incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
124 ms on average over the last 24 hours (70–227 ms).
Yes, at https://status.bytesize.me.
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 ByteSize here at once, the problem is on ByteSize'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 ByteSize. 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.