checked Sep 11, 2026 4:17 PM UTC · Onfido's official status page
Onfido is up and running.
All components operational
Statusfield watches Onfido alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.
Email only. No password. Free.
4 reports published by Onfido in the last 30 days
When Onfido breaks, it is typically resolved in 1h 5m — median across 5 resolved incidents over 90 days.
resolvedSep 7 · 14:30 UTC
Between 14:30 and 15:30 UTC, customers in the CA region experienced degraded access to the Public API. A faulty deployment in the authentication layer caused valid tokens to be incorrectly rejected, resulting in failed API requests. The issue has been fully resolved. No action is required on your end. We apologise for the disruption.
Reported by Onfido on their status page.
resolvedSep 1 · 13:21 UTC
From approximately 1:21 PM UTC to 1:46 PM UTC, there was a disruption to accepting Document requests from the Web SDK as well as Entrust IDV SDKs for flows containing web modules. Onfido Android & iOS SDKs were not impacted. We apologize for this disruption. A detailed postmortem will follow once we've concluded our investigation.
Reported by Onfido on their status page.
postmortemSep 8 · 13:24 UTC
On August 26, 2026, an increase in the consider rate of Known Faces was observed during the period between 15:00 and 18:00 UTC. The overall observed consider rate of Known Faces increased from ~6% to ~23% across all regions. Perceived increase may have been higher or lower, depending on the client’s specific geography or vertical.
The was driven by a change to how matching scores are calculated for Known Faces matches, which inflated scores for non-matching faces and thus causing many reports to return false matches and a consider result.
The change introduced a new algorithm for scoring matching faces, which is intended to improve Known Faces recall performance. This was extensively evaluated and validated by internal benchmarks before being released. Inadvertently, the transition from benchmarks to production partially failed to account for particular production environment characteristics. At the root, a single constant wasn’t properly converted in the transition, resulting in wrong behavior of the new scoring algorithm.
15:20 UTC: Change to Known Faces is released
17:35 UTC: Increased consider rate on Known Faces is noticed.
17:50 UTC: Change is rolled back. Consider rate drops soon after.
We are reviewing internal benchmarks and testing procedures which can increase the safety of this kind of change. Specifically, ensuring internal testing reflects the real production landscape when it comes to datasets and that transitions from internal benchmarks and experiments to production are thoroughly tested.
In addition, change procedures will be carried out with tighter monitoring so it allows us to notice and act faster.
Reported by Onfido on their status page.
postmortemSep 8 · 13:17 UTC
On 24 August 2026, between 15:00 UTC and 06:53 UTC the following morning, Facial Similarity Motion checks using randomness challenges failed at a much higher rate than normal in the EU region. A stricter validation was applied to all customers in the region when it should have been limited to a single customer, causing verifications that would otherwise have passed to be rejected. Affected reports were returned with a "Visual Authenticity" failure.
Because Motion checks are fully automated, the end users behind these reports were rejected with no manual review, and some attempted the check again and were rejected a second time.
The clear rate for these checks fell from around 97% to around 54% for approximately 1.67% of Facial Similarity Motion reports were affected. Disabling the change restored normal clear rates immediately. Other Motion checks and other regions were unaffected.
A stricter validation of the motion randomness challenge was being trialled with a single customer, controlled by a per-customer configuration setting. A bug in our code meant the setting was evaluated without the customer identifier, so the stricter validation was applied to all customers in the EU region running Motion with randomness checks rather than to the intended one. Verifications that would have passed under the standard validation were rejected instead, and reported under the "Visual Authenticity" breakdown. No customer configuration or submitted data was at fault.
All times UTC.
Reported by Onfido on their status page.
