User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Health
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 13 min ago. Last stored result reached it in 265 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 20 | 0 | 0.0 | 215 ms | 0 |
| Tue 23 | 0 | 0.0 | 224 ms | 0 |
| Wed 01 | 0 | 0.0 | 219 ms | 0 |
| Wed 03 | 0 | 0.0 | 250 ms | 0 |
| Wed 05 | 0 | 0.0 | 223 ms | 0 |
| Wed 07 | 0 | 0.0 | 240 ms | 0 |
| Wed 10 | 0 | 0.0 | 216 ms | 0 |
| Wed 12 | 0 | 0.0 | 236 ms | 0 |
| Wed 14 | 0 | 0.0 | 152 ms | 0 |
| Wed 16 | 0 | 0.0 | 251 ms | 0 |
| Wed 18 | 0 | 0.0 | 249 ms | 0 |
| Wed 21 | 0 | 0.0 | 182 ms | 0 |
| Wed 23 | 0 | 0.0 | 220 ms | 0 |
| Thu 01 | 0 | 0.0 | 227 ms | 0 |
| Thu 03 | 0 | 0.0 | 283 ms | 0 |
| Thu 05 | 0 | 0.0 | 251 ms | 0 |
| Thu 07 | 0 | 0.0 | 288 ms | 0 |
| Thu 09 | 0 | 0.0 | 199 ms | 0 |
| Thu 11 | 0 | 0.0 | 287 ms | 0 |
| Thu 13 | 0 | 0.0 | 263 ms | 0 |
| Thu 15 | 0 | 0.0 | 210 ms | 0 |
| Thu 17 | 0 | 0.0 | 253 ms | 0 |
| Thu 19 | 0 | 0.0 | 221 ms | 0 |
| Thu 22 | 0 | 0.0 | 185 ms | 0 |
| Fri 00 | 0 | 0.0 | 197 ms | 0 |
| Fri 02 | 0 | 0.0 | 206 ms | 0 |
| Fri 04 | 0 | 0.0 | 101 ms | 0 |
| Fri 06 | 0 | 0.0 | 299 ms | 0 |
| Fri 08 | 0 | 0.0 | 240 ms | 0 |
| Fri 10 | 0 | 0.0 | 215 ms | 0 |
| Fri 11 | 0 | 0.0 | 243 ms | 0 |
| Fri 13 | 0 | 0.0 | 284 ms | 0 |
| Fri 14 | 0 | 0.0 | 100 ms | 0 |
| Fri 16 | 0 | 0.0 | 213 ms | 0 |
| Fri 17 | 0 | 0.0 | 213 ms | 0 |
| Fri 18 | 0 | 0.0 | 223 ms | 0 |
| Fri 20 | 0 | 0.0 | 287 ms | 0 |
| Fri 22 | 0 | 0.0 | 278 ms | 0 |
| Sat 00 | 0 | 0.0 | 122 ms | 0 |
| Sat 02 | 0 | 0.0 | 254 ms | 0 |
| Sat 04 | 0 | 0.0 | 281 ms | 0 |
| Sat 06 | 0 | 0.0 | 210 ms | 0 |
| Sat 08 | 0 | 0.0 | 274 ms | 0 |
| Sat 10 | 0 | 0.0 | 212 ms | 0 |
| Sat 12 | 0 | 0.0 | 210 ms | 0 |
| Sat 15 | 0 | 0.0 | 98 ms | 0 |
| Sat 17 | 0 | 0.0 | 273 ms | 0 |
| Sat 19 | 0 | 0.0 | 265 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 Healthy Roster 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 Healthy Roster goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
We track Healthy Roster (healthyroster.com) as part of the Health group. The leading Athletic Trainer EMR for outreach, using mobile and desktop software for faster documentation and communication
Healthy Roster publishes an official status page at status.healthyroster.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with health services: patient portal and member sign-in failures, prescription refills or appointment booking not going through, and app errors.
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: 230 ms average, 98–287 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Healthy Roster incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
230 ms on average over the last 24 hours (98–287 ms).
Yes, at https://status.healthyroster.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For health services, watch for patient portal and member sign-in failures, prescription refills or appointment booking not going through, and app errors. If many people report Healthy Roster here at once, the problem is on Healthy Roster'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 Healthy Roster. 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.