Yoti Outage History

22 incidents recorded over the last 365 days, 22 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Yoti status100.00% uptime history

Every Recorded Yoti Incident

Yoti incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 15, 2026Information NoticeThe incident has been successfully resolved and all systems are stable. Thank you for your patience.3h 36mResolved
Sep 28, 2026Information noticeThe issue with our third-party service provider affecting CPF checks has been resolved, customers in Brazil should no longer experience errors when using the Age Verification Service.2h 29mResolved
Sep 24, 2026INC-3854 (P2 - Medium priority)The Digital ID and IDV service is now fully operational. The incident has been successfully resolved and all systems are stable. Thank you for your patience.8 minResolved
Sep 19, 2026INC-3846 (P1 - High Priority)**Saturday 19th September 10:06 UTC - Saturday 19th September 14:00 UTC** We are writing to provide an update regarding a brief service interruption that impacted our systems earlier today. Our monitoring alerted us…3h 41mResolved
Sep 15, 2026INC-3843 (P2 - Medium Priority)**Monday 14th September: 19:56 UTC - Tuesday 15th September: 08:56 UTC** ‌ We are writing to provide an update regarding a temporary service disruption, affecting our Identity Verification and Age Estimation services…6h 30mResolved
Aug 12, 2026INC-3820 (P2- Medium Priority)**Wednesday 12th August \(14:57 – 15:53 UTC\)** We are writing to inform you about a temporary service interruption that affected some of our services yesterday, during which time some customers may have experienced…7 minResolved
Aug 10, 2026INC-3818 (P3 - Low Priority)The IDV and Digital ID services are fully operational. This incident has been resolved.2h 8mResolved
Aug 5, 2026High volume of requestsThe volume of requests are now back to normal level and all services are functioning correctly.6h 43mResolved
Jul 20, 2026INC-3796 (P1- High Priority)**Monday 20 July 2026 from 09:44 UTC - 10:20 UTC** ‌ We recently experienced a temporary disruption affecting our Identity Verification service in the USA. Our Network Operations Centre \(NOC\) quickly identified the…35 minResolved
Jun 24, 2026INC-3763 (P2- Medium Priority)Resolved: Temporary Performance Degradation with Identity verification service Yesterday, between 09:52 UTC and 12:22 UTC. We identified a performance degradation affecting the Identity verification service. During…0 minResolved
Jun 22, 2026INC-3762 (P1 - High Priority)**Monday 22nd June 2026 from 14:52 UTC - 15:10 UTC** We are writing to provide an update regarding a brief service interruption that impacted Yoti systems earlier today. Our monitoring systems alerted us to an…18 minResolved
May 19, 2026INC-3727 (P2- Medium Priority)We are writing to provide an update regarding a temporary service disruption that affected Yoti services earlier today. Our Network Operations Centre \(NOC\) identified a degradation affecting our Digital ID, Identity…39 minResolved
May 12, 2026High volume of requestsThe volume of requests are now back to normal level and all services are functioning correctly.30h 27mResolved
May 10, 2026INC-3723 (P1 - High Priority)**Sunday 10th May 2026 - Tuesday 12th May** We are pleased to confirm that all Yoti services have returned to normal operation following a period of service instability. Starting on the evening of May 10th, our…43h 41mResolved
Apr 20, 2026INC-3704(P1 - High Priority)**Thursday 20th April 2026 from 15:45 UTC - 16:13 UTC** Earlier this evening, the Yoti Network Operations Centre \(NOC\) detected a surge in inbound traffic directed at our Digital Identity, Identity Verification…28 minResolved
Apr 10, 2026INC-3674 (P1 - High Priority)A load balancer failure at one of our data centres caused service disruption. Our engineering team identified the issue, rerouted affected traffic to restore services, and subsequently brought the impacted load balancer…22 minResolved
Feb 12, 2026INC-3620 (P1 | High Priority)**Thursday 12th February 2026 from 15:05 UTC - 15:56 UTC** We are writing to provide an update concerning a temporary service interruption that affected Yoti services earlier today. Our Network Operations Centre…43 minResolved
Feb 10, 2026INC-3615 (P1 | High Priority)**Tuesday 10th February 2025 from 20:22 UTC - 21:47 UTC** Earlier this evening, the Yoti Network Operations Centre \(NOC\) detected an surge in inbound traffic directed at our Identity Verification, Age Verification…1h 21mResolved
Jan 16, 2026INC-3586 (P1 | High Priority)We are writing to share an update about a temporary interruption that affected our services earlier this morning. Our Network Operations Centre \(NOC\) first spotted an increase in error rates at 06:24 UTC.  On…1h 24mResolved
Jan 9, 2026INC-3576 (P2 - Medium Priority)Earlier today, some customers may have experienced errors \(5xx\) while accessing our services. This was due to a technical communication issue between our systems. Our monitoring alerts identified the spike…1h 14mResolved
Nov 6, 2025High volume of requestsThe volume of requests are now back to normal level and all services are functioning correctly.5h 26mResolved
Nov 6, 2025INC-3490 (P3 - Low Priority)The IDV and Digital ID services are fully operational. This incident has been resolved.2h 27mResolved

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 Yoti 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 Yoti 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 Yoti 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 Yoti outage in this window ran 1d 19h, against a mean recovery of 5h 12m. If you depend on Yoti 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.