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 4 min ago. Last stored result reached it in 74 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Wed 10 | 0 | 0.0 | 199 ms | 0 |
| Wed 12 | 0 | 0.0 | 59 ms | 0 |
| Wed 14 | 0 | 0.0 | 63 ms | 0 |
| Wed 16 | 0 | 0.0 | 56 ms | 0 |
| Wed 19 | 0 | 0.0 | 38 ms | 0 |
| Wed 21 | 0 | 0.0 | 42 ms | 0 |
| Wed 23 | 0 | 0.0 | 79 ms | 0 |
| Thu 01 | 0 | 0.0 | 174 ms | 0 |
| Thu 03 | 0 | 0.0 | 36 ms | 0 |
| Thu 05 | 0 | 0.0 | 37 ms | 0 |
| Thu 07 | 0 | 0.0 | 100 ms | 0 |
| Thu 09 | 0 | 0.0 | 78 ms | 0 |
| Thu 11 | 0 | 0.0 | 65 ms | 0 |
| Thu 13 | 0 | 0.0 | 80 ms | 0 |
| Thu 16 | 0 | 0.0 | 137 ms | 0 |
| Thu 18 | 0 | 0.0 | 64 ms | 0 |
| Thu 20 | 0 | 0.0 | 152 ms | 0 |
| Thu 21 | 0 | 0.0 | 40 ms | 0 |
| Thu 23 | 0 | 0.0 | 136 ms | 0 |
| Fri 01 | 0 | 0.0 | 60 ms | 0 |
| Fri 04 | 0 | 0.0 | 128 ms | 0 |
| Fri 06 | 0 | 0.0 | 44 ms | 0 |
| Fri 08 | 0 | 0.0 | 85 ms | 0 |
| Fri 10 | 0 | 0.0 | 57 ms | 0 |
| Fri 12 | 0 | 0.0 | 87 ms | 0 |
| Fri 14 | 0 | 0.0 | 39 ms | 0 |
| Fri 16 | 0 | 0.0 | 37 ms | 0 |
| Fri 17 | 0 | 0.0 | 54 ms | 0 |
| Fri 18 | 0 | 0.0 | 144 ms | 0 |
| Fri 19 | 0 | 0.0 | 43 ms | 0 |
| Fri 20 | 0 | 0.0 | 49 ms | 0 |
| Fri 22 | 0 | 0.0 | 62 ms | 0 |
| Sat 00 | 0 | 0.0 | 30 ms | 0 |
| Sat 02 | 0 | 0.0 | 131 ms | 0 |
| Sat 04 | 0 | 0.0 | 43 ms | 0 |
| Sat 06 | 0 | 0.0 | 95 ms | 0 |
| Sat 07 | 0 | 0.0 | 100 ms | 0 |
| Sat 08 | 0 | 0.0 | 86 ms | 0 |
| Sat 10 | 0 | 0.0 | 56 ms | 0 |
| Sat 13 | 0 | 0.0 | 29 ms | 0 |
| Sat 15 | 0 | 0.0 | 121 ms | 0 |
| Sat 17 | 0 | 0.0 | 70 ms | 0 |
| Sat 20 | 0 | 0.0 | 27 ms | 0 |
| Sat 22 | 0 | 0.0 | 108 ms | 0 |
| Sun 00 | 0 | 0.0 | 66 ms | 0 |
| Sun 03 | 0 | 0.0 | 140 ms | 0 |
| Sun 05 | 0 | 0.0 | 83 ms | 0 |
| Sun 07 | 0 | 0.0 | 74 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 10 days of data so far, so the 90-day numbers fill in over time.
[Scheduled] Cache Infrastructure Maintenance
During this maintenance window, some services may undergo brief restarts, which could result in short periods of instability or temporary connection interruptions. All services are expected to remain operational, and no extended downtime is anticipated. Thank you for your understanding. We will update this page once the scheduled maintenance has been completed.
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
No outages on record for Luma Health 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 Luma Health 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.
Luma Health is listed in our Health category and checked at lumahealth.io. Transform patient journeys with Luma's AI, enhancing scheduling, communication, and revenue collection while seamlessly integrating with your EHR.
Luma Health publishes an official status page at status.lumahealth.io; 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 10 days of checks. No public incidents logged since monitoring began 10 days ago.
Response time over the last 24 hours: 83 ms average, 27–219 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 Luma Health incident since monitoring began 10 days ago.
From our own checks: 100% over 10 days of checks.
83 ms on average over the last 24 hours (27–219 ms).
Yes, at https://status.lumahealth.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 Luma Health here at once, the problem is on Luma Health'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 Luma Health. 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.