Lumos incident
Some on-prem connector syncs are incorrectly returning all accounts as inactive
Resolved after 6 hours 29 minutes, affecting On-Prem Integrations, on February 10, 2026.
We have deployed the rollback and have successfully verified that the root issue has been resolved. We have launched corrected syncs for impacted domains and will continue to monitor them.
Affected components
Update timeline
- investigating Feb 10, 2026, 06:49 AM UTC
We are investigating an incident causing offboarding workflows to be erroneously triggered by on-prem, source-of-truth application syncs. Some customers may be impacted during this time. We are actively working to mitigate and resolve this issue.
- investigating Feb 10, 2026, 06:54 AM UTC
We are continuing to investigate this issue.
- identified Feb 10, 2026, 10:08 AM UTC
We’ve identified the root cause of the issue and are deploying the rollback. In the interim, we’ve also temporarily disabled all syncs as of Feb 9 10:08 PM PT while we roll out the fixed code.
- monitoring Feb 10, 2026, 11:49 AM UTC
We have deployed the rollback and have successfully verified that the root issue has been resolved. We have launched corrected syncs for impacted domains and will continue to monitor them.
- resolved Feb 10, 2026, 03:00 PM UTC
The syncs have been completed successfully, resolving any incorrect data.
Your product runs on more than Lumos
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