Lumos incident

Some on-prem connector syncs are incorrectly returning all accounts as inactive

Critical Resolved View vendor source →

Lumos experienced a critical incident on February 10, 2026 affecting On-Prem Integrations, lasting 6h 29m. The incident has been resolved; the full update timeline is below.

Started
Feb 10, 2026, 05:15 AM UTC
Resolved
Feb 10, 2026, 11:45 AM UTC
Duration
6h 29m
Detected by Pingoru
Feb 10, 2026, 05:15 AM UTC

Affected components

On-Prem Integrations

Update timeline

  1. 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.

  2. investigating Feb 10, 2026, 06:54 AM UTC

    We are continuing to investigate this issue.

  3. 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.

  4. 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.

  5. resolved Feb 10, 2026, 03:00 PM UTC

    The syncs have been completed successfully, resolving any incorrect data.