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 9 min ago. Last stored result reached it in 36 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 110 ms | 0 |
| Nov 7 | 0 | 0.0 | 130 ms | 0 |
| Nov 7 | 0 | 0.0 | 82 ms | 0 |
| Nov 7 | 0 | 0.0 | 45 ms | 0 |
| Nov 7 | 0 | 0.0 | 133 ms | 0 |
| Nov 8 | 0 | 0.0 | 61 ms | 0 |
| Nov 8 | 0 | 0.0 | 114 ms | 0 |
| Nov 8 | 0 | 0.0 | 64 ms | 0 |
| Nov 8 | 0 | 0.0 | 98 ms | 0 |
| Nov 9 | 0 | 0.0 | 134 ms | 0 |
| Nov 9 | 0 | 0.0 | 79 ms | 0 |
| Nov 9 | 0 | 0.0 | 69 ms | 0 |
| Nov 9 | 0 | 0.0 | 54 ms | 0 |
| Nov 10 | 0 | 0.0 | 56 ms | 0 |
| Nov 10 | 0 | 0.0 | 70 ms | 0 |
| Nov 10 | 0 | 0.0 | 67 ms | 0 |
| Nov 10 | 0 | 0.0 | 73 ms | 0 |
| Nov 11 | 0 | 0.0 | 117 ms | 0 |
| Nov 11 | 0 | 0.0 | 55 ms | 0 |
| Nov 11 | 0 | 0.0 | 64 ms | 0 |
| Nov 11 | 0 | 0.0 | 73 ms | 0 |
| Nov 12 | 0 | 0.0 | 73 ms | 0 |
| Nov 12 | 0 | 0.0 | 40 ms | 0 |
| Nov 12 | 0 | 0.0 | 64 ms | 0 |
| Nov 12 | 0 | 0.0 | 52 ms | 0 |
| Nov 13 | 0 | 0.0 | 66 ms | 0 |
| Nov 13 | 0 | 0.0 | 45 ms | 0 |
| Nov 13 | 0 | 0.0 | 32 ms | 0 |
| Nov 13 | 0 | 0.0 | 73 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 CentralReach 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 CentralReach goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send CentralReach alerts to Slack, Discord or a webhook — free.
We track CentralReach (centralreach.com) as part of the Health group. ABA and Multidisciplinary Software Solutions for Autism & IDD Care. End-to-end software that supports the efficient delivery of care.
CentralReach publishes an official status page at status.centralreach.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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 55 ms average, 21–80 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 CentralReach incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
55 ms on average over the last 24 hours (21–80 ms).
Yes, at https://status.centralreach.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 CentralReach here at once, the problem is on CentralReach'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 CentralReach. 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.