Sumsub incident
Temporary Aggregation Inaccuracy in Transaction Monitoring Rules
Update timeline
- 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.
Looking to track Sumsub downtime and outages?
Pingoru polls Sumsub's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Sumsub reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Sumsub alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required