Insurity incident

Notification: Issue identified with Outlook Online email service

Minor Resolved View vendor source →

Insurity experienced a minor incident on January 22, 2026 affecting Insurity Public Cloud - Canada and Insurity Public Cloud - Canada and 1 more component, lasting 3d 16h. The incident has been resolved; the full update timeline is below.

Started
Jan 22, 2026, 08:57 PM UTC
Resolved
Jan 26, 2026, 01:50 PM UTC
Duration
3d 16h
Detected by Pingoru
Jan 22, 2026, 08:57 PM UTC

Affected components

Insurity Public Cloud - CanadaInsurity Public Cloud - CanadaInsurity Public Cloud - US - NewInsurity Public Cloud - US - OldInsurity Private Cloud - Canada (Non Production)Insurity Public Cloud - CanadaInsurity Public Cloud - US

Update timeline

  1. identified Jan 22, 2026, 08:57 PM UTC

    The following is an important message from Insurity Customer Support. We are aware that some outbound emails from our systems, including multi-factor authentication (MFA) messages, are currently not being delivered due to a widespread issue affecting Microsoft’s Outlook Online email service. Our team is actively monitoring the situation and working closely with Microsoft’s service updates to restore normal email delivery as quickly as possible. We are sorry for the inconvenience this may cause you and thank you for your cooperation. Please do not hesitate to contact Customer Support through our support portal if you have any questions.

  2. monitoring Jan 23, 2026, 03:05 AM UTC

    The following is an important message from Insurity Customer Support. As of 10:00 PM EST, Insurity Cloud Operations is seeing recovery in email delivery from our systems, including MFA messages, following a widespread issue affecting Microsoft’s Outlook Online email service. We are continuing to monitor the situation and will take further mitigation steps where required. We are sorry for the inconvenience this may cause you and thank you for your cooperation. Please do not hesitate to contact Customer Support through our support portal if you have any questions.

  3. resolved Jan 26, 2026, 01:50 PM UTC

    This incident has been resolved.