Obsidian Security Outage History

Started Oct 01, 2026, 01:56 AM UTC· resolved Oct 01, 2026, 03:24 AM UTC

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 →

Started Aug 14, 2026, 08:09 PM UTC· resolved Aug 14, 2026, 08:09 PM UTC

1. resolved Aug 14, 2026, 08:09 PM UTC

   Security Advisory: CloudSEK Disclosure — TeamPCP / Trivy Supply Chain Campaign Published: August 14, 2026 Status: Resolved - no customer impact Customer action required: None Summary Obsidian Security is aware of the CloudSEK disclosure regarding the TeamPCP supply chain campaign, which targeted CI/CD pipelines and AI infrastructure beginning in March 2026 and named 2,500+ affected companies. Obsidian is listed among them. The data published by CloudSEK corresponds to the original Trivy-based campaign that affected our CI/CD systems in mid-March 2026, an incident we detected at the time, fully investigated, and remediated. No customer data was exposed at any time. A limited set of Obsidian internal secrets and CI/CD configurations were exposed. The secrets were all unusable in the hands of a third party owing to our defense-in-depth protections and swift incident response. All were revoked and rotated in March 2026, and we confirmed none were used to make any unauthorized access. What Happened Mid-March 2026 — Original incident - Our CI/CD systems were impacted by the Trivy supply chain campaign. - Some internal secrets and CI/CD configuration were potentially exposed. - We detected the activity immediately and initiated an incident response. Our findings: - No customer data or customer secrets were affected. - Any exfiltrated secrets were unusable on their own due to our defense-in-depth posture. - No unauthorized access occurred. Remediation completed at the time: - Revoked and rotated all secrets used in the CI/CD pipeline. - Hardened how our CI/CD pipeline pulls in open-source dependencies and implemented restrictions. August 2026 — CloudSEK publication CloudSEK obtained and published data from the Trivy campaign, listing 2,500+ impacted companies including Obsidian. Our response: - Engaged directly with CloudSEK and obtained the full incident report, including raw log files. - Confirmed the published data originates entirely from the mid-March 2026 incident, with no new or additional exposure. - Reconfirmed that every internal secret appearing in the report had already been rotated in March 2026. - Verified that none of the exposed secrets were used in any access attempt. Any such attempt would have failed given our layered controls. - Re-evaluating our disclosure criteria. Why We Did Not Disclose Earlier Obsidian is continuously targeted, as are all security vendors. We assessed the March 2026 incident against our disclosure criteria and determined that no customer sensitive information was exfiltrated and no customer environment was affected. The incident was contained, remediated, and closed. We are publishing now because the CloudSEK report has brought the underlying data into public view, and we want customers to have an accurate account of what it does and does not represent. We are re-evaluating our disclosure criteria, and going forward anticipate releasing more information about attacks that exfiltrate data, even if we do not consider the data to be sensitive. Current Status We have found no new evidence of unauthorized access and have had no incidents reported. We continue to monitor and will provide updates if our assessment changes. Contact Customers with questions are welcome to reach out to their Obsidian account team or our support team directly at [email protected]. We are happy to schedule a call to walk through the details of this advisory.

Read the full incident report →

Started Jun 12, 2026, 04:31 PM UTC· resolved Jun 13, 2026, 01:08 AM UTC

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 →

Started Jun 09, 2026, 02:38 PM UTC· resolved Jun 09, 2026, 03:29 PM UTC

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 →

Started May 27, 2026, 12:40 PM UTC· resolved May 27, 2026, 02:25 PM UTC

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 →

Started May 15, 2026, 03:10 PM UTC· resolved May 15, 2026, 09:03 PM UTC

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 →

Started May 15, 2026, 02:05 PM UTC· resolved May 15, 2026, 02:47 PM UTC

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 →

Started Mar 11, 2026, 02:05 PM UTC· resolved Mar 11, 2026, 02:34 PM UTC

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 →

Started Mar 11, 2026, 07:51 AM UTC· resolved Mar 11, 2026, 11:47 AM UTC

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 →

Started Feb 09, 2026, 09:06 PM UTC· resolved Feb 09, 2026, 10:50 PM UTC

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 →

Started Feb 09, 2026, 07:00 PM UTC· resolved Feb 09, 2026, 07:00 PM UTC

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 →

Started Jan 05, 2026, 01:44 AM UTC· resolved Jan 05, 2026, 01:04 PM UTC

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 →

Started Dec 05, 2025, 09:07 AM UTC· resolved Dec 05, 2025, 09:22 AM UTC

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 →

Started Nov 12, 2025, 07:12 PM UTC· resolved Nov 13, 2025, 02:56 PM UTC

1. investigating Nov 12, 2025, 07:12 PM UTC

   We are currently investigating reports from a subset of customers reporting page unresponsive messages for a subset of webpages under Google Chrome and Microsoft edge when running version 1.13.x of the Obsidian browser extension. Additional updates will be posted on this incident notification as our investigation into the root cause of this issue progresses

2. identified Nov 13, 2025, 01:14 AM UTC

   A root cause has been identified for the issue impacting the Obsidian Browser extension that is resulting in a subset of customers experiencing browser performance degradation when the Obsidian Browser Extension analyzes certain pages for Phishing Detections. Scope and impact Issue onset has been observed with ver. 1.13.x and up Other Browser Extension capabilities remain unaffected. Temporary mitigation (workaround) Administrators can temporarily disable the Phishing Detections component to prevent the behavior while a permanent fix is prepared. How to apply the workaround Sign in to the Obsidian admin console, then open Browser Extension settings. Locate Phishing Detections and set the Phishing Status to “Disabled.” Save changes, wait a few minutes for propagation, then refresh affected browsers. Next steps A new extension version with a permanent fix is being prepared and will roll out via auto‑upgrade. After the fixed version is deployed in your environment, re‑enable Phishing Detections to restore full protection. Support For assistance determining whether to apply this mitigation, contact Obsidian Support at [email protected] or your Technical Account Manager.

3. resolved Nov 13, 2025, 02:56 PM UTC

   This incident has been resolved. We have released a permanent fix in the Obsidian Browser Extension version ver. 1.13.4, which is now rolling out via auto‑update. What to expect: The updated extension will install automatically as it propagates to users. Next steps: If you previously disabled Phishing Detections as a workaround, you may re‑enable it once your environment has received version 1.13.4. Scope: No other Browser Extension capabilities were affected. Support: For help confirming rollout status or re‑enabling Phishing Detections, contact Obsidian Support at [email protected] or your Technical Account Manager. Thank you for your patience while we worked to resolve this issue.

Read the full incident report →

Started Nov 06, 2025, 07:03 PM UTC· resolved Nov 06, 2025, 07:39 PM UTC

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 →

Started Aug 28, 2025, 04:06 PM UTC· resolved Aug 28, 2025, 11:05 PM UTC

1. identified Aug 28, 2025, 04:06 PM UTC

   We have identified an issue impacting a subset of Salesforce posture rules. Impacted customers may find that the rule IDs 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. Environments Impacted: US, EU, AU SalesforceInactivePrivilegedAccounts SalesforceSystemAdmins SalesforcePrivilegedUsersFromLowReputationDomains SalesforceGhostAdmins SalesforceUsersWithCreatePublicLinks SalesforceWeakerProfilePasswordSettings SalesforceExternalUserObjectAccess SalesforceUsersWaivedMFA SalesforceGuestUserObjectAccess SalesforceUsersNoMFA SalesforceIntegrationUsersWithSysAdminProfile SalesforceRiskyGuestUsers SalesforceFieldLevelAccessForEncryptedData SalesforceWeakerProfileSessionSettings SalesforceFieldLevelAccessForComplianceData SalesforceAppsExcessivePermissions Additional updates will be provided via this posting as our investigation progresses and the issue is mitigated.

2. resolved Aug 28, 2025, 11:05 PM UTC

   The issue has been resolved and impacted Salesforce posture rules now reflect the correct status. We appreciate your patience and understanding during this time, and if you experience any further issues, please do not hesitate to reach out.

Read the full incident report →

Started Aug 06, 2025, 02:48 PM UTC· resolved Aug 07, 2025, 04:22 PM UTC

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

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

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

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

Started Jul 17, 2025, 07:13 PM UTC· resolved Jul 18, 2025, 09:31 PM UTC

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

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

Started Jul 15, 2025, 01:08 PM UTC· resolved Jul 15, 2025, 01:08 PM UTC

1. resolved Jul 15, 2025, 01:08 PM UTC

   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 August 14th, 2025. These updates have been carefully considered to enhance the security and efficiency of our services. We are adding the following data sub-processor: Vendor Name - Catalyst Data Processing Location - United States Data Processed - Customer contact information, metadata, usage and activity data related to your use of our services Please contact [email protected] on or before August 14th, 2025 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

Read the full incident report →

Started Jul 08, 2025, 02:30 PM UTC· resolved Jul 08, 2025, 03:16 PM UTC

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

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

Started Jun 23, 2025, 10:05 PM UTC· resolved Jul 01, 2025, 03:00 PM UTC

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

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

3. resolved Jul 01, 2025, 03:00 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 11, 2025, 06:21 PM UTC· resolved Jun 12, 2025, 12:32 PM UTC

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

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

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

4. resolved Jun 12, 2025, 12:32 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 02, 2025, 01:35 PM UTC· resolved Jun 03, 2025, 05:03 PM UTC

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

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

Started Apr 23, 2025, 07:15 PM UTC· resolved Apr 23, 2025, 08:02 PM UTC

1. investigating Apr 23, 2025, 07:15 PM UTC

   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.

2. identified Apr 23, 2025, 07:47 PM UTC

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

3. resolved Apr 23, 2025, 08:02 PM UTC

   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.

Read the full incident report →

Started Jan 07, 2025, 02:35 AM UTC· resolved Jan 07, 2025, 06:09 PM UTC

1. investigating Jan 07, 2025, 02:35 AM UTC

   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.

2. identified Jan 07, 2025, 04:42 AM UTC

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

3. monitoring Jan 07, 2025, 03:22 PM UTC

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

4. resolved Jan 07, 2025, 06:09 PM UTC

   This incident has been resloved.

Read the full incident report →