Luma Health logo

Is Luma Health Down?

SaaSLive status, outages, and incident history

No. Luma Health is up right now.

Every monitored Luma Health system is operational as of November 14, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · every 60s

Know the moment Luma Health breaks

Luma Health is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official Luma Health status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Luma Health Status Summary

As of 19:43 UTC on 14 November 2026, Luma Health is operational. PulsAPI checked Luma Health's official status page and found 24 of 24 components operational, with no active incidents. The latest incident, "Service Disruption", was on Nov 2, 2026 and lasted 10h 26m.

Cite as: PulsAPI, “Luma Health status”, checked 14 November 2026, 19:43 UTC. https://www.pulsapi.com/services/luma-health

Luma Health Component Status

The main Luma Health systems on this page. All 24 are operational right now.

24operational
AI Services
Operational
Auth0 User Authentication
Operational
AWS » AWS cloudfront
Operational

21 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking AWS » AWS ec2-us-west-2, AWS » AWS eks-us-west-2, AWS » AWS elasticache-us-west-2, AWS » AWS lambda-us-west-2, AWS » AWS s3-us-west-2, Bandwidth » Toll-Free SMS - Inbound, Bandwidth » Toll-Free SMS - Outbound, Cloudflare CDN/Cache, Communication Services, EHR/PM Integration System, Luma Health API, Luma Health Patient Web, and 9 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Luma Health Outages & Incidents

Incident history from the official Luma Health status page, including resolution updates.

Service DisruptionResolved Nov 2, 2026 · 10h 26mResolved

The service disruption affecting the Luma Health platform has been resolved. All affected services have been restored and are operational. Our Engineering team will continue monitoring platform stability and addressing any issues identified following recovery. We sincerely apologize for the disruption and appreciate your patience and understanding. --- [2026-11-02T23:36:14.460-08:00] (monitoring) All affected Luma Health services have been restored and are operational. Our Engineering team has completed the service recovery process and is actively monitoring the platform to ensure continued stability. We will continue monitoring before marking this incident as fully resolved. We sincerely apologize for the disruption and appreciate your patience throughout the recovery process. --- [2026-11-02T23:16:08.429-08:00] (identified) Recovery work on the Luma platform is still underway, and our teams continue to move through the remaining steps. Systems are not yet fully operational, and some features may still be unavailable. We will share an update as soon as there is a change in the situation. We understand the impact this has on your work, and we appreciate your continued patience. --- [2026-11-02T23:16:58.156-08:00] (monitoring) Recovery work on the Luma platform is still underway, and our teams continue to move through the remaining steps. Systems are not yet fully operational, and some features may still be unavailable. We will share an update as soon as there is a change in the situation. We understand the impact this has on your work, and we appreciate your continued patience. --- [2026-11-02T21:58:35.229-08:00] (identified) Service restoration for the Luma platform continues. Systems are not yet fully operational, and we do not have an exact timeline for full recovery. Our next update will be at 22:00 PST, or sooner if possible. We're sorry for the disruption and thank you for bearing with us. --- [2026-11-02T21:01:49.864-08:00] (identified) Service restoration for the Luma platform continues. Systems are not yet fully operational, and we do not have an exact timeline for full recovery. Our next update will be at 21:00 PST, or sooner if possible. We're sorry for the disruption and thank you for bearing with us. --- [2026-11-02T19:57:15.869-08:00] (identified) Restoration efforts for the Luma platform are well underway. Systems are not yet fully operational, and we do not have an exact timeline for full recovery. Our next update will be at 20:00 PST, or sooner if the situation changes. We understand the impact this has on your work, and we appreciate your continued patience. --- [2026-11-02T19:10:17.757-08:00] (identified) Service restoration efforts for the Luma platform continue. Systems are not yet fully operational, and we do not have an exact timeline for full recovery. Our engineering team is working to restore services as quickly as possible. Our next update will be at 20:00 PST, or sooner if the situation changes. We apologize for the disruption and appreciate your patience. --- [2026-11-02T17:56:35.329-08:00] (identified) Our team continues to make progress restoring services for the Luma platform. We do not have an exact timeline for full recovery. Our next update will be in 19:00 PST, or sooner if the situation changes. We apologize for the disruption and appreciate your patience. --- [2026-11-02T17:12:37.230-08:00] (identified) Our team is continuing to restore services for the Luma platform. Systems are not yet fully operational, and we do not have an exact timeline for full recovery. Our next update will be at 18:00 PST, or sooner if the situation changes. We apologize for the disruption and appreciate your patience. --- [2026-11-02T17:10:45.501-08:00] (identified) Service Recovery and service restoration for the Luma platform are still in progress. Systems are not yet fully operational, and we cannot give an exact timeline at this point. Our engineers are continuing recovery efforts. We will provide our next update at 17:00 PST. Thank you for your patience. We apologize for the impact to your work. --- [2026-11-02T18:30:04.738-08:00] (identified) Our Engineering team has identified the issue impacting the Luma platform. A database snapshot has been restored, and the team is now working to bring remaining services back online. Some features may still be unavailable while recovery is in progress, and we do not have an exact timeline for full recovery at this time. We will share our next update by 16:00 PST, or sooner if the situation changes. We apologize for the disruption and appreciate your patience. --- [2026-11-02T18:28:05.200-08:00] (investigating) Our Engineering team is continuing to investigate the issue impacting the Luma platform. We have made some progress, but we have not yet confirmed the full cause. Work to restore services remains underway, and some features may still be unavailable. We do not have an exact timeline for full recovery at this time. We apologize for the disruption and appreciate your patience. --- [2026-11-02T18:26:34.648-08:00] (investigating) Our teams are continuing to work on the service disruption impacting the Luma platform. Most features will still be unavailable. Engineering is working to fully identify the root cause and restore normal operation. We will share additional details as they become available. We regret the inconvenience and thank you for your continued patience. --- [2026-11-02T18:25:44.931-08:00] (investigating) Our Engineering team has identified the issue impacting the Luma platform and is continuing to investigate to confirm the full scope and root cause. Work to restore services is underway, and some features may remain unavailable in the meantime. We do not have an exact timeline for full recovery at this time. We apologize for the disruption and appreciate your patience. We will share additional updates as more information becomes available. --- [2026-11-02T12:54:06.154-08:00] (investigating) We are continuing to investigate this issue. --- [2026-11-02T12:50:04.902-08:00] (investigating) We’re currently experiencing a service disruption affecting the Luma platform. Functionality may be temporarily disrupted. Our engineering team is aware and is working to resolve it. We’ll share more information as soon as we have it. We apologize for the inconvenience and appreciate your patience.

Cloudflare Outage Affecting Luma Site Access and Sign-InResolved Oct 27, 2026 · 57 minResolved

This incident has been resolved. Cloudflare identified an issue affecting customers whose traffic passes through an external vendor firewall, which may have prevented some Luma customers from loading pages or signing in. The issue has been fixed and access has been restored. There is nothing you need to do on your end, and your data was not affected. We apologize for the disruption and thank you for your patience. --- [2026-10-27T07:58:12.398-07:00] (monitoring) Cloudflare has implemented a fix for the issue that was preventing some Luma customers from loading pages or signing in. We are now monitoring the results to confirm that access is fully restored. There is nothing you need to do on your end, and your data was not affected. We will post another update here once we have confirmed full recovery. Thank you for your patience. --- [2026-10-27T07:19:10.862-07:00] (identified) A problem at Cloudflare, one of our network providers, may be stopping some Luma customers from loading pages or signing in. We’re watching Cloudflare’s status updates closely and will post here as soon as we have more. There’s nothing you need to do on your end, and your data isn’t affected. We’ll confirm here once access is fully restored. Thank you for your patience.

Navigator calls disconnecting unexpectedlyResolved Oct 5, 2026Resolved

Resolved - Between approximately 7:00 AM ET and 10:28 AM ET, some patient calls to Navigator were dropped mid-conversation after the greeting played. The cause was an unannounced change made by our third-party voice AI vendor, which affected our integration's ability to process the conversation. Our team identified the issue and performed a global failover to a backup voice vendor, which stopped the dropped calls. We have also escalated the issue to the original vendor. We are working with the vendor to establish advance notification for future changes, and we are strengthening our automatic failover detection so similar issues are caught and resolved faster. We know how disruptive this is when it affects patient care, and we apologize for the impact.

Upcoming maintenance

Announced by Luma Health. Planned work, not an outage.

[Scheduled] Cache Infrastructure MaintenanceScheduled for Nov 20, 2026 · 2h 0mScheduled

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.

Luma Health Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Luma Health incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history3 days observed
Nov 12100.00% averageNov 14

Live Luma Health Outage Reports

Problems reported by engineers using Luma Health. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Luma Health problems reported yet.

Something wrong with Luma Health on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Luma Health

Luma Health posts its status at status.lumahealth.io. The page covers 24 components, among them AI Services, AWS cloudfront and AWS ec2-us-west-2. Past incidents and uptime for Luma Health stay on this page, which helps when you want to know how often it has trouble.

Luma Health Status FAQ

Is Luma Health down right now?

The verdict at the top of this page comes from the latest poll of the official Luma Health status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Luma Health is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Luma Health recovers.

How do I check Luma Health uptime history?

PulsAPI tracks Luma Health uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Luma Health changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Luma Health outages?

PulsAPI reads the official Luma Health status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Luma Health components?

Yes. PulsAPI monitors 24 individual Luma Health components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Luma Health goes down?

Yes. Create a free account and subscribe to Luma Health: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Luma Health to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Luma Health problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Luma Health?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Luma Health plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Luma Health with the rest of your stack

4372+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services