Sumsub incident

EU Production Database Performance Incident

Minor Resolved View vendor source →
Started
Mar 02, 2026, 11:06 AM UTC
Resolved
Feb 26, 2026, 03:00 PM UTC
Duration
Detected by Pingoru
Mar 02, 2026, 11:06 AM UTC

Update timeline

  1. resolved Mar 02, 2026, 11:06 AM UTC

    Description: Between 15:00 and 18:08 UTC on February 26, 2026, one database node in our EU production cluster experienced network throttling, resulting in increased query latency. This manifested as general interface sluggishness and intermittent API response delays. Root Cause: A spike in traffic triggered AWS network throttling on the affected database instance, leading to degraded performance. Resolution: Traffic was redirected to another instance, restoring normal operation. Next Steps: We are strengthening network monitoring, reviewing instance sizing, and working with the platform team to implement additional traffic control measures to prevent recurrence.

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
Start monitoring Sumsub for free

5 free monitors · No credit card required