The incident has been resolved and service fully restored. The root cause was a change to our load balancer getting stuck mid-deployment -- resolving that issue resulted in the load balancer being deleted and re-created. This process only took about a minute, but the way DNS results are cached by ISPs and browsers meant the new load balancer address took somewhat longer to propagate to all end users.
Posted Sep 18, 2020 - 12:18 PDT
Monitoring
A fix has been implemented and we are monitoring the results.
Posted Sep 18, 2020 - 10:48 PDT
Identified
We're experiencing an elevated level of errors on Luma Health and are currently looking into the issue. This is currently causing an inability for certain users to use https://next.lumahealth.io and https://patient.lumahealth.io and associated services.
Patient communication is not impacted at this time.
Posted Sep 18, 2020 - 10:38 PDT
This incident affected: Luma Health Web (next.lumahealth.io) and Luma Health Patient Web (patient.lumahealth.io).