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 2 hr ago. Last stored result reached it in 1060 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 14 | 0 | 0.0 | 589 ms | 0 |
| Mon 17 | 0 | 0.0 | 829 ms | 0 |
| Mon 19 | 0 | 0.0 | 936 ms | 0 |
| Mon 21 | 0 | 0.0 | 1006 ms | 0 |
| Mon 23 | 0 | 0.0 | 846 ms | 0 |
| Tue 01 | 0 | 0.0 | 955 ms | 0 |
| Tue 03 | 0 | 0.0 | 675 ms | 0 |
| Tue 05 | 0 | 0.0 | 573 ms | 0 |
| Tue 07 | 0 | 0.0 | 494 ms | 0 |
| Tue 09 | 0 | 0.0 | 641 ms | 0 |
| Tue 11 | 0 | 0.0 | 867 ms | 0 |
| Tue 14 | 0 | 0.0 | 689 ms | 0 |
| Tue 16 | 0 | 0.0 | 572 ms | 0 |
| Tue 18 | 0 | 0.0 | 1443 ms | 0 |
| Tue 20 | 0 | 0.0 | 769 ms | 0 |
| Tue 23 | 0 | 0.0 | 627 ms | 0 |
| Wed 01 | 0 | 0.0 | 820 ms | 0 |
| Wed 03 | 0 | 0.0 | 612 ms | 0 |
| Wed 05 | 0 | 0.0 | 830 ms | 0 |
| Wed 08 | 0 | 0.0 | 598 ms | 0 |
| Wed 10 | 0 | 0.0 | 444 ms | 0 |
| Wed 12 | 0 | 0.0 | 631 ms | 0 |
| Wed 14 | 0 | 0.0 | 710 ms | 0 |
| Wed 16 | 0 | 0.0 | 514 ms | 0 |
| Wed 18 | 0 | 0.0 | 1029 ms | 0 |
| Wed 21 | 0 | 0.0 | 775 ms | 0 |
| Wed 23 | 0 | 0.0 | 853 ms | 0 |
| Thu 01 | 0 | 0.0 | 897 ms | 0 |
| Thu 03 | 0 | 0.0 | 697 ms | 0 |
| Thu 05 | 0 | 0.0 | 682 ms | 0 |
| Thu 07 | 0 | 0.0 | 866 ms | 0 |
| Thu 09 | 0 | 0.0 | 858 ms | 0 |
| Thu 11 | 0 | 0.0 | 517 ms | 0 |
| Thu 13 | 0 | 0.0 | 640 ms | 0 |
| Thu 15 | 0 | 0.0 | 571 ms | 0 |
| Thu 17 | 0 | 0.0 | 753 ms | 0 |
| Thu 19 | 0 | 0.0 | 697 ms | 0 |
| Thu 21 | 0 | 0.0 | 761 ms | 0 |
| Fri 00 | 0 | 0.0 | 624 ms | 0 |
| Fri 02 | 0 | 0.0 | 938 ms | 0 |
| Fri 04 | 0 | 0.0 | 629 ms | 0 |
| Fri 06 | 0 | 0.0 | 805 ms | 0 |
| Fri 08 | 0 | 0.0 | 806 ms | 0 |
| Fri 10 | 0 | 0.0 | 661 ms | 0 |
| Fri 11 | 0 | 0.0 | 619 ms | 0 |
| Fri 12 | 0 | 0.0 | 1004 ms | 0 |
| Fri 14 | 0 | 0.0 | 597 ms | 0 |
| Fri 16 | 0 | 0.0 | 1060 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 Chartbeat 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 Chartbeat goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Chartbeat alerts to Slack, Discord or a webhook — free.
Chartbeat is listed in our Entertainment category and checked at chartbeat.com. Chartbeat provides solutions combining instant real-time insights, rich engagement data, and powerful optimization tools for media publishers
Chartbeat publishes an official status page at status.chartbeat.com; 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: 769 ms average, 560–1060 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 Chartbeat incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
769 ms on average over the last 24 hours (560–1060 ms).
Yes, at https://status.chartbeat.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 Chartbeat here at once, the problem is on Chartbeat'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 Chartbeat. 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.