SafetyChain incident

Status Update: Non-Compliant Notifications Issue

Major Resolved View vendor source →

SafetyChain experienced a major incident on February 11, 2025 affecting Notifications, lasting 33m. The incident has been resolved; the full update timeline is below.

Started
Feb 11, 2025, 03:29 PM UTC
Resolved
Feb 11, 2025, 04:03 PM UTC
Duration
33m
Detected by Pingoru
Feb 11, 2025, 03:29 PM UTC

Affected components

Notifications

Update timeline

  1. identified Feb 11, 2025, 03:29 PM UTC

    We are currently experiencing an issue where Non-Compliant Notifications are not being sent. Our team is actively working to restore this service as soon as possible. In the meantime, please use the Exceptions Report in LINK or other Record-based Reports to monitor non-compliant records.

  2. monitoring Feb 11, 2025, 03:34 PM UTC

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

  3. resolved Feb 11, 2025, 04:03 PM UTC

    Non-compliant notifications are now sending as expected. This is effective as of 7:26 AM PT. For records submitted between 11:30 PM and 7:26 AM PT, please use the Exceptions Report in LINK or other Record-based Reports to monitor non-compliant records