Sumsub incident

Temporary Aggregation Inaccuracy in Transaction Monitoring Rules

Minor Resolved View vendor source →

Sumsub experienced a minor incident on February 24, 2026, lasting —. The incident has been resolved; the full update timeline is below.

Started
Feb 24, 2026, 02:30 PM UTC
Resolved
Feb 20, 2026, 12:00 PM UTC
Duration
—
Detected by Pingoru
Feb 24, 2026, 02:30 PM UTC

Update timeline

  1. resolved Feb 24, 2026, 02:30 PM UTC

    Between 20.02 (12:00 UTC) and 23.02 (18:00 UTC), during a scheduled aggregation tables migration, a configuration inconsistency caused partial data to not be fully reflected in the production aggregation layer. This affected certain rules relying on aggregate expressions for a limited period. Core monitoring and transaction processing were not impacted, and no data loss occurred. The issue has been resolved and aggregation data fully reconciled. Additional validation and automation controls have been implemented to prevent recurrence. As a precaution, we will automatically rescore all transactions evaluated by aggregate-based rules during the affected period. If you have any questions or require assistance, please contact our Support team.