Cyderes incident

Service Disruption - Cyderes Portal search and Microsoft Sentinel bi-directional syncing.

Major Resolved View vendor source →

Cyderes experienced a major incident on September 10, 2025 affecting Client Portal and Ticket System Integrations, lasting 8h 23m. The incident has been resolved; the full update timeline is below.

Started
Sep 10, 2025, 11:00 AM UTC
Resolved
Sep 10, 2025, 07:23 PM UTC
Duration
8h 23m
Detected by Pingoru
Sep 10, 2025, 11:00 AM UTC

Affected components

Client PortalTicket System Integrations

Update timeline

  1. investigating Sep 10, 2025, 11:00 AM UTC

    We are currently experiencing a service outage for the Cyderes Client Portal search functionality and the ability to conduct bi-directional syncing with Microsoft Sentinel. Our engineering team is investigating the issue with the highest priority and working diligently to restore service as quickly as possible.

  2. identified Sep 10, 2025, 01:04 PM UTC

    Our team has identified the cause of the outage and remediation actions are underway.

  3. identified Sep 10, 2025, 03:46 PM UTC

    The remediation actions are in the process of testing and validation across all impacted subsystems.

  4. monitoring Sep 10, 2025, 04:41 PM UTC

    All major subsystems are now operational. We appreciate your patience during the recent service interruption. We'd also like to provide an update on two related items within the Cyderes Portal: Case View Sorting: Table sorting in the case view is currently limited to the default "Newest to Oldest" order. Our team is actively working to restore full sorting functionality. Case List Pagination: A change has been implemented for case list navigation. Instead of traditional page-to-page navigation, you will now see a "Load More" prompt at the bottom of the list. We will notify you once the case view sorting is fully restored. Thank you for your continued partnership.

  5. resolved Sep 10, 2025, 07:23 PM UTC

    We have successfully resolved the recent service outage. All systems are now operating as expected and case view sorting has been corrected. Thank you for your patience while our team worked to address this issue.