Luma Health Outage History

Luma Health is up right now

Luma Health had 19 outages in the last 2 years totaling 49h 59m of downtime — averaging 0.8 incidents per month.

There were 19 Luma Health outages since June 28, 2024 totaling 49h 59m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.lumahealth.io

Minor May 18, 2026

Navigator Slowness Affecting Voice

Detected by Pingoru
May 18, 2026, 03:19 PM UTC
Resolved
May 18, 2026, 04:35 PM UTC
Duration
1h 15m
Timeline · 3 updates
  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

Detected by Pingoru
May 06, 2026, 12:59 PM UTC
Resolved
May 06, 2026, 12:59 PM UTC
Duration
Affected: EHR/PM Integration System
Timeline · 1 update
  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

Slowness across Luma Platform

Detected by Pingoru
Mar 30, 2026, 08:25 PM UTC
Resolved
Mar 31, 2026, 04:14 AM UTC
Duration
7h 48m
Affected: Luma Health Web (next.lumahealth.io)Luma Health APICommunication ServicesLuma Health Patient Web (patient.lumahealth.io)
Timeline · 11 updates

Read the full incident report →

Notice March 30, 2026

Luma Health Web intermittent issues

Detected by Pingoru
Mar 30, 2026, 05:08 PM UTC
Resolved
Mar 30, 2026, 06:39 PM UTC
Duration
1h 31m
Affected: Luma Health Web (next.lumahealth.io)
Timeline · 3 updates
  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

Detected by Pingoru
Mar 04, 2026, 03:41 PM UTC
Resolved
Mar 04, 2026, 04:48 PM UTC
Duration
1h 7m
Affected: Luma Health Web (next.lumahealth.io)
Timeline · 4 updates
  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

Detected by Pingoru
Dec 04, 2025, 04:54 PM UTC
Resolved
Dec 04, 2025, 07:38 PM UTC
Duration
2h 44m
Affected: EHR/PM Integration System
Timeline · 4 updates
  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

Detected by Pingoru
Nov 18, 2025, 01:39 PM UTC
Resolved
Nov 18, 2025, 08:56 PM UTC
Duration
7h 17m
Affected: Luma Health Web (next.lumahealth.io)Luma Health APICommunication ServicesEHR/PM Integration SystemLuma Health Patient Web (patient.lumahealth.io)Reporting and Datawarehouse
Timeline · 5 updates
  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

Detected by Pingoru
Oct 02, 2025, 12:23 PM UTC
Resolved
Oct 02, 2025, 02:26 PM UTC
Duration
2h 3m
Affected: EHR/PM Integration System
Timeline · 3 updates
  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

Detected by Pingoru
Sep 23, 2025, 06:21 PM UTC
Resolved
Sep 23, 2025, 09:02 PM UTC
Duration
2h 40m
Affected: Luma Health Web (next.lumahealth.io)Luma Health APICommunication ServicesEHR/PM Integration SystemReporting and Datawarehouse
Timeline · 6 updates
  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

Detected by Pingoru
Aug 19, 2025, 05:28 PM UTC
Resolved
Aug 19, 2025, 07:32 PM UTC
Duration
2h 3m
Affected: EHR/PM Integration System
Timeline · 2 updates
  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

Detected by Pingoru
May 06, 2025, 05:03 PM UTC
Resolved
May 06, 2025, 06:10 PM UTC
Duration
1h 7m
Affected: Luma Health APICommunication Services
Timeline · 5 updates
  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

Detected by Pingoru
Apr 09, 2025, 04:54 PM UTC
Resolved
Apr 09, 2025, 05:43 PM UTC
Duration
48m
Affected: Luma Health Web (next.lumahealth.io)Luma Health Patient Web (patient.lumahealth.io)
Timeline · 3 updates
  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

Detected by Pingoru
Feb 19, 2025, 03:34 PM UTC
Resolved
Feb 19, 2025, 09:30 PM UTC
Duration
5h 56m
Affected: EHR/PM Integration System
Timeline · 4 updates
  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

Detected by Pingoru
Nov 19, 2024, 03:52 PM UTC
Resolved
Nov 19, 2024, 04:07 PM UTC
Duration
15m
Affected: Communication ServicesTwilio SMS
Timeline · 2 updates
  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

Detected by Pingoru
Nov 14, 2024, 06:35 PM UTC
Resolved
Nov 14, 2024, 07:16 PM UTC
Duration
41m
Affected: Communication ServicesEHR/PM Integration System
Timeline · 4 updates
  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

Detected by Pingoru
Oct 25, 2024, 03:03 PM UTC
Resolved
Oct 25, 2024, 04:04 PM UTC
Duration
1h
Affected: Communication Services
Timeline · 4 updates
  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

Detected by Pingoru
Oct 24, 2024, 07:33 PM UTC
Resolved
Oct 24, 2024, 01:30 AM UTC
Duration
Timeline · 1 update
  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 →

Major June 28, 2024

Email Messages Outage

Detected by Pingoru
Jun 28, 2024, 10:47 PM UTC
Resolved
Jun 29, 2024, 03:30 AM UTC
Duration
4h 42m
Affected: Communication Services
Timeline · 4 updates
  1. investigating Jun 28, 2024, 10:47 PM UTC

    Our Engineering team has identified that our email vendor unexpectedly interrupted our service. We're actively working to identify the root cause and we will also work on a replay strategy as soon as possible.

  2. identified Jun 28, 2024, 11:14 PM UTC

    Our Engineering team is in contact with our vendor so they can re-establish our services as soon as possible. We will provide new updates as soon as they become available.

  3. monitoring Jun 29, 2024, 02:58 AM UTC

    We have routed services to our backup email vendor and email service is restored. We will update again when we have moved traffic back to our primary email vendor.

  4. resolved Jun 29, 2024, 03:30 AM UTC

    We have switched email providers to restore the service, and messages will be sent without any problems in the future.

Read the full incident report →