Obsidian Security Outage History
Obsidian Security is up right nowObsidian Security had 28 outages in the last 2 years totaling 357h 49m of downtime — averaging 1.2 incidents per month.
There were 28 Obsidian Security outages since August 21, 2024 totaling 357h 49m of downtime. Each is summarised below — incident details, duration, and resolution information.
[US Region] - Delayed Identity-Centric Alerts
Timeline · 2 updates
- monitoring Jun 12, 2026, 04:31 PM UTC
We have identified an issue that delayed a subset of identity-centric detections and related alert notifications within the Obsidian US environment beginning on 06/03/26. A fix has been applied, and backlog processing for the affected detections is in progress. As processing continues, customers may receive delayed alerts generated from previously queued detections. We are actively monitoring recovery and will share another update once backlog processing is complete.
- resolved Jun 13, 2026, 01:08 AM UTC
This issue is resolved. We have verified that the issue affecting a subset of identity-centric detections and related alert notifications within the Obsidian US environment has been fully mitigated. Alerting is operating as expected, and this incident is now resolved.
[US Region] - Subset of Alerts Delayed
Timeline · 2 updates
- investigating Jun 09, 2026, 02:38 PM UTC
We are investigating an issue that may result in delayed delivery of batch (non-real-time) alerts for a subset of customers within the US Region. At this time, real-time alerting is not impacted. Our team is actively working to restore normal processing and reduce any alerting delays. We will continue to provide updates as we make progress.
- resolved Jun 09, 2026, 03:29 PM UTC
This issue is resolved. We have taken mitigating actions to restore processing, and batch (non-real-time) alerts are now processing normally. Alerting workflows impacted by this issue have resumed as expected, and we are no longer seeing ongoing delay related to this event.
[US Region] - Subset of threat detections delayed
Timeline · 4 updates
- investigating May 27, 2026, 12:40 PM UTC
We are currently investigating an issue affecting a subset of threat detections in US region environments that may result in delayed alerting for impacted detections.
- identified May 27, 2026, 01:09 PM UTC
We have identified the underlying issue affecting a subset of threat detections in US region environments and are taking actions to fully mitigate the impact. We will continue to provide updates as progress is made.
- monitoring May 27, 2026, 01:44 PM UTC
Mitigation actions have been fully implemented for the issue affecting a subset of threat detections in US region environments. We are monitoring and reviewing telemetry to confirm the issue has been fully addressed and will provide further updates as needed
- resolved May 27, 2026, 02:25 PM UTC
We have verified that the issue affecting a subset of threat detections in US region environments has been fully mitigated. Alerting is operating as expected, and this incident is now resolved.
Subset of Detections Delayed
Timeline · 4 updates
- investigating May 15, 2026, 03:10 PM UTC
Monitoring has detected a recurrence of the issue impacting a subset of threat detections, and investigation has resumed. We are actively investigating and will provide further updates as our investigation progresses.
- investigating May 15, 2026, 04:49 PM UTC
We are continuing to investigate the root cause of the issue affecting a subset of threat detections. Our team remains actively engaged, and we will provide additional updates as more information becomes available.
- monitoring May 15, 2026, 07:25 PM UTC
The root cause of the issue affecting a subset of threat detections has been identified, and corrective actions have been taken. We are currently monitoring to ensure full resolution and will provide additional updates as needed.
- resolved May 15, 2026, 09:03 PM UTC
This incident has been resolved. Monitoring has confirmed that service has returned to normal operation, and threat detections are processing as expected.
Subset of detections delayed
Timeline · 2 updates
- investigating May 15, 2026, 02:05 PM UTC
We are currently investigating an issue impacting a subset of threat detections and resulting in delayed alerting for impacted detections
- resolved May 15, 2026, 02:47 PM UTC
A fix to address an issue resulting in detection and alerting delays for a subset of threat detections has been deployed. Telemetry and post fix validation confirm a return to normal service operation.
Not Found ( HTTP-404) Errors when attempting to access Obsidian Environment
Timeline · 3 updates
- investigating Mar 11, 2026, 02:05 PM UTC
We are currently investigating an issue that is resulting in users encountering a "Not Found" / HTTP-404 error when attempting to access Obsidian environments.
- investigating Mar 11, 2026, 02:07 PM UTC
We are currently investigating an issue that is resulting in users encountering a "Not Found" / HTTP-404 error when attempting to access Obsidian environments.
- resolved Mar 11, 2026, 02:34 PM UTC
A fix to address the issue of "Not Found" errors being displayed upon attempt to load Obsidian Environments has been released, and telemetry and post fix validation confirm a return to normal service operation.
Activity timeline delay
Timeline · 5 updates
- investigating Mar 11, 2026, 07:51 AM UTC
We have identified an issue that may result in delayed event population within the activity module. Our teams are currently working to mitigate the issue and any updates will be posted on this incident notification.
- investigating Mar 11, 2026, 08:57 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Mar 11, 2026, 08:59 AM UTC
The activity data is catching up, and we are closely monitoring the system's performance. We will provide another update once the system is fully up to date with the activity data.
- monitoring Mar 11, 2026, 11:23 AM UTC
The backfill process is nearing completion, and activity data is now mostly up to date. We will continue to monitor the system as the remaining backfill completes
- resolved Mar 11, 2026, 11:47 AM UTC
This incident has been resolved.
Intermittent failures when loading Obsidian admin console
Timeline · 4 updates
- investigating Feb 09, 2026, 09:06 PM UTC
We are currently investing an issue resulting in intermittent issues loading the Obsidian admin console and modules within.
- investigating Feb 09, 2026, 10:06 PM UTC
We are continuing to investigate an issue currently impacting the US environment and resulting in intermittent or slow page loads when accessing the Obsidian UI. At this time, all other environments remain operational and unaffected. Our engineering team is actively working to isolate the underlying root cause and mitigate impact. We will provide a further update in 1 hour, or sooner, as more information becomes available. Thank you for your patience while we work to restore normal operation.
- monitoring Feb 09, 2026, 10:37 PM UTC
We have implemented mitigation actions to address the issue impacting the US / live environment, and we are seeing improved performance at this time. Our engineering team is actively monitoring the system to ensure stability and will continue to take additional corrective steps as needed. We will provide another update in 1 hour, or sooner, if there are any significant changes.
- resolved Feb 09, 2026, 10:50 PM UTC
We have fully resolved the issue that was impacting the US environment. System performance and operation have returned to normal levels, and all services are functioning as expected. Our team will continue to monitor the environment closely, but no further impact is anticipated at this time. Thank you for your patience while we work to restore normal operation.
Web UI slowness for US region
Timeline · 1 update
- resolved Feb 09, 2026, 07:23 PM UTC
We see US region got UI response slowness. Team identified it related to a backend issue. A fix was applied. The issue is resolved at 11:20AM
Service partially down(threat, activity) for US region
Timeline · 7 updates
- investigating Jan 05, 2026, 01:44 AM UTC
Our systems have detected an issue impacting threat that may result in "No Data" being displayed for a subset of settings. Our engineering team is currently working to address the underlying issue, and any updates will be posted on this incident notification.
- investigating Jan 05, 2026, 01:46 AM UTC
We are continuing to investigate this issue.
- identified Jan 05, 2026, 02:26 AM UTC
Update to Scope of Impact: Our ongoing investigation into this issue and identification of cause has resulted in a clarification on the scope of impact. Impact resulting from this issue is now scoped to the threat and activity modules, including APIs underlying these modules Impacted customers will encounter "An error has occurred" error upon attempt to load these impacted modules. Our engineering team is currently working to address the underlying issue, and any updates will be posted on this incident notification.
- identified Jan 05, 2026, 02:30 AM UTC
Update to Scope of Impact: Our ongoing investigation into this issue and identification of cause has resulted in a clarification on the scope of impact. Impact resulting from this issue is now scoped to the threat, activity, dashboards, and objects modules, including APIs underlying these modules Impacted customers will encounter "An error has occurred" error upon attempt to load these impacted modules. Our engineering team is currently working to address the underlying issue, and any updates will be posted on this incident notification.
- identified Jan 05, 2026, 05:27 AM UTC
We have identified the root cause of the issue impacting the threat, activity, dashboards, and objects modules in the US region and are currently implementing a fix. Impacted customers may still encounter "An error has occurred" when loading these modules while the fix is being rolled out. We will provide another update once the deployment is complete and we have validated full restoration of service.
- monitoring Jan 05, 2026, 06:35 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jan 05, 2026, 01:04 PM UTC
After monitoring system performance and fully confirming the previously deployed fix to be effective, we are now marking this incident as resolved. All affected functionality has been fully restored, and customers should no longer encounter "An error has occurred" when loading these modules. Thank you for your patience while we worked through and resolved this incident.
Obsidian Administration UI Access - Cloudflare Outage
Timeline · 2 updates
- investigating Dec 05, 2025, 09:07 AM UTC
Obsidian is aware of and tracking the widespread issues with Cloudflare which may be impacting access to the Administration UI. We will post additional updates as we learn of recovery and next steps.
- resolved Dec 05, 2025, 09:22 AM UTC
This incident has been resolved. Our monitoring is no longer showing elevated error rates and all components across the Obsidian platform are fully operational.
Obsidian Browser Extension ver. 1.13.x Page Unresponsive Errors
Timeline · 3 updates
Errors when authenticating to the Obsidian admin portal
Timeline · 4 updates
- investigating Nov 06, 2025, 07:03 PM UTC
We are currently investigating an issue with our Admin portal authentication service which might prevent users from successfully authenticating to the Obsidian platform. Impacted users will encounter an error indicating "No access granted" when attempting to authenticate. Our teams are currently investigating the issue and any updates will be posted on this incident notification.
- investigating Nov 06, 2025, 07:35 PM UTC
We have identified the root cause of the issue resulting in users encountering a "No access granted" error when attempting to authenticate to the Obsidian platform, and are in the process of taking mitigation actions. Additional updates will be posted on this incident notification.
- identified Nov 06, 2025, 07:35 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Nov 06, 2025, 07:39 PM UTC
This issue has been resolved. A fix addressing the underlying issue was implemented and authentication services have returned to normal operation.
Subset of Salesforce posture rule unexpectedly changed to passing
Timeline · 2 updates
Threat alerts and a subset of historical activity not visible within administrator UI
Timeline · 4 updates
- investigating Aug 06, 2025, 02:48 PM UTC
We are are currently investigating an issue resulting in threat alerts not being visible within the administrator UI threat module. Our teams are actively working to resolve the issue, and we'll provide updates on this incident as they become available.
- identified Aug 06, 2025, 07:53 PM UTC
We have identified the cause of the underlying issue resulting in alerts not being visible within the administrator UI threat module, and are currently implementing a fix. Further updates will be provided once the fix has been fully deployed and issue mitigation validated.
- identified Aug 06, 2025, 11:07 PM UTC
The scope of impact for this issue has been updated: A fix for the issue resulting in threat alerts not being visible within the administrator UI threat module has been deployed and verified. During the process of development and deployment, it was additionally found that for a subset for customers within our US environment, a subset of historical activity is not visible within the activity module. The impact of this secondary issue is isolated solely to the ability for the underlying data to be displayed within the UI, with no interruption to threat detections or action policies. A fix for this secondary issue is being prepared and tested, and further updates will be provided once it has been fully deployed and issue mitigation validated.
- resolved Aug 07, 2025, 04:22 PM UTC
This incident has been resolved. Fixes addressing UI visibility for threat alerts and historical activity data have each been deployed, and post fix validation confirms each to have been fully mitigated.
Increased Streaming Detection Lag and Potential Threat Alert Generation Delay
Timeline · 2 updates
- investigating Jul 17, 2025, 07:13 PM UTC
Our monitoring has identified an issue within our US environment resulting in increased lag on streaming detections for a subset of customers. While no direct impact has been identified at this time, there is the possibility that alerts resulting from detections designated as streaming might be delayed as time progresses. We will post additional updates as we continue our investigation and mitigation efforts.
- resolved Jul 18, 2025, 09:31 PM UTC
This incident has been resolved. Actions to mitigate the conditions resulting in lag on streaming detections within the US environment have been taken and telemetry has confirmed the issue to been fully mitigated.
[System Notice] Data Sub-Processor Change/Update
Timeline · 1 update
No Routes error message encountered when onboarding oAuth based connections
Timeline · 2 updates
- investigating Jul 08, 2025, 02:30 PM UTC
We are currently investigating an issue resulting in a "No Routes" error message being encountered when attempting to onboard connections leveraging oAuth authentication. Examples of such connections include Microsoft Graph and Slack. Additional updates will be provided via this posting as our investigation progresses and the issue is mitigated.
- resolved Jul 08, 2025, 03:16 PM UTC
This incident has been resolved. We have identified the root cause of the issue resulting in a "No Routes" error being encountered when attempting to onboard oAuth based connections. A fix has now been deployed to all environments, and post fix validation and telemetry have confirmed the issue has been fully mitigated. If you encounter any further issues, please reach out to our support team.
Intermittent Delays In Outbound Alert Notifications
Timeline · 3 updates
- identified Jun 23, 2025, 10:05 PM UTC
Our monitoring identified an issue within our action policy framework that could have resulted in outbound notifications / actions to have not intermittently triggered on time for a subset of generated alerts starting June 17th 2025. We have put in measures to mitigate the impact and are monitoring closely. As a result of these measures, the missed notifications/actions are going to be retroactively generated, which may present itself as a delayed notification / action. Please reach out to our support team should you have additional questions
- identified Jul 01, 2025, 02:59 PM UTC
This issue has been resolved. A permanent fix addressing the underlying issue was implemented, and on-going monitoring has shown no further outbound notification / action delays following deployment of the fix.
- resolved Jul 01, 2025, 03:00 PM UTC
This incident has been resolved.
Potential Threat Alert Generation Delay
Timeline · 4 updates
- identified Jun 11, 2025, 06:21 PM UTC
Our monitoring has identified a potential issue with one of the underlying components responsible for alert generation. Although we have not identified a direct impact at this time, for a subset of customers, there is a possibility that alerts generated might be delayed as time progresses. We will post additional updates as we continue our investigation.
- identified Jun 11, 2025, 06:52 PM UTC
We have further scoped the identified issue with one of the underlying components responsible for alert generation, and for the subset of potentially impacted customers found that any alert generation delay will be limited to those alerts designated as "Streaming" within the threat catalog. We will post additional updates as we continue our investigation.
- identified Jun 12, 2025, 12:31 PM UTC
This issue has been resolved. A fix addressing the underlying issue was implemented and streaming alert generation has returned to normal.
- resolved Jun 12, 2025, 12:32 PM UTC
This incident has been resolved.
Delayed Activity Collection and Threat alerting for Microsoft Connections
Timeline · 2 updates
- monitoring Jun 02, 2025, 01:35 PM UTC
We have identified and resolved an issue that resulted in delayed event population for Microsoft connections between 5/30/2025 4:00 pm PDT and 6/1/2025 9:30 pm PDT. As a result of the delay in event collection, customers may additionally observe a delay in threat alert triggering during the impact window for Microsoft connections.
- resolved Jun 03, 2025, 05:03 PM UTC
This incident has been resolved. All activity event processing and alerting queues have returned to normalized levels. If you encounter any further issues, please reach out to our support team.
Error encountered when accessing the settings page for the browser extension module
Timeline · 3 updates
- investigating Apr 23, 2025, 07:15 PM UTC
We are currently investigating an issue impacting the ability to successfully load the settings page for the Obsidian Browser Extension module that may result in an UI error or 50x error upon navigating to the page.
- identified Apr 23, 2025, 07:47 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Apr 23, 2025, 08:02 PM UTC
The issue has been resolved and confirmed to be working as expected. We appreciate your patience and understanding during this time. If you experience any further issues, please do not hesitate to reach out.
Delayed alerts and activity module population
Timeline · 4 updates
- investigating Jan 07, 2025, 02:35 AM UTC
We have identified an issue that may result in delayed event population within the activity module and a delay in alerts being triggered. Our teams are currently working to mitigate the issue and any updates will be posted on this incident notification.
- identified Jan 07, 2025, 04:42 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jan 07, 2025, 03:22 PM UTC
A fix has been implemented. We are monitoring the results.
- resolved Jan 07, 2025, 06:09 PM UTC
This incident has been resloved.
Increased Activity Module Load Times
Timeline · 4 updates
- investigating Oct 24, 2024, 08:38 PM UTC
We have identified an issue that may cause longer load times for the activity module in the US region. Our teams are actively working to resolve the issue, and we'll provide updates on this incident as they become available.
- identified Oct 24, 2024, 08:55 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Oct 24, 2024, 09:05 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Oct 24, 2024, 10:05 PM UTC
The issue causing increased load times for the Activity Module in the US region has been resolved. We appreciate your patience while our teams worked to address the issue. If you experience any further problems, please don't hesitate to contact our support team for assistance. Thank you for your understanding and continued support