- 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
-
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.
Read the full incident report →
- 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
-
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.
Read the full incident report →
- 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
-
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.
Read the full incident report →
- Detected by Pingoru
- Mar 11, 2026, 07:51 AM UTC
- Resolved
- Mar 11, 2026, 11:47 AM UTC
- Duration
- 3h 55m
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.
Read the full incident report →
- 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
-
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.
Read the full incident report →
- Detected by Pingoru
- Feb 09, 2026, 07:23 PM UTC
- Resolved
- Feb 09, 2026, 07:00 PM UTC
- Duration
- —
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
Read the full incident report →
- 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
-
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.
Read the full incident report →
- 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
-
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.
Read the full incident report →
- Detected by Pingoru
- Nov 13, 2025, 01:14 AM UTC
- Resolved
- Nov 13, 2025, 02:56 PM UTC
- Duration
- 13h 41m
Affected: Threat Management
Timeline · 3 updates
Read the full incident report →
Critical November 6, 2025 - 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
-
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.
Read the full incident report →
- Detected by Pingoru
- Aug 28, 2025, 04:06 PM UTC
- Resolved
- Aug 28, 2025, 11:05 PM UTC
- Duration
- 6h 59m
Affected: Posture Management
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- Aug 06, 2025, 02:48 PM UTC
- Resolved
- Aug 07, 2025, 04:22 PM UTC
- Duration
- 1d 1h
Affected: Admin Portal and 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.
Read the full incident report →
- Detected by Pingoru
- Jul 17, 2025, 07:13 PM UTC
- Resolved
- Jul 18, 2025, 09:31 PM UTC
- Duration
- 1d 2h
Affected: Threat Management
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.
Read the full incident report →
- Detected by Pingoru
- Jul 15, 2025, 01:08 PM UTC
- Resolved
- Jul 15, 2025, 01:08 PM UTC
- Duration
- —
Affected: Notification
Timeline · 1 update
Read the full incident report →
- Detected by Pingoru
- Jul 08, 2025, 02:30 PM UTC
- Resolved
- Jul 08, 2025, 03:16 PM UTC
- Duration
- 45m
Affected: Connections (SaaS Applications)
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.
Read the full incident report →
- Detected by Pingoru
- Jun 23, 2025, 10:05 PM UTC
- Resolved
- Jul 01, 2025, 03:00 PM UTC
- Duration
- 7d 16h
Affected: Action Policies
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.
Read the full incident report →
- Detected by Pingoru
- Jun 11, 2025, 06:21 PM UTC
- Resolved
- Jun 12, 2025, 12:32 PM UTC
- Duration
- 18h 11m
Affected: Threat Management
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.
Read the full incident report →
- Detected by Pingoru
- Jun 02, 2025, 01:35 PM UTC
- Resolved
- Jun 03, 2025, 05:03 PM UTC
- Duration
- 1d 3h
Affected: Threat Management
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.
Read the full incident report →
