Company Logo

Is there an Sumsub outage?

Sumsub status: Systems Active

Last checked: 4 minutes ago

Get notified about any outages, downtime or incidents for Sumsub and 1800+ other cloud vendors. Monitor 10 companies, for free.

Subscribe for updates

Sumsub outages and incidents

Outage and incident data over the last 30 days for Sumsub.

There have been 0 outages or incidents for Sumsub in the last 30 days.

Severity Breakdown:

Tired of searching for status updates?

Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!

Sign Up Now

Components and Services Monitored for Sumsub

Outlogger tracks the status of these components for Xero:

API Active
MobileSDK Active
WebSDK Active
Component Status
API Active
MobileSDK Active
WebSDK Active

Latest Sumsub outages and incidents.

View the latest incidents for Sumsub and check for official updates:

Updates:

  • Time: May 12, 2023, 2:03 p.m.
    Status: Resolved
    Update: Date: 2023-05-12 Duration: 11:00 UTC - 11:09 UTC (9 minutes) Impact: Document uploading and fetching from the dashboard were not working. Incident Summary On May 12, 2023, our system experienced a disruption in document uploading and downloading functionality on the dashboard. The issue persisted for 9 minutes, during which time requests failed with HTTP 500 errors. Users were unable to upload documents or access them from the dashboard. Our team promptly investigated the issue and resolved it. We apologize for any inconvenience this incident may have caused, and we remain committed to providing reliable and high-quality service to our users. We will continue to monitor the situation and implement necessary measures to prevent similar issues in the future. Timeline 11:00 UTC - Received alerts from the monitoring system and initiated an investigation. 11:02 UTC - Root cause identified. 11:07 UTC - Root cause addressed and fixed. 11:09 UTC - Service restored and returned to normal.

Updates:

  • Time: April 6, 2023, 4:11 p.m.
    Status: Postmortem
    Update: Minor bug caused by back-end update. Issue was detected only on the old versions of MSDK \(1.18.\*\) Impact: Several dozens of users who were using an outdated version of the mobile SDK.
  • Time: April 6, 2023, 1:05 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: April 6, 2023, 12:30 p.m.
    Status: Investigating
    Update: We are currently investigating the issue.

Updates:

  • Time: Feb. 3, 2023, 5:55 p.m.
    Status: Postmortem
    Update: Around 15:50 UTC we received the first alerts on increased system load in our platform. Our automatic scaling system attempted to mitigate the problem by increasing the number of backend instances. During this time a significant amount of requests were still going through, but our system was showing an extreme delay performing any of these actions.This prompted our Engineering team to open an incident report and dive into a full scale investigation. As result we found out that IO was the root cause. It is important to clarify that our backend relies heavily on a distributed file system provided by AWS. We opened a case with AWS, as we worked around the clock on a plan to make our system responsive again, without knowing that the root cause had started on Amazon side. Here are some of the actions : 1\. We replaced the file system for another one with more aggressive settings. That action showed improvement, but unfortunately did not gave us expected results. This forced us to make some changes on the backend to prevent any performance degradation while working without distributed filesystem at all. 2\. Around 21:25 UTC - A fix was rolled out. And we confirmed, the changes made in the system were working with the expected performance. 3\. Around 00:15 UTC - AWS acknowledged, there were elevated latencies for the file system and and started investigation on their side 4\. Around 02:00 UTC - AWS identified the issue’s root cause and confirmed they are working on a fix. There were no further updates from AWS on the case yet. Although, this incident was not yet reflected on the global AWS status page.
  • Time: Feb. 2, 2023, 10:21 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: Feb. 2, 2023, 7:53 p.m.
    Status: Monitoring
    Update: A fix has been implemented and we are monitoring the results.
  • Time: Feb. 2, 2023, 7:40 p.m.
    Status: Identified
    Update: The issue has been identified and a fix is being implemented.
  • Time: Feb. 2, 2023, 6:40 p.m.
    Status: Investigating
    Update: We are continuing to investigate this issue.
  • Time: Feb. 2, 2023, 6:18 p.m.
    Status: Investigating
    Update: Service has encountered a technical problem with access for majority of clients. No images can be uploaded for applicants. Our team is investigating the incident.
  • Time: Feb. 2, 2023, 6:16 p.m.
    Status: Investigating
    Update: We are currently investigating this issue.
  • Time: Feb. 2, 2023, 4:30 p.m.
    Status: Identified
    Update: The issue has been identified and a fix is being implemented.
  • Time: Feb. 2, 2023, 4:30 p.m.
    Status: Investigating
    Update: Service has encountered a technical problem with access for majority of clients. No images can be uploaded for applicants. Our team is investigating the incident.

Updates:

  • Time: Dec. 2, 2022, 6:12 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: Dec. 2, 2022, 5:17 p.m.
    Status: Identified
    Update: Our service has encountered a technical problem preventing us from getting a response from the external source responsible for providing AML matches. In some cases, there may be an increase in verification time. Our team together with AML provider are actively investigating the incident and we will update you with more details as we have them.

Updates:

  • Time: Sept. 29, 2022, 7:48 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: Sept. 29, 2022, 7:11 p.m.
    Status: Monitoring
    Update: A fix has been implemented and we are monitoring the results.
  • Time: Sept. 29, 2022, 6:22 p.m.
    Status: Identified
    Update: Issue identified on our side. KYC checks take significantly longer time. LiveChat widgets are also affected. Customer support available only via e-mail or TG chat.
  • Time: Sept. 29, 2022, 6:09 p.m.
    Status: Investigating
    Update: We are continuing to investigate this issue.
  • Time: Sept. 29, 2022, 6:09 p.m.
    Status: Investigating
    Update: Currently applicant checks take significant longer time, than usually. No data has been lost and the system should be caught up shortly.

Check the status of similar companies and alternatives to Sumsub

KnowBe4
KnowBe4

Systems Active

Intapp
Intapp

Systems Active

Aderant
Aderant

Systems Active

Springbrook
Springbrook

Systems Active

AgentSync
AgentSync

Systems Active

MyCase - Public
MyCase - Public

Systems Active

Litify
Litify

Systems Active

Evotix
Evotix

Systems Active

Penneo A/S
Penneo A/S

Systems Active

Casetext
Casetext

Systems Active

FOSSA
FOSSA

Systems Active

Frequently Asked Questions - Sumsub

Is there a Sumsub outage?
The current status of Sumsub is: Systems Active
Where can I find the official status page of Sumsub?
The official status page for Sumsub is here
How can I get notified if Sumsub is down or experiencing an outage?
To get notified of any status changes to Sumsub, simply sign up to OutLogger's free monitoring service. OutLogger checks the official status of Sumsub every few minutes and will notify you of any changes. You can veiw the status of all your cloud vendors in one dashboard. Sign up here
What does Sumsub do?
A compliance-as-a-service provider with a full-cycle verification platform available in 220+ countries. Trusted by 2000+ clients with high pass rates. Book a free demo.

Start monitoring now!

Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.

Get Started for Free