Sumsub logo and current status indicator

Sumsub Incident History

Sumsub is currently operational with all systems functioning normally.

Last checked Jul 28, 2026 8:44 AM UTC from Sumsub's official status page

Incident History

Showing incidents from the last 15 days

Report: "Performance Degradation: AML Screening"

Last update
resolved

The intermittent issue has been fully resolved. Systems have been operating without issue for over 30 minutes. All applicants affected during the brief degradation window were automatically re-screened and processed successfully. All AML screening services are now functioning normally.

monitoring

Errors are occurring sporadically, and overall error counts remain low; most applicant screenings are processing normally. Applicants affected during this window are being automatically re-screened by our system to ensure processing is completed.

monitoring

We are continuing to monitor for any further issues.

monitoring

We are currently monitoring intermittent issues with our AML screening provider, ComplyAdvantage. Customers utilizing the default ComplyAdvantage CSOM service may experience delays or errors with AML Screening, which could temporarily increase overall applicant verification times. The service has experienced brief spikes in errors since 14:52 UTC, followed by temporary recovery. While the system is currently functioning normally, we are actively monitoring the situation closely and will provide updates as needed.

Report: "SDK Initialization Failures"

Last update
resolved

Between 07:02 and 07:15 UTC, some users may have encountered a 403 Forbidden error when initializing the SDK, which prevented applicant verification requests from being processed. The root cause of the issue is related to developed feature misconfiguration that caused the feature to be applied more broadly than intended. Our monitoring systems detected the unexpected behavior, and the change was disabled within several minutes We identified the underlying issue and implemented a fix. The issue has been fully resolved. This incident is being reported retrospectively for transparency.