Resolved after 3 hours 26 minutes, affecting Luma Health Web (next.lumahealth.io), on June 11, 2026.
This incident has been resolved. The slowness affecting Luma services has been fully addressed and performance has returned to normal levels. Earlier today, a large-scale data processing operation triggered an unexpected spike in our infrastructure, which led to the slowness some users experienced across Luma services. Our Engineering team identified the root cause, deployed a fix, and is continuing to make improvements to prevent this from happening again.
Affected components
Update timeline
- investigating Jun 11, 2026, 04:31 PM UTC
We are currently investigating reports of slowness in the Luma Platform. Our team is actively working to identify the root cause.
- identified Jun 11, 2026, 05:01 PM UTC
We have identified the issue causing the slowness in Luma services. Our Engineering team is actively working on a fix and making progress toward full resolution.
- identified Jun 11, 2026, 06:02 PM UTC
We have identified the issue impacting Luma services performance. Our Engineering team is still working on a fix and is progressing toward a complete resolution.
- monitoring Jun 11, 2026, 06:28 PM UTC
A fix has been deployed and we are monitoring the results. Luma services are recovering and performance is returning to normal levels.
- resolved Jun 11, 2026, 07:58 PM UTC
This incident has been resolved. The slowness affecting Luma services has been fully addressed and performance has returned to normal levels. Earlier today, a large-scale data processing operation triggered an unexpected spike in our infrastructure, which led to the slowness some users experienced across Luma services. Our Engineering team identified the root cause, deployed a fix, and is continuing to make improvements to prevent this from happening again.
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