Sumsub Outage History
29 incidents recorded over the last 365 days, 28 of them resolved, 1 still open. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Sumsub Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 29, 2026 | Degraded performance of International TIN ValidationInternational TIN Validation is fully operational again. From 15:00 UTC on October 28 to 09:40 UTC on October 29, an issue with our upstream data service caused most checks to fail. Checks have been stable since… | 5h 5m | Resolved |
| Oct 12, 2026 | Applicants incorrectly rejected due to face matching issueDescription: On October 12, 2026, between 08:28 and 08:45 UTC, a technical issue on our side affected face matching. During this time, applicants whose verification included a face match check were asked to resubmit… | 30 min | Resolved |
| Oct 2, 2026 | Connectivity issues for some users in VietnamWe are continuing to work on a permanent solution and will keep you posted. Our team is developing a technical solution and remains in direct contact with the affected telecom providers. Clients whose applicants are… | — | Investigating |
| Sep 15, 2026 | Dashboard applicant search impairedBetween 13:23 and 15:13 UTC, we experienced a temporary issue affecting applicant search functionality. As a result, some applicant search requests in the Dashboard and CSV exports may have been unavailable or returned… | -1363 min | Resolved |
| Aug 31, 2026 | Complete Service OutageBetween 08:15 and 08:28 UTC, we experienced a complete service outage. The incident was caused by a software bug in a critical code path handling all API requests, which was triggered by a configuration change. The… | -33 min | Resolved |
| Jul 20, 2026 | Performance Degradation: AML ScreeningThe 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… | 1h 14m | Resolved |
| Jul 14, 2026 | SDK Initialization FailuresBetween 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… | -84 min | Resolved |
| Jun 3, 2026 | Limited TM creation failures due to invalid full name dataWe 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… | -152 min | Resolved |
| May 28, 2026 | Temporary ticketing system outageThe 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. | 1h 27m | Resolved |
| May 27, 2026 | Public documentation unavailableThis incident has been resolved. | 15h 48m | Resolved |
| May 26, 2026 | Limited access issue in the Admin PanelThe 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… | 59 min | Resolved |
| May 20, 2026 | CloudFlare DNS issueBetween 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… | -87 min | Resolved |
| May 18, 2026 | DDos attackThe 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… | 49h 42m | Resolved |
| May 16, 2026 | DDos attackThe incident has been resolved, and all services are operating normally. Our teams will continue monitoring the platform to ensure ongoing stability. We appreciate your patience and understanding throughout the… | 27h 36m | Resolved |
| May 16, 2026 | DDos attackOur Team has succesfully concluded the incident resolved. Everything is now operational. The attack took place between 07:15 UTC and 8:00 UTC. During the attack, we received a spike of 20–30x increase in total… | 6h 6m | Resolved |
| May 4, 2026 | Support integration for SlackWe 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… | 14h 45m | Resolved |
| Mar 26, 2026 | Incomplete PDF reports for reports generated on 2026-03-26 between 11:07 UTC - 12:50 UTCBetween 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… | 0 min | Resolved |
| Mar 16, 2026 | Clients may be unable to contact us at this time.The incident affecting incoming client messages has been resolved. All systems are now operating normally. | 0 min | Resolved |
| Mar 2, 2026 | EU Production Database Performance IncidentDescription: 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… | -5526 min | Resolved |
| Mar 2, 2026 | AWS UAE Region Infrastructure DegradationAs there is currently no estimated time of resolution from AWS regarding the UAE region outage, we are closing this incident. All affected customers have been successfully migrated to alternative regions shortly after… | 1370h 1m | Resolved |
| Feb 24, 2026 | Temporary Aggregation Inaccuracy in Transaction Monitoring RulesBetween 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… | -5910 min | Resolved |
| Dec 15, 2025 | Liveness Initialization IssueMobile 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… | 0 min | Resolved |
| Dec 11, 2025 | AML verifications disruptionOur 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… | -27 min | Resolved |
| Dec 10, 2025 | Delayed Liveness Initialization in WebSDKAfter 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… | 12 min | Resolved |
| Dec 5, 2025 | Partial service disruption due to Cloudflare outageWe 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… | 0 min | Resolved |
| Nov 28, 2025 | Dashboard UI issue affecting Transaction Monitoring, Travel Rule, and AML casesWe are happy to confirm the issue has been fully resolved. Should you have any additional questions, please, reach out to our Support team! | 5h 37m | Resolved |
| Nov 19, 2025 | Support Ticketing System DisruptionThe 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… | 44 min | Resolved |
| Nov 19, 2025 | Transaction Monitoring, Payment Method Check Advanced issuesRoot 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… | 2h 44m | Resolved |
| Nov 18, 2025 | Cloudflare-related issuesCloudflare 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… | 4h 59m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Sumsub incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Sumsub Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Sumsub acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Sumsub outage in this window ran 57d 2h, against a mean recovery of 3d 3h. If you depend on Sumsub in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.