Luma Health Incident History

1. resolvedSep 1 · 17:21 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.

Reported by Luma Health on their status page.

1. resolvedAug 26 · 18:52 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.

Reported by Luma Health on their status page.