Onfido Outage History

Onfido is up right now

Onfido had 45 outages in the last 2 years totaling 92h 8m of downtime — averaging 1.8 incidents per month.

There were 45 Onfido outages since June 2, 2025 totaling 92h 8m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.onfido.com

Minor July 27, 2026

Delays in processing reports in the US cluster

Detected by Pingoru
Jul 27, 2026, 06:12 PM UTC
Resolved
Jul 27, 2026, 07:21 PM UTC
Duration
1h 9m
Affected: APIDocument VerificationFacial SimilarityKnown faces
Timeline · 6 updates
  1. investigating Jul 27, 2026, 06:12 PM UTC

    We are currently investigating delays in our US cluster for the processing of Facial Similarity, Document and Known Faces reports.

  2. investigating Jul 27, 2026, 06:23 PM UTC

    We are seeing degraded performance of some nodes in our search cluster for indexed faces. We continue to investigate the root cause and possible remediations.

  3. identified Jul 27, 2026, 06:51 PM UTC

    We've identified the root cause of degraded performance in our US search cluster and are actively working to resolve it. We'll follow up once fully restored.

  4. monitoring Jul 27, 2026, 07:18 PM UTC

    We implemented a fix and continue to monitor the quality of processing time, which is now improved.

  5. monitoring Jul 27, 2026, 07:20 PM UTC

    Processing time keeps improving, all systems are now operational.

  6. resolved Jul 27, 2026, 07:21 PM UTC

    Processing times are back to normal. This issue is now resolved. Post-mortem to follow soon.

Read the full incident report →

Minor July 24, 2026

Identity Enhanced issues

Detected by Pingoru
Jul 24, 2026, 04:18 AM UTC
Resolved
Jul 24, 2026, 07:08 AM UTC
Duration
2h 49m
Affected: Identity EnhancedIdentity Enhanced
Timeline · 5 updates
  1. investigating Jul 24, 2026, 04:18 AM UTC

    Identity Enhanced is experiencing a major decrease in clear rates for applicants all other the world except UK

  2. identified Jul 24, 2026, 04:36 AM UTC

    We are working with our third-party provider to resolve the issue and will share updates as they become available.

  3. identified Jul 24, 2026, 04:55 AM UTC

    We are continuing to work on a fix for this issue.

  4. monitoring Jul 24, 2026, 05:09 AM UTC

    We are seeing our provider's service recovery and request success rates improving. We continue to monitor the situation closely.

  5. resolved Jul 24, 2026, 07:08 AM UTC

    The provider has resolved the issue, and the service is now operating normally

Read the full incident report →

Critical June 23, 2026

QES tasks cannot complete because our provider is encountering issues.

Detected by Pingoru
Jun 23, 2026, 02:38 AM UTC
Resolved
Jun 23, 2026, 03:49 AM UTC
Duration
1h 11m
Affected: QES
Timeline · 5 updates
  1. investigating Jun 23, 2026, 02:38 AM UTC

    We cannot complete QES tasks because our electronic signature provider is encountering issues.

  2. identified Jun 23, 2026, 02:57 AM UTC

    Our provider is experiencing issues. All QES tasks cannot complete for now.

  3. identified Jun 23, 2026, 03:20 AM UTC

    Our provider is still experiencing issues. All QES tasks cannot complete for now.

  4. monitoring Jun 23, 2026, 03:45 AM UTC

    The issue has been fixed. We're monitoring and resuming blocked QES tasks, if they can be.

  5. resolved Jun 23, 2026, 03:49 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 17, 2026

Electronic signature increased TaT

Detected by Pingoru
Jun 17, 2026, 04:59 AM UTC
Resolved
Jun 17, 2026, 09:23 AM UTC
Duration
4h 23m
Affected: QES
Timeline · 7 updates
  1. identified Jun 17, 2026, 04:59 AM UTC

    One of our providers is still experiencing issues, resulting in higher TaT for electronic signature tasks.

  2. identified Jun 17, 2026, 05:30 AM UTC

    Our provider is actively working on fixing the issue.

  3. identified Jun 17, 2026, 06:19 AM UTC

    Our provider is still working on fixing the issue. We're monitoring the impact and we're making sure to keep the TaT as low as possible, considering the situation.

  4. identified Jun 17, 2026, 06:50 AM UTC

    Our provider's error rate dropped significantly. The TaT of QES tasks is now close to the usual value.

  5. identified Jun 17, 2026, 08:17 AM UTC

    We're working closely with our provider to find the reason of the remaining errors. The error rate contacting our provider is stable and the impact on the QES task TaT is under control.

  6. monitoring Jun 17, 2026, 08:48 AM UTC

    Our provider was able to fix the issue and we don't get any error when contacting them. The TaT of QES tasks is back to normal. Monitoring the situation to make sure the errors don't come back.

  7. resolved Jun 17, 2026, 09:23 AM UTC

    The QES tasks TaT is back to normal.

Read the full incident report →

Minor June 16, 2026

Electronic signature high TaT

Detected by Pingoru
Jun 16, 2026, 10:19 PM UTC
Resolved
Jun 16, 2026, 11:17 PM UTC
Duration
58m
Affected: QES
Timeline · 3 updates
  1. identified Jun 16, 2026, 10:19 PM UTC

    Our electronic signature tasks are taking more time to complete because one of our providers is doing some maintenance.

  2. identified Jun 16, 2026, 10:52 PM UTC

    Our provider is still not able to answer to all requests, resulting in longer-than-usual electronic signature task processing time.

  3. resolved Jun 16, 2026, 11:17 PM UTC

    The service is operational again.

Read the full incident report →

Major June 6, 2026

Partial outage for Watchlist reports

Detected by Pingoru
Jun 06, 2026, 02:08 PM UTC
Resolved
Jun 06, 2026, 03:49 PM UTC
Duration
1h 41m
Affected: WatchlistWatchlist
Timeline · 4 updates
  1. investigating Jun 06, 2026, 02:08 PM UTC

    Some Watchlist search search profiles are not working correctly the impacted reports are not being processed. We are investigation the root cause.

  2. identified Jun 06, 2026, 02:36 PM UTC

    We identified the issue and are implementing a fix.

  3. monitoring Jun 06, 2026, 03:05 PM UTC

    The issue has been fixed, and the reports are being processed correctly. We are still monitoring the service.

  4. resolved Jun 06, 2026, 03:49 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 11, 2026

Degraded performance for Identity Reports in UK jurisdiction

Detected by Pingoru
May 11, 2026, 11:11 PM UTC
Resolved
May 12, 2026, 01:14 PM UTC
Duration
14h 2m
Affected: Identity Enhanced
Timeline · 3 updates
  1. identified May 12, 2026, 12:25 PM UTC

    We are facing issues with one of our providers and we see a slight decrease in clear rate for Identity Reports in UK jurisdiction

  2. monitoring May 12, 2026, 12:55 PM UTC

    A fix has been implemented and we are monitoring the results. All clear rates should be back to normal

  3. resolved May 12, 2026, 01:14 PM UTC

    All reports are back to normal.

Read the full incident report →

Critical May 5, 2026

QES tasks outage

Detected by Pingoru
May 05, 2026, 06:52 AM UTC
Resolved
May 05, 2026, 08:39 AM UTC
Duration
1h 46m
Affected: QES
Timeline · 5 updates
  1. investigating May 05, 2026, 06:52 AM UTC

    We noticed an issue with our QES tasks, we're investigating.

  2. identified May 05, 2026, 06:56 AM UTC

    Our provider is experiencing issues. All QES tasks cannot complete for now.

  3. identified May 05, 2026, 07:35 AM UTC

    Our provider is fixing the issue. QES tasks still cannot complete.

  4. monitoring May 05, 2026, 08:04 AM UTC

    The issue has been fixed. We're monitoring and resuming blocked QES tasks, if they can be.

  5. resolved May 05, 2026, 08:39 AM UTC

    QES is operational again.

Read the full incident report →

Critical April 21, 2026

QES tasks degraded performance

Detected by Pingoru
Apr 21, 2026, 02:28 PM UTC
Resolved
Apr 21, 2026, 05:12 PM UTC
Duration
2h 44m
Affected: QES
Timeline · 5 updates
  1. identified Apr 21, 2026, 02:56 PM UTC

    We identified an issue with one of our provider and some QES tasks may encounter some problems.

  2. identified Apr 21, 2026, 03:14 PM UTC

    Our provider is still experiencing issues. All QES tasks cannot complete for now.

  3. identified Apr 21, 2026, 04:12 PM UTC

    Our provider continues experiencing issues and is working on a fix.

  4. identified Apr 21, 2026, 05:02 PM UTC

    Our provider is slowly recovering, we expect some QES tasks to complete.

  5. resolved Apr 21, 2026, 05:12 PM UTC

    QES is operational again.

Read the full incident report →

Major February 3, 2026

QES tasks partial outage

Detected by Pingoru
Feb 03, 2026, 10:42 AM UTC
Resolved
Feb 03, 2026, 01:16 PM UTC
Duration
2h 33m
Affected: QES
Timeline · 6 updates
  1. identified Feb 03, 2026, 10:42 AM UTC

    One of our provider is experiencing issues. QES capture tasks will fail and QES verification tasks will have an increase in TaT.

  2. identified Feb 03, 2026, 11:13 AM UTC

    The provider is working on a fix, QES is still suffering a partial outage.

  3. identified Feb 03, 2026, 11:44 AM UTC

    The provider is still working on a fix.

  4. identified Feb 03, 2026, 12:16 PM UTC

    The provider is still working on a fix. QES verification tasks may start to time out, depending on their configuration, as we passed 90 minutes of downtime.

  5. monitoring Feb 03, 2026, 12:46 PM UTC

    The provider fixed the issue. We can confirm our QES tasks are now processed correctly. We'll monitor the situation to make sure the error is indeed fixed.

  6. resolved Feb 03, 2026, 01:16 PM UTC

    We can confirm the error stopped and services are stable and operational.

Read the full incident report →

Notice January 20, 2026

High Processing times for Video Facial Similarity Checks

Detected by Pingoru
Jan 20, 2026, 02:20 PM UTC
Resolved
Jan 14, 2026, 01:30 AM UTC
Duration
—
Timeline · 2 updates
  1. resolved Jan 20, 2026, 02:20 PM UTC

    Video facial similarity tasks are taking longer than expected to complete

  2. postmortem Jan 20, 2026, 02:21 PM UTC

    ### Summary _An increase of Facial Similarity Video Manual tasks backlog resulted in higher processing times for about 21% of that variant’s traffic._ ### Root Causes _A spike in Biometric Video volumes overwhelmed our BPO resources, lengthening Facial Similarity Video check turnaround times impacting around 20% of variant traffic._ ### Timeline _01:16 GMT: A significant backlog of tasks was reported._ _03:27 GMT: BPO team allocated more analysts to process pending video tasks._ _06:33 GMT: Backlog was cleared._ ### Remedies Not applicable: the increase in TaT resulted exclusively from an unexpected spike in volume that created a backlog for manual analysts. There were no system issues.

Read the full incident report →

Major December 19, 2025

Errors when processing checks in Canada region

Detected by Pingoru
Dec 19, 2025, 10:35 AM UTC
Resolved
Dec 19, 2025, 11:00 AM UTC
Duration
25m
Affected: APIDocument Verification
Timeline · 4 updates
  1. identified Dec 19, 2025, 10:35 AM UTC

    The issue has been identified and we are proceeding to the fix. We will provide an update in 15 minutes.

  2. identified Dec 19, 2025, 10:39 AM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring Dec 19, 2025, 10:52 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Dec 19, 2025, 11:00 AM UTC

    This incident has been resolved.

Read the full incident report →

Major December 18, 2025

Degraded performance of QES and Evidence File products

Detected by Pingoru
Dec 18, 2025, 11:26 AM UTC
Resolved
Dec 18, 2025, 12:31 PM UTC
Duration
1h 5m
Affected: QES
Timeline · 3 updates
  1. monitoring Dec 18, 2025, 11:26 AM UTC

    Our QTSP provider is currently experiencing technical issues that are impacting the performance of our Qualified Electronic Signature (QES) and Evidence File services. We are actively monitoring the situation and will provide updates as soon as more information becomes available.

  2. monitoring Dec 18, 2025, 11:49 AM UTC

    Performance of the Evidence File service has been fully restored. However, the Qualified Electronic Signature (QES) service continues to experience significant degradation due to ongoing issues on the QTSP provider’s side. We are actively monitoring the situation and will share further updates as soon as possible.

  3. resolved Dec 18, 2025, 12:31 PM UTC

    The incident was resolved

Read the full incident report →

Minor December 9, 2025

Delays on Dashboard

Detected by Pingoru
Dec 09, 2025, 01:33 PM UTC
Resolved
Dec 09, 2025, 01:46 PM UTC
Duration
12m
Affected: Dashboard
Timeline · 2 updates
  1. identified Dec 09, 2025, 01:33 PM UTC

    We accumulated a large backlog of messages to update OpenSearch and we are currently processing it. The backlog should be cleared in the next hours.

  2. resolved Dec 09, 2025, 01:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Major November 14, 2025

High flagging rate for Document Video Reports

Detected by Pingoru
Nov 14, 2025, 01:22 PM UTC
Resolved
Nov 14, 2025, 02:10 PM UTC
Duration
48m
Affected: Document VerificationDocument VerificationDocument Verification
Timeline · 4 updates
  1. identified Nov 14, 2025, 01:22 PM UTC

    The issue has been identified and a fix is being rolled out. We will provide a further update in 30 minutes.

  2. monitoring Nov 14, 2025, 01:48 PM UTC

    The issue has been fixed for new checks going forward. We are still working on assessing the impact for the completed checks. We will provide a further update in 30 minutes.

  3. resolved Nov 14, 2025, 02:10 PM UTC

    This issue is now resolved: We take a lot of pride in running a robust, reliable service and we're working hard to make sure this does not happen again. A detailed postmortem will follow once we've concluded our investigation.

  4. postmortem Nov 18, 2025, 04:26 PM UTC

    ### Summary A change was deployed with a bug that resulted in ~30% of all Document Video Reports during a 3 hour period to be falsely rejected for Invalid Media Signature. ### Root Causes This incident was caused by a change deployed to our backend systems, that started incorrectly marking reports with unsigned medias as having incorrect signatures. ### Timeline 09:52 GMT: A change is deployed incorrectly marking unsigned medias as having invalid signatures 12:33 GMT: The team that owns the service is alerted of the issue 12:54 GMT: The change in media signatures handling is identified as the root cause 13:07 GMT: The service is rolled back, and the error stops ### Remedies We are refining our monitoring for the relevant service, so that issues similar to this one will be resolved in a more timely manner. We are reviewing our end to end test suite to ensure consistency in media signature verification.

Read the full incident report →