Luma Health Outage History

Luma Health is up right now

Pingoru has recorded 50 incidents for Luma Health: 14 in the last 12 months and 5 in the last 90 days.

Source: status.lumahealth.io

50incidents recorded
14last 12 months
5last 90 days
4 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct1
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Luma Health in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 2026225 of 744 (3%)
June 202626 of 720 (1%)
July 202610 of 744 (0%)
August 202614 of 744 (1%)
September 202622 of 720 (0%)
October 202610 of 508 (0%)

Incidents, newest first

Minor October 5, 2026 Navigator calls disconnecting unexpectedly –

Started Oct 05, 2026, 09:00 AM UTC· resolved Oct 05, 2026, 09:00 AM UTC

  1. resolved Oct 05, 2026, 04:58 PM UTC

    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.

Read the full incident report →

Minor September 18, 2026 Intermittent Loading Issues - Forms, Checklists & Clinic App 43m Luma Health Web (next.lumahealth.io)

Started Sep 18, 2026, 06:26 PM UTC· resolved Sep 18, 2026, 07:09 PM UTC

  1. investigating Sep 18, 2026, 06:26 PM UTC

    We are currently investigating reports of slow performance affecting Luma services. Our team is actively working to identify the root cause. We will provide an update as soon as more information is available.

  2. investigating Sep 18, 2026, 06:48 PM UTC

    We are currently experiencing intermittent loading issues affecting Forms, Checklists, and the Clinic app. Our Engineering team has identified the impact and is actively working to resolve it. Other Luma services are not affected at this time. We will provide an update as more information becomes available.

  3. resolved Sep 18, 2026, 07:09 PM UTC

    This incident has been resolved. Forms, Checklists, and the Clinic app are now loading normally. Our Engineering team confirmed the fix and will continue to monitor the situation to ensure stability. We apologize for any inconvenience this may have caused and thank you for your patience.

Read the full incident report →

Minor September 1, 2026 Sigma Reports Loading Issue 1h 31m Reporting and Datawarehouse

Started Sep 01, 2026, 03:49 PM UTC· resolved Sep 01, 2026, 05:21 PM UTC

  1. monitoring Sep 01, 2026, 03:49 PM UTC

    We are aware that some customers are currently unable to load reports due to an ongoing incident with Sigma, our reporting provider. Our team is actively monitoring the situation and working directly with Sigma to resolve it as quickly as possible. We will post updates here as soon as we have more information. For reference: https://status.sigmacomputing.com/incidents/8ttp4ncqt8lp

  2. monitoring Sep 01, 2026, 03:53 PM UTC

    We are continuing to monitor for any further issues.

  3. resolved Sep 01, 2026, 05:21 PM UTC

    This incident has been resolved. Sigma has confirmed that the underlying issue, related to a GCP (Google Cloud Platform) outage affecting their GCP-hosted infrastructure, has been fixed. Reports are now loading normally. We apologize for any inconvenience this may have caused. Sigma has indicated they will publish a root cause analysis (RCA) in the coming days, and we'll share any relevant findings if applicable. Thank you for your patience while we worked through this with Sigma.

Read the full incident report →

Minor August 26, 2026 Slowness and login issues across Luma Platform 4h 22m Luma Health Web (next.lumahealth.io)

Started Aug 26, 2026, 02:30 PM UTC· resolved Aug 26, 2026, 06:52 PM UTC

  1. investigating Aug 26, 2026, 02:30 PM UTC

    We are currently investigating reports of slower-than-usual performance affecting the Luma Platform. Some users may experience delays. Our team is actively looking into the root cause. We'll share an update as soon as we have more information.

  2. identified Aug 26, 2026, 03:05 PM UTC

    We have identified a resource constraint in one of our backend systems as a contributing factor to the ongoing performance issues. Some actions may continue to take longer than usual to complete. Our Engineering team is actively monitoring the situation, reviewing system activity to determine the exact cause, and coordinating additional infrastructure support before implementing a fix. The root cause is not yet confirmed. We will continue to provide updates as more information becomes available.

  3. identified Aug 26, 2026, 03:49 PM UTC

    Our Engineering team continues working on infrastructure recovery. We've increased backend capacity and are scaling up additional resources to process the backlog causing delays. However, some services are still experiencing intermittent connectivity issues, which may cause continued disruption for some users. We are coordinating closely with our infrastructure provider and investigating a possible spike in activity earlier today as a contributing factor. We understand this has been an extended disruption and appreciate your continued patience. We will share the next update as soon as we have more progress to report.

  4. monitoring Aug 26, 2026, 04:36 PM UTC

    We are seeing signs of recovery, and performance is improving. Some users may still experience lingering instability, including intermittent slowness, as systems continue to stabilize. Our Engineering team is continuing to closely monitor the situation to ensure full stability before marking this incident as resolved. We will provide a further update once services have returned to normal.

  5. resolved Aug 26, 2026, 06:52 PM UTC

    This incident has been resolved. All services are fully restored and operating normally. What happened: Starting around 10:06am ET, Luma experienced widespread platform instability, including general service errors, delays in message delivery, and disruptions to specific features such as Navigator voice calls and access to Luma Platform. Root cause: The issue was traced to an unusually high volume of inbound data processing triggered by a newly activated integration, which exceeded system capacity and caused a backlog affecting platform-wide performance. Resolution: The integration has been disabled, additional system capacity has been added to prevent recurrence, and all services have been confirmed stable and fully functional. Our team is continuing to monitor system stability and conducting a full internal review to help prevent similar issues in the future. We will share updates if any further action is needed. We sincerely apologize for the disruption this caused and thank you for your patience throughout.

Read the full incident report →

Minor July 30, 2026 LumaLink Integration Service Interruption –

Started Jul 30, 2026, 01:00 PM UTC· resolved Jul 30, 2026, 01:00 PM UTC

  1. resolved Aug 03, 2026, 06:22 PM UTC

    Summary: On July 30th, an internal configuration change unintentionally affected a shared network routing dependency used by certain versions of LumaLink. This interrupted communication between affected LumaLink instances and Luma Health systems, pausing database synchronization with the EHR for approximately two hours. Resolution: Our technical teams identified the issue via internal monitoring alerts, traced it to the configuration change, and resolved it by reverting that change. Communication and database synchronization were fully restored. Next Steps: Our Engineering team is evaluating enhanced monitoring to detect this type of connectivity interruption more quickly in the future, enabling faster response and resolution.

Read the full incident report →

Minor June 17, 2026 Slowness across Luma Platform 2h 12m Luma Health Web (next.lumahealth.io)

Started Jun 17, 2026, 06:36 PM UTC· resolved Jun 17, 2026, 08:49 PM UTC

  1. investigating Jun 17, 2026, 06:36 PM UTC

    We are currently investigating reports of slow performance affecting the Luma Platform. Our engineering team has been engaged and is actively investigating the root cause. Users may experience slower than normal load times and delayed responses during this time.

  2. monitoring Jun 17, 2026, 06:53 PM UTC

    We have identified the root cause of the slow performance affecting the Luma Platform and have implemented a fix. Our engineering team is actively monitoring the systems to confirm full recovery.

  3. monitoring Jun 17, 2026, 07:43 PM UTC

    Our engineering team continues to monitor the Luma Platform following the fix implemented earlier. Performance metrics are trending in the right direction and systems are stabilizing.

  4. resolved Jun 17, 2026, 08:49 PM UTC

    This incident has been resolved. All Luma systems are now operating normally. The performance degradation was caused by an unexpectedly high load on our platform, which impacted response times across all systems. Our engineering team responded quickly, identified the root cause, and implemented the necessary changes to stabilize the environment. We apologize for any disruption this may have caused to your workflows and thank you for your patience throughout this incident.

Read the full incident report →

Minor May 18, 2026 Navigator Slowness Affecting Voice 1h 15m

Started May 18, 2026, 03:19 PM UTC· resolved May 18, 2026, 04:35 PM UTC

  1. investigating May 18, 2026, 03:19 PM UTC

    We are currently investigating reports of slowness in Navigator that is impacting Voice performance. Our team has been alerted and is actively looking into the root cause. Further updates will be provided as we learn more.

  2. identified May 18, 2026, 04:03 PM UTC

    We have identified the root cause of the slowness in Navigator that is impacting Voice performance. Our Engineering team is actively working on a fix and further updates will be provided as we make progress toward resolution.

  3. resolved May 18, 2026, 04:35 PM UTC

    The slowness in Navigator that was impacting Voice performance has been fully resolved. All systems are operating normally. We apologize for any inconvenience this may have caused and thank you for your patience.

Read the full incident report →

Notice May 6, 2026 SFTP Service Disruption 1d EHR/PM Integration System

Started May 06, 2026, 12:59 PM UTC· resolved May 07, 2026, 01:00 PM UTC

  1. resolved May 06, 2026, 12:59 PM UTC

    Summary Our SFTP servers were unavailable following a scheduled maintenance window on our Kubernetes cluster, which resulted in an unexpected configuration change on our load balancer, causing SFTP connections to become unavailable. The service has been fully restored. Who was affected Only customers using SFTP file transfers between 8:00 PM PST (May 5) and 5:00 AM PST (May 6) were impacted. All other services remained fully operational during this period. Action Required If you received connection or transfer errors during the affected window, please re-send your files. They will be processed normally. We apologize for the inconvenience.

Read the full incident report →

Notice March 30, 2026 Luma Health Web intermittent issues 1h 31m Luma Health Web (next.lumahealth.io)

Started Mar 30, 2026, 05:08 PM UTC· resolved Mar 30, 2026, 06:39 PM UTC

  1. investigating Mar 30, 2026, 05:08 PM UTC

    Users may experience intermittent issues when accessing https://next.lumahealth.io. Our Engineering is working on it with the highest possible priority. We will provide updates as soon as they become available. We appreciate your patience and collaboration.

  2. monitoring Mar 30, 2026, 05:27 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Mar 30, 2026, 06:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 4, 2026 Slowness on Schedule View 1h 7m Luma Health Web (next.lumahealth.io)

Started Mar 04, 2026, 03:41 PM UTC· resolved Mar 04, 2026, 04:48 PM UTC

  1. investigating Mar 04, 2026, 03:41 PM UTC

    We're experiencing slowness on the Schedule View and are currently looking into the issue. This is currently causing an inability for certain users to access https://next.lumahealth.io/schedule Patient communication is not impacted at this time.

  2. investigating Mar 04, 2026, 04:07 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Mar 04, 2026, 04:33 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Mar 04, 2026, 04:48 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 4, 2025 Degraded performance on Oracle/Cerner FHIR API 2h 44m EHR/PM Integration System

Started Dec 04, 2025, 04:54 PM UTC· resolved Dec 04, 2025, 07:38 PM UTC

  1. investigating Dec 04, 2025, 04:54 PM UTC

    Our Integrations Monitoring detected that Cerner/Oracle are experiencing a performance issue with their API's effective 8:32 AM PST. We wanted you to be aware that this has been escalated to Cerner/Oracle and they are working the issue.

  2. investigating Dec 04, 2025, 05:26 PM UTC

    The Cerner/Oracle team continues to troubleshoot the ongoing API issue. At this time we have no ETA on a resolution. We will provide you with updates as soon as they become available. Thanks for your patience and collaboration.

  3. monitoring Dec 04, 2025, 05:53 PM UTC

    The Cerner/Oracle FHIR API performance has returned to normal levels. For more information about todays API performance issue, please contact Cerner/Oracle and they can provide root cause once available.

  4. resolved Dec 04, 2025, 07:38 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 18, 2025 Cloudflare Global Network issues 7h 17m Luma Health Web (next.lumahealth.io), Luma Health API, Communication Services, EHR/PM Integration System and 2 more

Started Nov 18, 2025, 01:39 PM UTC· resolved Nov 18, 2025, 08:56 PM UTC

  1. investigating Nov 18, 2025, 01:39 PM UTC

    We were notified by Cloudflare that they're experiencing Global Network issues that may impact Luma Health services. Our team is actively monitoring the situation and will continue to follow Cloudflare's recovery process. We appreciate your patience, and will keep you updated as more information becomes available. For more Information: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

  2. investigating Nov 18, 2025, 02:20 PM UTC

    Our team is still actively monitoring the situation and will continue to follow Cloudflare's recovery process. We appreciate your patience, and will keep you updated as more information becomes available. For more Information: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

  3. monitoring Nov 18, 2025, 02:52 PM UTC

    A fix has been implement by the Cloudflare team and they believe it resolved the global incident, we will keep monitoring their recovery process. We appreciate your patience, and will keep you updated as more information becomes available.

  4. monitoring Nov 18, 2025, 04:08 PM UTC

    We will keep monitoring their recovery process. We appreciate your patience, and will keep you updated as more information becomes available. For more Information: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

  5. resolved Nov 18, 2025, 08:56 PM UTC

    Cloudflare states that this incident has been resolved. For more information: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

Read the full incident report →

Major October 2, 2025 Veradigm API Integration Issues 2h 3m EHR/PM Integration System

Started Oct 02, 2025, 12:23 PM UTC· resolved Oct 02, 2025, 02:26 PM UTC

  1. investigating Oct 02, 2025, 12:23 PM UTC

    We have identified an issue connecting with the Veradigm API (formerly AllScriptsUnity); our engineering team is already investigating the matter and working with Veradigm to resolve the issue. We look forward to resolving this situation and will provide you with updates as soon as they become available. If you're not an API Integrated Veradigm customer, you're not being impacted.

  2. monitoring Oct 02, 2025, 01:50 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Oct 02, 2025, 02:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 23, 2025 System Delays 2h 40m Luma Health Web (next.lumahealth.io), Luma Health API, Communication Services, EHR/PM Integration System and 1 more

Started Sep 23, 2025, 06:21 PM UTC· resolved Sep 23, 2025, 09:02 PM UTC

  1. investigating Sep 23, 2025, 06:21 PM UTC

    We're experiencing system delays and are currently looking into the issue.

  2. investigating Sep 23, 2025, 06:54 PM UTC

    We are continuing to investigate this issue.

  3. investigating Sep 23, 2025, 07:16 PM UTC

    We are continuing to investigate this issue.

  4. identified Sep 23, 2025, 08:05 PM UTC

    The issue has been identified and a fix is being implemented.

  5. monitoring Sep 23, 2025, 08:15 PM UTC

    A fix has been implemented and we are monitoring the results.

  6. resolved Sep 23, 2025, 09:02 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 19, 2025 Resolved: Appointment Time Sync Issue 2h 3m EHR/PM Integration System

Started Aug 19, 2025, 05:28 PM UTC· resolved Aug 19, 2025, 07:32 PM UTC

  1. monitoring Aug 19, 2025, 05:28 PM UTC

    We identified and resolved an issue affecting appointment time sync for a small subset of customers. Between 10:31 AM and 12:40 PM EST today, some appointment reminders may have displayed incorrect times. After the fix was implemented the appointments started to get updated to the correct time. We will provide more updates soon and will proactively reach out to impacted customers.

  2. resolved Aug 19, 2025, 07:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 6, 2025 Impact to Appointment Status Updates 1h 7m Luma Health API, Communication Services

Started May 06, 2025, 05:03 PM UTC· resolved May 06, 2025, 06:10 PM UTC

  1. identified May 06, 2025, 05:03 PM UTC

    We are aware of an issue preventing appointments from being canceled and confirmed as expected. The root cause has been identified and a fix is being prepared. We will post an update in 15 minutes.

  2. monitoring May 06, 2025, 05:35 PM UTC

    We are aware of an issue preventing appointments from being canceled and confirmed as expected. The root cause has been identified and a fix is being prepared. We're also aware of general system delays. We will post an update in 15 minutes.

  3. identified May 06, 2025, 05:39 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring May 06, 2025, 05:42 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved May 06, 2025, 06:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 9, 2025 Slowness on Luma Health 48m Luma Health Web (next.lumahealth.io), Luma Health Patient Web (patient.lumahealth.io)

Started Apr 09, 2025, 04:54 PM UTC· resolved Apr 09, 2025, 05:43 PM UTC

  1. investigating Apr 09, 2025, 04:54 PM UTC

    We're experiencing slowness on Luma Health and are currently looking into the issue. This is currently causing delays for users to use https://next.lumahealth.io and https://patient.lumahealth.io. Patient communication is not impacted at this time.

  2. investigating Apr 09, 2025, 05:20 PM UTC

    We are continuing to investigate this issue.

  3. resolved Apr 09, 2025, 05:43 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 19, 2025 Oracle(Cerner) Integration Issues 5h 56m EHR/PM Integration System

Started Feb 19, 2025, 03:34 PM UTC· resolved Feb 19, 2025, 09:30 PM UTC

  1. investigating Feb 19, 2025, 03:34 PM UTC

    We are currently experiencing an increased rate of failures in our synchronization with Oracle(Cerner) EHR. As a result, customers integrated with Cerner may encounter delays in appointment synchronization and writebacks. Our R&D team is actively investigating the issue. We will provide an update in one hour or sooner if there are any significant developments.

  2. identified Feb 19, 2025, 05:07 PM UTC

    Oracle (Cerner) has confirmed that the problem originates from their Millennium Cloud Services, impacting their FHIR API. This may cause delays in appointment synchronization and write-backs within Luma for customers using that EHR. They're actively working on it, and we will provide updates as soon as they make them available.

  3. monitoring Feb 19, 2025, 06:23 PM UTC

    Oracle (Cerner) has confirmed that they are now stable and we will keep monitoring the situation.

  4. resolved Feb 19, 2025, 09:30 PM UTC

    The issue affecting Oracle (Cerner) EHR Integration has been fully resolved. Synchronization and write-backs are functioning as expected. We will continue to monitor, but no further impact is anticipated. Thank you for your patience.

Read the full incident report →

Minor November 19, 2024 SMS Deliverability Degraded Performance 15m Communication Services, Twilio SMS

Started Nov 19, 2024, 03:52 PM UTC· resolved Nov 19, 2024, 04:07 PM UTC

  1. investigating Nov 19, 2024, 03:52 PM UTC

    Our SMS vendor is currently experiencing degraded performance on SMS programmable messaging, and you may experience delays in SMS deliverability. Our team is working with Twilio to have more information, and we will provide updates as soon as they become available.

  2. resolved Nov 19, 2024, 04:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Major November 14, 2024 Delays on Luma Health 41m Communication Services, EHR/PM Integration System

Started Nov 14, 2024, 06:35 PM UTC· resolved Nov 14, 2024, 07:16 PM UTC

  1. investigating Nov 14, 2024, 06:35 PM UTC

    We're experiencing delays on Luma Health Platform and are currently looking into the issue. This is currently impacting Luma messaging and integration services.

  2. investigating Nov 14, 2024, 06:36 PM UTC

    We are currently experiencing delays on the Luma Health Platform, impacting our messaging and integration services. Our team is actively investigating the issue and working to resolve it as quickly as possible. We appreciate your patience and will provide updates as soon as more information is available. Thank you for your understanding.

  3. monitoring Nov 14, 2024, 06:46 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Nov 14, 2024, 11:21 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 25, 2024 Users unable to send messages on Patient Profile 1h Communication Services

Started Oct 25, 2024, 03:03 PM UTC· resolved Oct 25, 2024, 04:04 PM UTC

  1. investigating Oct 25, 2024, 03:03 PM UTC

    Some users may be unable to send messages to patients using the Patient Profile Chat. Our team is currently investigating the issue.

  2. identified Oct 25, 2024, 03:07 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Oct 25, 2024, 03:14 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Oct 25, 2024, 04:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 24, 2024 Chat Hub Message issue –

Started Oct 24, 2024, 01:30 AM UTC· resolved Oct 24, 2024, 01:30 AM UTC

  1. resolved Oct 24, 2024, 07:33 PM UTC

    In a recent code deployment, our product engineering team released a new version of our Chat Hub feature. This change ended up affecting Luma users with the setting filterChatsByGroupsFacilities enabled - disabling their ability to communicate directly in the Patient Profile. The changes were reverted and this incident is resolved. We apologize for the inconvenience.

Read the full incident report →