Insurity incident

Notification: Insurity Marine Suite Cognos Overnight Jobs Not Up to Date

Minor Resolved View vendor source →

Insurity experienced a minor incident on December 12, 2025 affecting Insurity Public Cloud - Canada, lasting 6d. The incident has been resolved; the full update timeline is below.

Started
Dec 12, 2025, 05:15 PM UTC
Resolved
Dec 18, 2025, 05:32 PM UTC
Duration
6d
Detected by Pingoru
Dec 12, 2025, 05:15 PM UTC

Affected components

Insurity Public Cloud - Canada

Update timeline

  1. identified Dec 12, 2025, 05:15 PM UTC

    Update: Our teams have continued to actively work on the Cognos reporting issue. As planned, the data refresh has been completed and all reporting data is now up to date. Additionally, please be advised that we will be performing maintenance on the Cognos server this evening starting at 9:00 PM EST, with an estimated duration of approximately 90 minutes. This maintenance is intended to stabilize the environment. Thank you for your understanding and continued patience. ____________________________________________________________________________________________________________________________________________ We have identified an issue affecting the Insurity Marine Suite Cognos overnight jobs. As a result, Cognos reports are not up to date. Our teams are actively investigating the issue in collaboration with Microsoft to determine the underlying cause. In parallel, we have initiated a refresh of the reporting environment to restore the latest available data. We will continue to provide updates as more information becomes available or once the reports are fully restored. Thank you for your patience and understanding as we work to resolve this incident.

  2. identified Dec 12, 2025, 09:02 PM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring Dec 16, 2025, 01:48 PM UTC

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

  4. monitoring Dec 16, 2025, 01:48 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Dec 18, 2025, 05:32 PM UTC

    This incident has been resolved.