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 2 hr ago. Last stored result reached it in 88 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 14 | 0 | 0.0 | 56 ms | 0 |
| Mon 16 | 0 | 0.0 | 181 ms | 0 |
| Mon 18 | 0 | 0.0 | 89 ms | 0 |
| Mon 20 | 0 | 0.0 | 132 ms | 0 |
| Mon 23 | 0 | 0.0 | 86 ms | 0 |
| Tue 01 | 0 | 0.0 | 85 ms | 0 |
| Tue 03 | 0 | 0.0 | 76 ms | 0 |
| Tue 05 | 0 | 0.0 | 73 ms | 0 |
| Tue 07 | 0 | 0.0 | 59 ms | 0 |
| Tue 09 | 0 | 0.0 | 84 ms | 0 |
| Tue 11 | 0 | 0.0 | 111 ms | 0 |
| Tue 13 | 0 | 0.0 | 165 ms | 0 |
| Tue 16 | 0 | 0.0 | 85 ms | 0 |
| Tue 18 | 0 | 0.0 | 37 ms | 0 |
| Tue 20 | 0 | 0.0 | 73 ms | 0 |
| Tue 22 | 0 | 0.0 | 95 ms | 0 |
| Wed 01 | 0 | 0.0 | 82 ms | 0 |
| Wed 03 | 0 | 0.0 | 71 ms | 0 |
| Wed 05 | 0 | 0.0 | 80 ms | 0 |
| Wed 07 | 0 | 0.0 | 83 ms | 0 |
| Wed 10 | 0 | 0.0 | 93 ms | 0 |
| Wed 12 | 0 | 0.0 | 109 ms | 0 |
| Wed 14 | 0 | 0.0 | 66 ms | 0 |
| Wed 16 | 0 | 0.0 | 93 ms | 0 |
| Wed 18 | 0 | 0.0 | 120 ms | 0 |
| Wed 20 | 0 | 0.0 | 227 ms | 0 |
| Wed 23 | 0 | 0.0 | 69 ms | 0 |
| Thu 01 | 0 | 0.0 | 128 ms | 0 |
| Thu 03 | 0 | 0.0 | 196 ms | 0 |
| Thu 05 | 0 | 0.0 | 101 ms | 0 |
| Thu 07 | 0 | 0.0 | 153 ms | 0 |
| Thu 09 | 0 | 0.0 | 30 ms | 0 |
| Thu 11 | 0 | 0.0 | 93 ms | 0 |
| Thu 13 | 0 | 0.0 | 155 ms | 0 |
| Thu 15 | 0 | 0.0 | 150 ms | 0 |
| Thu 17 | 0 | 0.0 | 42 ms | 0 |
| Thu 19 | 0 | 0.0 | 77 ms | 0 |
| Thu 21 | 0 | 0.0 | 49 ms | 0 |
| Thu 23 | 0 | 0.0 | 142 ms | 0 |
| Fri 01 | 0 | 0.0 | 83 ms | 0 |
| Fri 04 | 0 | 0.0 | 41 ms | 0 |
| Fri 06 | 0 | 0.0 | 137 ms | 0 |
| Fri 08 | 0 | 0.0 | 170 ms | 0 |
| Fri 10 | 0 | 0.0 | 103 ms | 0 |
| Fri 12 | 0 | 0.0 | 69 ms | 0 |
| Fri 14 | 0 | 0.0 | 30 ms | 0 |
| Fri 16 | 0 | 0.0 | 65 ms | 0 |
| Fri 18 | 0 | 0.0 | 88 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 EldermarkNEXT 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 EldermarkNEXT goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send EldermarkNEXT alerts to Slack, Discord or a webhook — free.
We track EldermarkNEXT (eldermark.com) as part of the Health group. Eldermark is the senior living management software platform connecting EHR, eMAR, billing, CRM, and analytics in one place. Trusted by 2,500+ communities.
EldermarkNEXT publishes an official status page at status.eldermark.com; when we can read it, its incident level is folded into the status shown here.
Common problems for 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: 89 ms average, 30–170 ms range across 11 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public EldermarkNEXT incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
89 ms on average over the last 24 hours (30–170 ms).
Yes, at https://status.eldermark.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 EldermarkNEXT here at once, the problem is on EldermarkNEXT'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 EldermarkNEXT. 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.