Resolved on July 30, 2026.
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.
Update timeline
- 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.
Your product runs on more than Luma Health
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services