Obsidian Security Status
Real-time updates of Obsidian Security issues and outages
Obsidian Security status is Operational
Obsidian Security Threat Management
You're checking on Obsidian Security - but is your own site converting?
Outages aren't the only thing that costs you visitors.
Get a visual audit that shows exactly where your site loses conversions.
Free, takes 2 minutes.
Active Incidents
No active incidents
Recently Resolved Incidents
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.
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.
Obsidian Security Outage Survival Guide
Obsidian Security Components
Obsidian Security Platform Services
Admin Portal and UI
Admin Authentication & SSO
Connections (SaaS Applications)
Action Policies
Reporting
Workflow Integrations
API
Obsidian Security Posture Management
Obsidian Security Threat Management
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.
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.