Lumos Outage History

Lumos is up right now

Lumos had 18 outages in the last 2 years totaling 69h 16m of downtime — averaging 0.7 incidents per month.

There were 18 Lumos outages since June 3, 2025 totaling 69h 16m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.lumos.com

Minor May 27, 2026

AppStore Permissions - Manual edits to Provisioning and Deprovisioning Flows are not shown until a page refresh

Detected by Pingoru
May 27, 2026, 02:51 PM UTC
Resolved
May 27, 2026, 11:46 PM UTC
Duration
8h 55m
Affected: AppStore
Timeline · 5 updates
  1. investigating May 27, 2026, 02:51 PM UTC

    Manual Edits to AppStore Permissions Provisioning and Deprovisioning Flows in the UI are not being saved. The workaround is to refresh the page after making the changes, and then Save.

  2. investigating May 27, 2026, 03:05 PM UTC

    We are continuing to investigate this issue.

  3. investigating May 27, 2026, 03:06 PM UTC

    Incident being downgraded to Minor - Manual Edits to AppStore Permissions Provisioning and Deprovisioning Flows are being saved, but the updates are not shown in the UI until a page refresh. The workaround is to refresh the page after making the changes.

  4. identified May 27, 2026, 03:57 PM UTC

    We have identified the issue and fix will be released shortly.

  5. resolved May 27, 2026, 11:46 PM UTC

    This incident has been resolved. No data was lost or affected, as the issue was only cosmetic in the AppStore Permissions UI.

Read the full incident report →

Minor May 8, 2026

Delay in processing workflows

Detected by Pingoru
May 08, 2026, 09:40 PM UTC
Resolved
May 08, 2026, 10:00 PM UTC
Duration
19m
Affected: AppStoreAccess ReviewsLifecycle Management
Timeline · 2 updates
  1. monitoring May 08, 2026, 09:40 PM UTC

    We are seeing a delay in some workflows being processed. The issue has been addressed, and all workflows are resuming where they left off.

  2. resolved May 08, 2026, 10:00 PM UTC

    This issue is resolved. All workflows have resumed normal processing with no delays.

Read the full incident report →

Minor April 27, 2026

Manually launched integration syncs failing to start

Detected by Pingoru
Apr 27, 2026, 08:46 PM UTC
Resolved
Apr 27, 2026, 09:36 PM UTC
Duration
50m
Affected: Hosted IntegrationsOn-Prem Integrations
Timeline · 2 updates
  1. identified Apr 27, 2026, 08:46 PM UTC

    Manually launched integration syncs are failing to launch. Our team has identified where the issue was introduced and is rolling back the change now. Regularly scheduled syncs are unaffected and should continue as normal.

  2. resolved Apr 27, 2026, 09:36 PM UTC

    This issue is now resolved—any manually launched syncs should proceed without issue.

Read the full incident report →

Minor April 21, 2026

Missing Activity Log Events

Detected by Pingoru
Apr 21, 2026, 05:42 PM UTC
Resolved
Apr 21, 2026, 09:39 PM UTC
Duration
3h 57m
Affected: Platform
Timeline · 4 updates
  1. investigating Apr 21, 2026, 05:42 PM UTC

    We are currently investigating an issue where Activity Log events are failing to display in the UI.

  2. identified Apr 21, 2026, 05:49 PM UTC

    Our engineers have identified the root cause - events have been queued but are delayed.

  3. monitoring Apr 21, 2026, 05:57 PM UTC

    All events will be restored as the queue drains. The team will continue monitoring through a full resolution.

  4. resolved Apr 21, 2026, 09:39 PM UTC

    This incident has been resolved. All Activity Log events are visible again, and new Activity Log events will be displayed without a delay.

Read the full incident report →

Notice March 18, 2026

Slack and ITSM Notification Failures

Detected by Pingoru
Mar 18, 2026, 11:00 PM UTC
Resolved
Mar 18, 2026, 11:00 PM UTC
Duration
Timeline · 1 update
  1. resolved Mar 19, 2026, 02:28 AM UTC

    A transient issue impacting the delivery of Slack and ITSM communications was identified. A subset of customers may see error tasks generated as a result of the access requests filed during the time of this issue.

Read the full incident report →

Major February 18, 2026

Provisioning Workflow Getting Stuck

Detected by Pingoru
Feb 18, 2026, 04:31 PM UTC
Resolved
Feb 18, 2026, 08:19 PM UTC
Duration
3h 47m
Affected: AppStoreLifecycle Management
Timeline · 4 updates
  1. investigating Feb 18, 2026, 04:31 PM UTC

    Our team is currently investigating an issue where access requests are getting 'stuck' in the provisioning phase. We'll provide updates on a root cause and resolution ASAP.

  2. investigating Feb 18, 2026, 04:33 PM UTC

    We are continuing to investigate this issue.

  3. identified Feb 18, 2026, 05:31 PM UTC

    The issue has been identified, and we are rolling out a fix that will resume all Access Requests that became 'stuck' with the Pending Provisioning status.

  4. resolved Feb 18, 2026, 08:19 PM UTC

    This incident has been resolved. Any Access Requests that became 'stuck' with the "Pending Provisioning" status have resumed and will continue running as expected now.

Read the full incident report →

Minor February 12, 2026

Inability to use Search Bar in UI Popups

Detected by Pingoru
Feb 12, 2026, 04:19 PM UTC
Resolved
Feb 12, 2026, 04:40 PM UTC
Duration
21m
Affected: AppStoreAccess ReviewsLifecycle Management
Timeline · 3 updates
  1. identified Feb 12, 2026, 04:19 PM UTC

    The team has observed an issue impacting ability to utilize the search bar in popups throughout the UI. Our engineers have identified a root cause of the issue and are working to mitigate.

  2. monitoring Feb 12, 2026, 04:38 PM UTC

    Our team has deployed a fix and are monitoring for continued success within the UI. Please refresh your browser to update.

  3. resolved Feb 12, 2026, 04:40 PM UTC

    Confirming all tests demonstrate issue resolution. The search bar is now working as expected, and all functionality has been restored.

Read the full incident report →

Critical February 10, 2026

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

Detected by Pingoru
Feb 10, 2026, 05:15 AM UTC
Resolved
Feb 10, 2026, 11:45 AM UTC
Duration
6h 29m
Affected: On-Prem Integrations
Timeline · 5 updates
  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.

Read the full incident report →

Minor January 22, 2026

Lumos is not redirecting to the login page for logged out users when following links

Detected by Pingoru
Jan 22, 2026, 11:05 PM UTC
Resolved
Jan 23, 2026, 01:58 PM UTC
Duration
14h 53m
Affected: Platform
Timeline · 3 updates
  1. investigating Jan 22, 2026, 11:05 PM UTC

    Lumos is not redirecting to the login page for logged out users when following links to https://app.lumosidentity.com/access_reviews. The workaround is to navigate to https://app.lumosidentity.com/login and login, and then follow the Lumos link again.

  2. investigating Jan 23, 2026, 02:38 AM UTC

    We've resolved the the issue for logged out users visiting https://app.lumosidentity.com/access_reviews, logged out users are now correctly redirected to the login page when following Access Review links. We are still investigating occurrences of logged out users getting "Something went wrong" dialog on their first login attempt. The workaround is selecting "Sign in" and logging in again which will result in a successful login.

  3. resolved Jan 23, 2026, 01:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 14, 2026

Database Maintenance

Detected by Pingoru
Jan 14, 2026, 11:00 PM UTC
Resolved
Jan 14, 2026, 11:00 PM UTC
Duration
Timeline · 1 update
  1. resolved Jan 14, 2026, 11:29 PM UTC

    Our engineers ran a minor DB maintenance event. Some syncs may have slowed during this period, but no disruptions were observed.

Read the full incident report →

Minor December 18, 2025

Provision to App Incorrectly Provisioning to Permissions

Detected by Pingoru
Dec 18, 2025, 06:31 PM UTC
Resolved
Dec 19, 2025, 12:26 AM UTC
Duration
5h 55m
Affected: AppStore
Timeline · 3 updates
  1. investigating Dec 18, 2025, 08:56 PM UTC

    We're currently investigating an issue causing 'Provision to App' access requests to incorrectly include a permission. This is only impacting applications where AppStore permissions are visible.

  2. identified Dec 18, 2025, 08:58 PM UTC

    We've identified the root cause and are working to deploy a fix.

  3. resolved Dec 19, 2025, 12:26 AM UTC

    The team has rolled out a fix, and all applications are now provisioning access as expected.

Read the full incident report →

Minor December 17, 2025

Increased failure rate for Okta permission syncs

Detected by Pingoru
Dec 17, 2025, 04:58 PM UTC
Resolved
Dec 17, 2025, 05:41 AM UTC
Duration
Affected: Platform
Timeline · 2 updates
  1. identified Dec 12, 2025, 11:20 PM UTC

    Our team has identified that there's been an increase in errors related to Okta permission syncs. We're still confirming the scope of the issue, but it appears that these aren't consistent failures—permission data coming from Okta may be slightly behind as a result, and account syncs are not affected. We'll provide updates as soon as we have more information.

  2. resolved Dec 17, 2025, 04:58 PM UTC

    We resolved an issue that caused intermittent permission sync failures for a small subset of IdP integrations (including Okta). Identity and account syncs were not affected. Permission syncing is now operating normally, and we are continuing to monitor.

Read the full incident report →

Minor October 15, 2025

Okta 'Remove From Group' steps are failing in Lumos

Detected by Pingoru
Oct 15, 2025, 07:21 AM UTC
Resolved
Oct 15, 2025, 04:35 AM UTC
Duration
Affected: Platform
Timeline · 3 updates
  1. investigating Oct 14, 2025, 02:14 PM UTC

    Our team is aware of an issue that's resulting in 'Remove From Group' Okta operations failing. If impacted, you may see errors associated with these operations in the activity log, or in the form of error tasks or notifications. We're investigating the issue and will provide updates as we learn more.

  2. monitoring Oct 14, 2025, 04:42 PM UTC

    A fix has been deployed, and our team is monitoring to ensure that the issue is corrected moving forward. We have an additional line of effort that's prioritizing retroactively correcting the failed group removal operations, so any failures should be completed successfully soon. More updates to come.

  3. resolved Oct 15, 2025, 07:21 AM UTC

    Our team has now corrected the failed group removal operations, and any affected requests should now be marked as completed.

Read the full incident report →

Major August 29, 2025

Slow Loading Speeds Across Lumos

Detected by Pingoru
Aug 29, 2025, 07:58 PM UTC
Resolved
Aug 29, 2025, 07:59 PM UTC
Duration
56s
Affected: Platform
Timeline · 6 updates
  1. investigating Aug 29, 2025, 04:26 PM UTC

    The team is investigating an ongoing issue causing pages to load very slowly within the Lumos Platform. All portions of the product are in working order, but loading speeds may temporarily reduce usability.

  2. investigating Aug 29, 2025, 05:05 PM UTC

    The team is continuing to investigate and has discovered increased impact of the loading slowness on platform functionality. Some aspects of Lumos will not work as expected, likely due to timeout errors. We're actively pinning down a root cause and working to restore full function.

  3. monitoring Aug 29, 2025, 05:28 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring Aug 29, 2025, 05:59 PM UTC

    Performance appears to be fully restored, and our team is continuing to investigate the root cause to mitigate future issues. We recommend re-trying any failed actions at this time.

  5. monitoring Aug 29, 2025, 07:58 PM UTC

    We are continuing to monitor for any further issues.

  6. resolved Aug 29, 2025, 07:59 PM UTC

    Loading speeds have been restored, and platform performance is fully operational.

Read the full incident report →

Minor June 25, 2025

Lumos On-prem proxy server is down

Detected by Pingoru
Jun 25, 2025, 11:45 PM UTC
Resolved
Jun 26, 2025, 01:08 AM UTC
Duration
1h 23m
Affected: Platform
Timeline · 2 updates
  1. investigating Jun 26, 2025, 12:00 AM UTC

    On-prem agents may be inoperative. We are currently investigating this issue.

  2. resolved Jun 26, 2025, 02:30 AM UTC

    We successfully deployed a fix and confirmed that the on-prem-proxy-server is now working as expected.

Read the full incident report →

Notice June 12, 2025

Third Party Incidents - Proactive Updates

Detected by Pingoru
Jun 12, 2025, 07:09 PM UTC
Resolved
Jun 12, 2025, 08:39 PM UTC
Duration
1h 29m
Affected: Platform
Timeline · 2 updates
  1. identified Jun 12, 2025, 07:09 PM UTC

    There is currently an issue impacting Google Cloud Platform, and consequently WorkOS, which could have impacts on the Lumos platform. We are not certain of the scope of issue quite yet, but please note that all is functioning as expected on the Lumos side and this is unfortunately outside of our control. We will continue monitoring and provide updates as we can.

  2. resolved Jun 12, 2025, 08:39 PM UTC

    The third party incidents are not impacting Lumos.

Read the full incident report →

Minor June 5, 2025

Delay in processing activity log events

Detected by Pingoru
Jun 05, 2025, 10:45 PM UTC
Resolved
Jun 06, 2025, 06:06 PM UTC
Duration
19h 21m
Affected: Platform
Timeline · 6 updates
  1. investigating Jun 05, 2025, 10:45 PM UTC

    We are aware of an issue resulting in delayed processing of Activity Log events. Customers visiting the Activity Log may see entries appearing approximately 10-12 hours after the ‘Ended’ timestamp of those events. We are actively investigating the issue and will provide regular updates.

  2. investigating Jun 05, 2025, 10:45 PM UTC

    The team is continuing to investigate the root cause.

  3. identified Jun 05, 2025, 11:15 PM UTC

    The team has identified that any events taking place after 5am EST on 6/5 will take ~1 day to register. Rest assured, these events are being logged as expected, but the display in the Activity Log is indeed delayed.

  4. monitoring Jun 06, 2025, 12:57 AM UTC

    Our engineers have found the root cause of the issue causing the delay in Activity Log events. We're working to implement a fix to drain the queue as quickly as possible.

  5. monitoring Jun 06, 2025, 01:52 PM UTC

    The root cause has been identified and addressed, and the event queue is continuing to drain. We will provide further updates as soon as we have them.

  6. resolved Jun 06, 2025, 06:32 PM UTC

    The Activity Log queue is now back to normal functionality! This issue is resolved.

Read the full incident report →

Critical June 3, 2025

Access reviews are not loading

Detected by Pingoru
Jun 03, 2025, 01:56 PM UTC
Resolved
Jun 03, 2025, 03:28 PM UTC
Duration
1h 32m
Affected: Platform
Timeline · 3 updates
  1. investigating Jun 03, 2025, 01:56 PM UTC

    We're investigating reports that access reviews are failing to load. From our initial investigation, this appears to be widespread.

  2. monitoring Jun 03, 2025, 02:04 PM UTC

    Access reviews are now loading as expected. We believe we've identified and corrected the root cause, and we're monitoring to confirm that all is back to normal.

  3. resolved Jun 03, 2025, 03:28 PM UTC

    Behavior has returned to normal.

Read the full incident report →