Obsidian Security Outage History

Obsidian Security is up right now

Obsidian Security had 15 outages in the last 2 years totaling 51h 19m of downtime — averaging 0.6 incidents per month.

There were 15 Obsidian Security outages since November 6, 2025 totaling 51h 19m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.obsidiansecurity.com

Major October 1, 2026

Delayed Activity Data in Live US Environment

Detected by Pingoru
Oct 01, 2026, 01:56 AM UTC
Resolved
Oct 01, 2026, 03:24 AM UTC
Duration
1h 27m
Affected: Posture ManagementThreat ManagementIntegration ManagementExtendSecurity Advisory
Timeline · 3 updates
  1. identified Oct 01, 2026, 01:56 AM UTC

    We have identified the cause of the issue affecting activity data in the live US environment. The affected services have stabilized, and our systems are steadily working through the backlog. Recovery is progressing, but not yet complete. Activity data for the live environment is still delayed while this clears. Once processing resumes, we expect the delayed data to catch up automatically. No data loss is expected, as delayed events are being retried and will be processed. We will post another update once activity processing has returned to normal.

  2. monitoring Oct 01, 2026, 02:55 AM UTC

    Our systems has recovered. Processing of activity data for the live environment has resumed, and the backlog of delayed activity is now being worked through.

  3. resolved Oct 01, 2026, 03:24 AM UTC

    Processing has returned to normal, and the backlog of delayed activity has been fully cleared. All activity data is now up to date.

Read the full incident report →

Minor June 12, 2026

[US Region] - Delayed Identity-Centric Alerts

Detected by Pingoru
Jun 12, 2026, 04:31 PM UTC
Resolved
Jun 13, 2026, 01:08 AM UTC
Duration
8h 37m
Affected: Threat Management
Timeline · 2 updates
  1. 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.

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

Read the full incident report →

Minor June 9, 2026

[US Region] - Subset of Alerts Delayed

Detected by Pingoru
Jun 09, 2026, 02:38 PM UTC
Resolved
Jun 09, 2026, 03:29 PM UTC
Duration
51m
Affected: Threat Management
Timeline · 2 updates
  1. 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.

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

Read the full incident report →

Minor May 27, 2026

[US Region] - Subset of threat detections delayed

Detected by Pingoru
May 27, 2026, 12:40 PM UTC
Resolved
May 27, 2026, 02:25 PM UTC
Duration
1h 45m
Affected: Threat Management
Timeline · 4 updates
  1. 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.

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

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

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

Read the full incident report →

Minor May 15, 2026

Subset of Detections Delayed

Detected by Pingoru
May 15, 2026, 03:10 PM UTC
Resolved
May 15, 2026, 09:03 PM UTC
Duration
5h 53m
Affected: Threat Management
Timeline · 4 updates
  1. 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.

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

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

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

Read the full incident report →

Minor May 15, 2026

Subset of detections delayed

Detected by Pingoru
May 15, 2026, 02:05 PM UTC
Resolved
May 15, 2026, 02:47 PM UTC
Duration
41m
Affected: Threat Management
Timeline · 2 updates
  1. 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

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

Read the full incident report →

Critical March 11, 2026

Not Found ( HTTP-404) Errors when attempting to access Obsidian Environment

Detected by Pingoru
Mar 11, 2026, 02:05 PM UTC
Resolved
Mar 11, 2026, 02:34 PM UTC
Duration
29m
Affected: Admin Portal and UIPosture ManagementAdmin Authentication & SSOThreat ManagementConnections (SaaS Applications)Integration ManagementAction PoliciesExtendReportingWorkflow IntegrationsSecurity AdvisoryAPINotification
Timeline · 3 updates
  1. 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.

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

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

Read the full incident report →

Notice March 11, 2026

Activity timeline delay

Detected by Pingoru
Mar 11, 2026, 07:51 AM UTC
Resolved
Mar 11, 2026, 11:47 AM UTC
Duration
3h 55m
Timeline · 5 updates
  1. 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.

  2. investigating Mar 11, 2026, 08:57 AM UTC

    The issue has been identified and a fix is being implemented.

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

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

  5. resolved Mar 11, 2026, 11:47 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 9, 2026

Intermittent failures when loading Obsidian admin console

Detected by Pingoru
Feb 09, 2026, 09:06 PM UTC
Resolved
Feb 09, 2026, 10:50 PM UTC
Duration
1h 44m
Affected: Admin Portal and UIPosture ManagementAdmin Authentication & SSOThreat ManagementConnections (SaaS Applications)Integration ManagementAction PoliciesExtendReportingWorkflow IntegrationsSecurity AdvisoryNotification
Timeline · 4 updates
  1. 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.

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

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

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

Read the full incident report →

Minor February 9, 2026

Web UI slowness for US region

Detected by Pingoru
Feb 09, 2026, 07:00 PM UTC
Resolved
Feb 09, 2026, 07:00 PM UTC
Duration
—
Timeline · 1 update
  1. 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

Read the full incident report →

Critical January 5, 2026

Service partially down(threat, activity) for US region

Detected by Pingoru
Jan 05, 2026, 01:44 AM UTC
Resolved
Jan 05, 2026, 01:04 PM UTC
Duration
11h 20m
Affected: Threat ManagementAPI
Timeline · 7 updates
  1. 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.

  2. investigating Jan 05, 2026, 01:46 AM UTC

    We are continuing to investigate this issue.

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

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

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

  6. monitoring Jan 05, 2026, 06:35 AM UTC

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

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

Read the full incident report →

Major December 5, 2025

Obsidian Administration UI Access - Cloudflare Outage

Detected by Pingoru
Dec 05, 2025, 09:07 AM UTC
Resolved
Dec 05, 2025, 09:22 AM UTC
Duration
15m
Affected: Admin Portal and UIAdmin Authentication & SSOConnections (SaaS Applications)
Timeline · 2 updates
  1. 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.

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

Read the full incident report →

Critical November 6, 2025

Errors when authenticating to the Obsidian admin portal

Detected by Pingoru
Nov 06, 2025, 07:03 PM UTC
Resolved
Nov 06, 2025, 07:39 PM UTC
Duration
36m
Affected: Admin Portal and UIAdmin Authentication & SSO
Timeline · 4 updates
  1. 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.

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

  3. identified Nov 06, 2025, 07:35 PM UTC

    The issue has been identified and a fix is being implemented.

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

Read the full incident report →