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 1 hr ago. Last stored result reached it in 242 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 19 | 0 | 0.0 | 160 ms | 0 |
| Mon 21 | 0 | 0.0 | 99 ms | 0 |
| Mon 23 | 0 | 0.0 | 150 ms | 0 |
| Tue 01 | 0 | 0.0 | 142 ms | 0 |
| Tue 03 | 0 | 0.0 | 195 ms | 0 |
| Tue 05 | 0 | 0.0 | 268 ms | 0 |
| Tue 07 | 0 | 0.0 | 110 ms | 0 |
| Tue 09 | 0 | 0.0 | 104 ms | 0 |
| Tue 12 | 0 | 0.0 | 241 ms | 0 |
| Tue 14 | 0 | 0.0 | 216 ms | 0 |
| Tue 16 | 0 | 0.0 | 88 ms | 0 |
| Tue 18 | 0 | 0.0 | 254 ms | 0 |
| Tue 21 | 0 | 0.0 | 100 ms | 0 |
| Tue 23 | 0 | 0.0 | 116 ms | 0 |
| Wed 01 | 0 | 0.0 | 281 ms | 0 |
| Wed 03 | 0 | 0.0 | 108 ms | 0 |
| Wed 06 | 0 | 0.0 | 235 ms | 0 |
| Wed 08 | 0 | 0.0 | 105 ms | 0 |
| Wed 10 | 0 | 0.0 | 68 ms | 0 |
| Wed 12 | 0 | 0.0 | 238 ms | 0 |
| Wed 14 | 0 | 0.0 | 282 ms | 0 |
| Wed 16 | 0 | 0.0 | 149 ms | 0 |
| Wed 19 | 0 | 0.0 | 95 ms | 0 |
| Wed 21 | 0 | 0.0 | 67 ms | 0 |
| Wed 23 | 0 | 0.0 | 104 ms | 0 |
| Thu 01 | 0 | 0.0 | 90 ms | 0 |
| Thu 03 | 0 | 0.0 | 83 ms | 0 |
| Thu 05 | 0 | 0.0 | 276 ms | 0 |
| Thu 07 | 0 | 0.0 | 123 ms | 0 |
| Thu 09 | 0 | 0.0 | 234 ms | 0 |
| Thu 11 | 0 | 0.0 | 157 ms | 0 |
| Thu 14 | 0 | 0.0 | 110 ms | 0 |
| Thu 16 | 0 | 0.0 | 104 ms | 0 |
| Thu 18 | 0 | 0.0 | 92 ms | 0 |
| Thu 20 | 0 | 0.0 | 235 ms | 0 |
| Thu 22 | 0 | 0.0 | 64 ms | 0 |
| Fri 00 | 0 | 0.0 | 510 ms | 0 |
| Fri 02 | 0 | 0.0 | 119 ms | 0 |
| Fri 04 | 0 | 0.0 | 180 ms | 0 |
| Fri 06 | 0 | 0.0 | 67 ms | 0 |
| Fri 08 | 0 | 0.0 | 81 ms | 0 |
| Fri 10 | 0 | 0.0 | 57 ms | 0 |
| Fri 12 | 0 | 0.0 | 178 ms | 0 |
| Fri 14 | 0 | 0.0 | 113 ms | 0 |
| Fri 17 | 0 | 0.0 | 295 ms | 0 |
| Fri 19 | 0 | 0.0 | 252 ms | 0 |
| Fri 20 | 0 | 0.0 | 105 ms | 0 |
| Fri 22 | 0 | 0.0 | 242 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 Nabla 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 Nabla goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Nabla alerts to Slack, Discord or a webhook — free.
Nabla is listed in our Health category and checked at nabla.com. Nabla’s Clinical AI Layer brings ambient documentation, dictation, and coding support into Epic and all major EHRs, trusted by health organizations nationwide.
Nabla publishes an official status page at status.nabla.com; when we can read it, its incident level is folded into the status shown here.
Typical issues 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: 177 ms average, 57–510 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Nabla incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
177 ms on average over the last 24 hours (57–510 ms).
Yes, at https://status.nabla.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 Nabla here at once, the problem is on Nabla'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 Nabla. 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.