Is Obsidian Security Down Right Now? Check if there is a current outage ongoing.

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.

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.

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.

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.

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.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We will be undergoing scheduled maintenance during this time.

We will be undergoing scheduled maintenance during this time.

We will be undergoing scheduled maintenance during this time.

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.

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

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.

This incident has been resloved.

A fix has been implemented. We are monitoring the results.

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

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.

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.

Mitigation actions have been taken to address the underlying issue resulting in delayed alerting and activity module population. Backlogged activity data are being processed successfully, and Obsidian's operations team will continue to actively monitor processing queues. Further updates will be posted to this incident notification once queue depths have returned to normal levels.

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.

The system continues to be stable and perform as expected. This incident is now being marked as resolved. Please contact Obsidian support in case you have any questions.

We have identified the cause of the underlying issue and implemented a fix. Services have been recovered and are now performing as expected. Some alerts generated will still have a delay prior to this point. Please contact Obsidian support in case you see any anomalies in your environment.

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, there is a possibility that alerts generated might be delayed as time progresses. We will post additional updates as we continue our investigation.

This is a System Notice. All Obsidian systems remain operational at this point in time and there is no impact. Obsidian periodically reviews and updates its data sub-processor list to ensure that we work with trusted partners who share our commitment to data security and privacy. These sub-processors play a crucial role in providing our services to you, and we take their selection very seriously. We are pleased to inform you that we have made some updates to our data sub-processor list, which will come into effect on November 15, 2024. These updates have been carefully considered to enhance the security and efficiency of our services. A list of the sub-processors we will be adding is provided below: Google - Google Cloud Platform and Looker provide compute, storage, networking, and analytic services for various product infrastructure services and business intelligence purposes. Please contact security@obsidiansecurity.com on or before November 15th, 2024 for raising any objections to this change. Please note that if we do not receive any objections within the specified period, we will consider your consent to the updated data sub-processor list as implied. If you have any questions or require additional information about the changes to our data sub-processor list, please do not hesitate to contact us on the same email address above. Thank you for your continued trust and partnership with Obsidian Security. We remain dedicated to safeguarding your data and providing you with the highest level of service.

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

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

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

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.

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.

A fix to address delays with event population and alerting has been deployed, and backlogged events are being processed successfully at this time. Obsidian's operations team will continue to actively monitor processing queues, and further updates will be posted to this incident notification once queues have been fully processed.

We have identified the offending component and are continuing to work towards development of a fix to address the underlying issue. Further updates will be posted on this incident notification as we progress towards full resolution.

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.

All tenants have been successfully updated with the latest Activity Data. Our teams will continue to monitor the system closely. Should you have any further questions or require assistance, please feel free to reach out to our support teams.

Good news! 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. An update will be sent once the activity data is fully up to date across all tenants. Thank you for your patience.

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

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

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.

Our teams have successfully mitigated the problem, and is now functioning at optimal performance. Thank you for your patience and understanding while we worked to address this matter. Your continued support and cooperation during this process are greatly appreciated.

We have identified an issue that may result in increased load times for the activity module. Our teams are currently working to mitigate the issue and any updates will be posted on this incident notification.

All tenants are now fully up to date with the latest Activity Data. Our teams will continue to monitor this from our side, however, this incident is now being marked as resolved. Please reach out to our support teams in case you have any questions.

We have made significant progress in reducing the activity data backlog. The delay now affects only a small number of tenants, and they are recovering at a steady pace. We expect full recovery within the next 6-8 hours. An update will be sent once the activity data is fully up to date across all tenants. If you have any questions, please feel free to contact our support team.

Good news! 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. Thank you for your patience.

We are continuing to monitor this issue on our side. There are still a few tenants where the activity data is not latest and is recovering swiftly.

We are continuing to monitor this issue on our side. There are still a few tenants where the activity data is not latest and is recovering swiftly.

We have detected a delay in fetching Activity Data for a subset of customers. Impact: Activity Data: Some customers may experience delays of several hours before their activity data is fully updated. Alert Processing: A limited number of alerts may also be delayed during this time. Current Status: Our teams are actively working to optimize processes and clear the data backlog. Next Steps: We expect this issue to be resolved within a few hours. Please open a support ticket via the normal channels if you require more information or assistance.

The issue has been resolved, and users should now be able to log in successfully.

We have identified the issue and are working on a fix.

We are currently experiencing issues with the login process for users with Multi-Factor Authentication (MFA) enabled iUsers may encounter failures when attempting to log in with their username and password due to invalid MFA. Please note that Single Sign-On (SSO) functionality is working as expected.

The incident has been resolved. Thank you for your cooperation. If you experience any further issues, please don't hesitate to reach out to our support team

The root cause has been identified, and a fix is currently under review.

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

We are currently investigating an issue impacting a subset of Okta posture rules. Impacted customers may find that the rules noted below will have unexpectedly moved from a failing to passing state. In the course of addressing the underlying cause, and rules being reverted to their proper state, posture drift alerts may be received. #Global session policies with long max session lifetime #Global session policies without MFA required #Policies in Okta with zero assigned rules #Global session policies with long session timeout #Users only covered by the default global session sign-on rule # Sign-on policies with MFA required on new devices only

This incident has been resolved, and all affected services have been restored. All services are now fully operational. If you encounter any further issues, please reach out to our support team.

We are currently investigating an issue impacting the Obsidian activity stream and custom alerts. Customers may experience a pause in activity and a delay in custom alerts during this period.

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.

We are currently investigating an issue with our Admin portal authentication service which might prevent users from successfully authenticating to the Obsidian platform. When navigating to the login prompt, the option to use SSO for authentication might not appear. Our teams are currently investigating the issue and any updates will be posted on this incident notification.

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.

The fix has been deployed and is currently under monitoring. We are closely observing the system to ensure the issue is fully resolved. Further updates will be provided as needed.

We are currently investigating an issue impacting interaction with the Obsidian posture module that may result in an UI error or 50x error being received when making changes or updates within the module.

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.

The fix has been deployed and is currently under monitoring. We are closely observing the system to ensure the issue is fully resolved. Further updates will be provided as needed.

Update 1: The engineering team has identified the root cause of the issue . They are actively working on a resolution. We apologize for any inconvenience caused and appreciate your patience. Further updates will be provided as soon as more information is available.

Our systems have detected an issue impacting Microsoft posture settings that may result in "No Data" being displayed for a subset of settings. Our engineering team is currently working to address the underlying issue. Additional status updates will be posted at 9:30am PDT

All tenants are now fully up to date with the latest Activity Data as of 6 hours ago. Our teams will continue to monitor this from our side, however, this incident is now being marked as resolved. Please reach out to our support teams in case you have any questions.

We have made significant progress in reducing the backlog overnight and the delay remains only in a small number of tenants which are recovering at a good pace. We expect the delay to be fully recovered in the next 6-8 hours. We will send an update once the activity data is latest across all tenants. Please contact our support team in case of any questions.

Our teams have put measures in place to normalize the infrastructure responsible for processing activity data. We will be monitoring overnight and expect to make significant progress to reduce the overall delay and backlog. We will share next updates on the overall progress of recovery in the PST morning hours. Please contact our support team in case you have any questions.

We are aware of a few instances in which some tenants are still seeing delays with Activity data not being the latest. During our efforts to clear the delay in processing the events, we encountered an infrastructure issue which has caused the recovery process to not scale to our expectations. Our teams are continuing to work on optimizing the recovery process to clear the backlog. Next update with more concrete timelines on full recovery will be shared in next 3 hours. Please contact our support team in case you have any questions.

We are continuing to monitor this issue on our side. There are still a few tenants where the activity data is not latest and is recovering swiftly. We expect the data to be fully latest by end of today PST. Please contact our support team for any further information that you may require.

Our systems detected a delay in fetching activity information for connections to Salesforce. Our engineering teams have since identified and resolved the underlying issue and are currently monitoring. Due to the nature of the fix deployed, it might take a few hours for the data under the 'Activity' section to become latest on our systems for a few tenants. This might also result in some delay in regards to processing of a limited set of Alerts. Please open a support ticket via the normal channels in case more information is required and we would be happy to assist you.

There were issues with the WebUI and API endpoints in the Europe region that could have impacted users' authentication to the Obsidian platform. Our team has fixed the issues and is currently monitoring the services. If you are still experiencing any problems, please submit a support ticket, and we will gladly help you investigate them.

This incident has been resolved.

Our monitoring recently discovered an issue with our Admin portal authentication service which might have prevented users from successfully authenticating to the Obsidian platform. Our team has restored the services and are now monitoring. If you are still experiencing any symptoms, please open a support ticket and we will assist in investigating the same.

We discovered an issue with our Okta data retrieval that might have introduced a delay of up to 48 hours starting approximately from Jan-19-2024 5.30 PM US Pacific time for the relevant activity data from being shown on your Obsidian UI and related alerts from being triggered during that period. Our engineering teams have since identified the issue and have restored the service. If you are still encountering the symptoms reported above or have any questions, please open a support ticket and we will assist with the same.

We would like to inform you that the scheduled maintenance, which we previously communicated, has been postponed. The maintenance activity was initially planned for January 20, 2024, at 9:00 PM PST in the US region. After careful consideration, we have made the decision to reschedule the maintenance to ensure minimal disruption to your operations. Our team is actively working to optimize the timing of this maintenance to better align with your needs and minimize any potential impact on your business operations. We understand how important our services are to your workflow, and this decision reflects our dedication to delivering reliable and uninterrupted support. We appreciate your understanding and flexibility in this matter. Rest assured that we will keep you informed about the revised schedule as soon as it is finalized. If you have any questions or concerns, please feel free to reach out to our support team. Please note that this is just a system notification relayed via our Status page. No Obsidian systems are currently affected.

At Obsidian Security, we are committed to maintaining the highest standards of data security and privacy for our customers. As part of our ongoing efforts to ensure the protection of your data, we are writing to inform you about some important changes to our data sub-processor list. We are pleased to inform you that we have made some updates to our data sub-processor list, which will come into effect on February 9, 2024. These updates have been carefully considered to enhance the security and efficiency of our services. A list of the sub-processors we will be adding is provided below: 1. Anthropic - Supporting data analysis and contextualization. 2. Zendesk - Providing Customer support services. We understand the importance of transparency and value your trust in our organization. Therefore, we want to give you the opportunity to review and, if necessary, raise any concerns or objections regarding these updates. If you have any concerns with these additions, please contact our Privacy team via email at security@obsidiansecurity.com within the next 14 business days from the date of this notification. Your feedback is essential to us, and we will make every effort to address any valid concerns you may have. Please note that if we do not receive any objections within the specified 14-day period, we will consider your consent to the updated data sub-processor list as implied. Please note that this is just a system notification relayed via our Status page - no Obsidian systems are currently affected.

Monitoring has indicated no further occurrences and as a result, this issue is being marked as resolved.

We discovered an issue with our Action Policies that utilize Webhooks as a delivery mechanism to not have triggered properly in some instances between 02:00 UTC 12/09/2023 to 18:30 UTC 12/11/2023 . Our engineering teams have since identified the issue and have restored the service. If you are still encountering any delivery issues where Webhooks have been defined as the delivery mechanism, please open a support ticket and we will assist in investigating the same.

In response to the recent new information shared by Okta on their incident involving compromise of their Customer Support system (https://sec.okta.com/harfiles), Obsidian has published an updated guidance on detection, remediation as well as associated best practices for your environment in its documentation which is available here (please login into your Obsidian Console before clicking the link): https://docs.obsidiansecurity.com/obsidian/publicly-disclosed-security-incidents/okta-scattered-spider-social-engieering Please note that this is just a security advisory notification. Obsidian Security systems or operations were not impacted by this incident.

The issue has been resolved and services are back to normal

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

We are currently investigating a potential issue affecting the authentication to the Obsidian Administration UI. Our engineering team is actively working on restoring the service.