Obsidian Security incident
Service partially down(threat, activity) for US region
Obsidian Security experienced a critical incident on January 5, 2026 affecting Threat Management and API, lasting 11h 20m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- 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.