Is Sumsub down?

Last checked 7m ago
Current status
Sumsub is up

No incidents right now.

Official status page: https://status.sumsub.com · Polled every 5 minutes · 10 components tracked

Sumsub is operational right now. Last checked 7m ago; the most recent incident resolved 2d ago.

Real-time Sumsub status, recent outages, and incident history — pulled directly from Sumsub's official status page at https://status.sumsub.com every 5 minutes. Pingoru tracks 10 Sumsub services and has captured 4 incidents in the last 90 days (99.78% uptime). Get email, Slack, Discord, or webhook alerts the moment Sumsub reports a new incident — free for 5 monitors, no credit card.

Users who monitor Sumsub also follow these Identity Management services: JumpCloud Dropbox Sign Ping Identity MobileIron GBG Onfido Persona Identities Thycotic Beyond Identity Ekata View all 6,000+ providers
Sumsub uptime 99.78% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Recent outages & incidents

Past 90 days
  1. Resolved
    Started Sep 15, 2026, 11:43 AM UTC · Resolved Sep 14, 2026, 01:00 PM UTC
    Timeline · 1 update
    • resolved · Sep 15, 2026, 11:43 AM UTC

      Between 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 errors. New verifications continued to be created and processed during this period. The issue has been fully resolved.

    Latest: Between 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…

  2. Resolved
    Started Aug 31, 2026, 08:00 AM UTC · Resolved Aug 31, 2026, 08:00 AM UTC
    Timeline · 1 update
    • resolved · Aug 31, 2026, 08:32 AM UTC

      Between 08:15 and 08:28 UTC, we experienced a complete service outage. The service has been restored and is now operational. We will provide further updates as more information becomes available.

    Latest: Between 08:15 and 08:28 UTC, we experienced a complete service outage. The service has been restored and is now operational. We will provide further updates as more information bec…

  3. Resolved 1h 14m
    Started Jul 20, 2026, 03:52 PM UTC · Resolved Jul 20, 2026, 05:07 PM UTC
    Timeline · 4 updates
    • monitoring · Jul 20, 2026, 03:52 PM UTC

      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.

    • monitoring · Jul 20, 2026, 03:55 PM UTC

      We are continuing to monitor for any further issues.

    • monitoring · Jul 20, 2026, 04:07 PM UTC

      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.

    • resolved · Jul 20, 2026, 05:07 PM UTC

      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.

    Latest: 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 auto…

  4. Resolved
    Started Jul 14, 2026, 08:24 AM UTC · Resolved Jul 14, 2026, 07:00 AM UTC
    Timeline · 1 update
    • resolved · Jul 14, 2026, 08:24 AM UTC

      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.

    Latest: 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. …

Outage history

Past 90 days · 4 incidents View full outage history →