User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Sports
Is Heartbeat down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → heartbeat.chat—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 9 min ago. Last stored result reached it in 97 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 03 | 0 | 0.0 | 298 ms | 0 |
| Tue 05 | 0 | 0.0 | 71 ms | 0 |
| Tue 07 | 0 | 0.0 | 87 ms | 0 |
| Tue 09 | 0 | 0.0 | 104 ms | 0 |
| Tue 11 | 0 | 0.0 | 232 ms | 0 |
| Tue 13 | 0 | 0.0 | 107 ms | 0 |
| Tue 16 | 0 | 0.0 | 102 ms | 0 |
| Tue 18 | 0 | 0.0 | 274 ms | 0 |
| Tue 20 | 0 | 0.0 | 100 ms | 0 |
| Tue 22 | 0 | 0.0 | 101 ms | 0 |
| Wed 01 | 0 | 0.0 | 142 ms | 0 |
| Wed 03 | 0 | 0.0 | 95 ms | 0 |
| Wed 05 | 0 | 0.0 | 282 ms | 0 |
| Wed 07 | 0 | 0.0 | 190 ms | 0 |
| Wed 10 | 0 | 0.0 | 105 ms | 0 |
| Wed 12 | 0 | 0.0 | 153 ms | 0 |
| Wed 14 | 0 | 0.0 | 96 ms | 0 |
| Wed 16 | 0 | 0.0 | 205 ms | 0 |
| Wed 18 | 0 | 0.0 | 112 ms | 0 |
| Wed 20 | 0 | 0.0 | 209 ms | 0 |
| Wed 23 | 0 | 0.0 | 257 ms | 0 |
| Thu 01 | 0 | 0.0 | 74 ms | 0 |
| Thu 03 | 0 | 0.0 | 127 ms | 0 |
| Thu 05 | 0 | 0.0 | 227 ms | 0 |
| Thu 07 | 0 | 0.0 | 136 ms | 0 |
| Thu 09 | 0 | 0.0 | 272 ms | 0 |
| Thu 11 | 0 | 0.0 | 109 ms | 0 |
| Thu 13 | 0 | 0.0 | 231 ms | 0 |
| Thu 15 | 0 | 0.0 | 116 ms | 0 |
| Thu 17 | 0 | 0.0 | 271 ms | 0 |
| Thu 19 | 0 | 0.0 | 133 ms | 0 |
| Thu 21 | 0 | 0.0 | 300 ms | 0 |
| Thu 23 | 0 | 0.0 | 95 ms | 0 |
| Fri 01 | 0 | 0.0 | 167 ms | 0 |
| Fri 03 | 0 | 0.0 | 89 ms | 0 |
| Fri 05 | 0 | 0.0 | 100 ms | 0 |
| Fri 07 | 0 | 0.0 | 101 ms | 0 |
| Fri 09 | 0 | 0.0 | 104 ms | 0 |
| Fri 10 | 0 | 0.0 | 116 ms | 0 |
| Fri 11 | 0 | 0.0 | 120 ms | 0 |
| Fri 13 | 0 | 0.0 | 135 ms | 0 |
| Fri 15 | 0 | 0.0 | 130 ms | 0 |
| Fri 17 | 0 | 0.0 | 194 ms | 0 |
| Fri 18 | 0 | 0.0 | 63 ms | 0 |
| Fri 20 | 0 | 0.0 | 84 ms | 0 |
| Fri 22 | 0 | 0.0 | 236 ms | 0 |
| Sat 00 | 0 | 0.0 | 69 ms | 0 |
| Sat 02 | 0 | 0.0 | 97 ms | 0 |
Reliability
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 9 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Heartbeat badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Heartbeat yet. Outages of 10 minutes or more get their own page here.
Having trouble with Heartbeat?
One report per service every 10 minutes from this network. No account.
Follow Heartbeat
Get an email when Heartbeat goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Heartbeat alerts to Slack, Discord or a webhook — free.
About Heartbeat
Heartbeat, at heartbeat.chat, is one of the Sports services we monitor. The online community platform for creators and coaches. Run memberships, courses, events and payments in one place you own. 37,000+ communities built.
Heartbeat publishes an official status page at status.heartbeat.chat; when we can read it, its incident level is folded into the status shown here.
Common problems for sports services: ticketing, team app and live-score pages slowing down around game time.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 117 ms average, 63–236 ms range across 14 successful checks.
Questions
Is Heartbeat down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Heartbeat last down?
We have not recorded a public Heartbeat incident since monitoring began 9 days ago.
What is Heartbeat's uptime?
From our own checks: 100% over 9 days of checks.
How fast does Heartbeat respond?
117 ms on average over the last 24 hours (63–236 ms).
Does Heartbeat have an official status page?
Yes, at https://status.heartbeat.chat.
Heartbeat not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For sports services, watch for ticketing, team app and live-score pages slowing down around game time. If many people report Heartbeat here at once, the problem is on Heartbeat'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 Heartbeat. 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.