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 139 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 18 | 0 | 0.0 | 142 ms | 0 |
| Tue 21 | 0 | 0.0 | 280 ms | 0 |
| Tue 23 | 0 | 0.0 | 186 ms | 0 |
| Wed 01 | 0 | 0.0 | 106 ms | 0 |
| Wed 03 | 0 | 0.0 | 246 ms | 0 |
| Wed 05 | 0 | 0.0 | 123 ms | 0 |
| Wed 08 | 0 | 0.0 | 162 ms | 0 |
| Wed 10 | 0 | 0.0 | 220 ms | 0 |
| Wed 12 | 0 | 0.0 | 140 ms | 0 |
| Wed 14 | 0 | 0.0 | 104 ms | 0 |
| Wed 16 | 0 | 0.0 | 183 ms | 0 |
| Wed 19 | 0 | 0.0 | 229 ms | 0 |
| Wed 21 | 0 | 0.0 | 174 ms | 0 |
| Wed 23 | 0 | 0.0 | 288 ms | 0 |
| Thu 01 | 0 | 0.0 | 171 ms | 0 |
| Thu 03 | 0 | 0.0 | 157 ms | 0 |
| Thu 05 | 0 | 0.0 | 147 ms | 0 |
| Thu 07 | 0 | 0.0 | 87 ms | 0 |
| Thu 09 | 0 | 0.0 | 131 ms | 0 |
| Thu 11 | 0 | 0.0 | 102 ms | 0 |
| Thu 14 | 0 | 0.0 | 330 ms | 0 |
| Thu 16 | 0 | 0.0 | 144 ms | 0 |
| Thu 18 | 0 | 0.0 | 136 ms | 0 |
| Thu 20 | 0 | 0.0 | 117 ms | 0 |
| Thu 22 | 0 | 0.0 | 159 ms | 0 |
| Fri 00 | 0 | 0.0 | 221 ms | 0 |
| Fri 02 | 0 | 0.0 | 168 ms | 0 |
| Fri 03 | 0 | 0.0 | 97 ms | 0 |
| Fri 05 | 0 | 0.0 | 148 ms | 0 |
| Fri 07 | 0 | 0.0 | 130 ms | 0 |
| Fri 09 | 0 | 0.0 | 147 ms | 0 |
| Fri 11 | 0 | 0.0 | 144 ms | 0 |
| Fri 13 | 0 | 0.0 | 245 ms | 0 |
| Fri 15 | 0 | 0.0 | 263 ms | 0 |
| Fri 17 | 0 | 0.0 | 149 ms | 0 |
| Fri 18 | 0 | 0.0 | 154 ms | 0 |
| Fri 20 | 0 | 0.0 | 140 ms | 0 |
| Fri 21 | 0 | 0.0 | 131 ms | 0 |
| Fri 23 | 0 | 0.0 | 125 ms | 0 |
| Sat 01 | 0 | 0.0 | 175 ms | 0 |
| Sat 03 | 0 | 0.0 | 251 ms | 0 |
| Sat 05 | 0 | 0.0 | 249 ms | 0 |
| Sat 07 | 0 | 0.0 | 178 ms | 0 |
| Sat 09 | 0 | 0.0 | 118 ms | 0 |
| Sat 12 | 0 | 0.0 | 140 ms | 0 |
| Sat 14 | 0 | 0.0 | 215 ms | 0 |
| Sat 16 | 0 | 0.0 | 122 ms | 0 |
| Sat 19 | 0 | 0.0 | 139 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 Upheal, Inc. 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 Upheal, Inc. 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.
Upheal, Inc., at upheal.io, is one of the Health services we monitor. Get AI therapy notes in minutes: AI progress notes from your sessions, free to start. Move your whole practice to Upheal’s EHR when you’re ready.
Upheal, Inc. publishes an official status page at status.upheal.io; 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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 165 ms average, 118–251 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 Upheal, Inc. incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
165 ms on average over the last 24 hours (118–251 ms).
Yes, at https://status.upheal.io.
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 Upheal, Inc. here at once, the problem is on Upheal, Inc.'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 Upheal, Inc.. 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.