Sumsub Outage History

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.

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.

We identified and resolved an issue that caused TM creation requests to return 400 errors when the transaction included an invalid full name. This affected only a limited number of transactions where the full name value was incorrect. Transactions with valid full name data were not impacted. As the affected requests failed validation before transaction creation, no affected transactions were created in our system. Affected transactions need to be recreated by the client. This incident is being reported retrospectively for transparency. UTC time: 8:08 - 9:05

The infrastructure provider confirmed an incident and currently investigating the root cause. Ticketing functionality is restored, all previous messages can be resubmitted and processed by the support team.

This incident has been resolved.

The issue has been fixed, and access to the affected Admin Panel sections has been restored. The incident was caused by a very specific edge-case bug affecting only a limited role configuration. No broader impact has been identified.

Between 15:00 and 15:13 UTC, we experienced a brief service disruption caused by a Cloudflare DNS timeout. During this period, a small amount of requests failed with 5XX errors. The issue has been resolved, and services are operating normally. We apologize for the inconvenience and appreciate your patience.

The incident has been resolved, and service stability has been fully restored. Mitigation measures have been applied, and our teams have confirmed normal platform operation. We will continue monitoring the infrastructure, and a detailed incident review will follow internally. Thank you for your patience and understanding.

We are pleased to confirm the system was operational for the last 12 hours. The root cause has been identified and a permanent fix has been implemented. All affected support tickets were reopened and processed. Our team is available through all the usual channels to assist you. Thank you for your patience throughout this process!

Between 2026-03-26 11:07 UTC and 2026-03-26 12:50 UTC, we experienced a minor issue affecting PDF report generation. During this time, applicant PDF exports may have been incomplete. The issue has now been fully resolved. If your PDF report contains blank sections, missing pages, or looks incomplete, please generate the PDF report again. We apologize for any inconvenience caused. Please, contact our Support Team in case you have any questions!

The incident affecting incoming client messages has been resolved. All systems are now operating normally.

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.

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.

Mobile SDK users experienced an issue during the Liveness verification step, where the interface could appear unresponsive and remain in a prolonged loading state. The issue has been fully resolved, and the service is currently operating normally. Affected period: 15:22 - 15:45 UTC

Our external service provider for AML verifications experienced technical issues, which caused some verifications to take longer than usual. Affected period: 10:04 - 10:11 UTC The issue has now been resolved, and services are operating normally.

After review, no widespread or systemic issue was identified. A small number of isolated user reports indicated slower-than-usual loading times when accessing the liveness verification screen. The service remained fully available throughout the reported period. Overall system performance was stable, and the behavior appears to have been limited to individual cases rather than a broader service impact. Those reports will be investigated and fixed individually. Please contact Sumsub Support in case you have any questions!

We experienced temporary service issues caused by a Cloudflare incident. https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q Our traffic has been successfully rerouted to CloudFront, and all core services are now operating normally. Please note that our documentation (https://docs.sumsub.com), which is still hosted on Cloudflare, may experience temporary access issues.

We are happy to confirm the issue has been fully resolved. Should you have any additional questions, please, reach out to our Support team!

The issue affecting our support ticketing system has been fully resolved. The disruption was caused by a temporary outage on the side of an external provider, which has now been restored to normal service. All incoming support tickets are being received and processed as expected.

Root Cause: The issue was caused by significantly increased response times from the external provider API The system continued waiting for risk-scoring responses until reaching the maximum timeout, which led to slow queue processing and delays for handling of part of transactions. Next Steps: We will enhance our queue-management logic to better handle scenarios where third-party providers are involved in the scoring process.

Cloudflare has resolved the incident. We can confirm that our services remained fully operational and were not affected at any time. If you experience any issues or have any questions, please don't hesitate to contact our support team via chat or [email protected].

We can confirm that the technical issues with Video Verifications have been fully resolved. All systems are operating normally, and we have observed stable performance following the AWS recovery. Users have experienced issues with Video Verifications between 07:27 and 12:02 UTC. The service is now fully stable and operating as expected.

Following Cloudflare’s confirmation that the incident has been resolved, our team has observed no further issues and can confirm that services are stable. We remain at your disposal for any additional questions, which you can address to our Support team. More details about the incident can be found at Cloudflare's status page: https://www.cloudflarestatus.com/incidents/ffwzxb94kxk9