Yoti incident

INC-3586 (P1 | High Priority)

Resolved after 1 hour 24 minutes, affecting Digital ID and Identity verification and 1 more, on January 16, 2026.

postmortem Jan 16, 2026, 09:28 AM UTC

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 investigation, we found the issue was caused by an unexpected storage bottleneck within our infrastructure. One of our storage drives \(an OSD\) had not cleared out old data as it usually would, which led to it reaching its capacity limit. When this occurred, the drive automatically switched itself to a ‘read-only’ safety mode. While this impacted service availability, it is also a built-in feature designed specifically to protect the integrity of the data. We have now resolved the immediate issue and services are running normally. Our engineering team is currently investigating why the drive’s automated cleanup process did not trigger as expected, and we are looking closely at the system logic to ensure this remains an isolated incident. We sincerely apologise for any frustration or inconvenience this may have caused you today. Thank you for your patience while we get to the bottom of this.

Started
Jan 16, 2026, 06:32 AM UTC
Resolved
Jan 16, 2026, 07:56 AM UTC
Duration
1h 24m
Detected by Pingoru
Jan 16, 2026, 06:32 AM UTC

Affected components

Digital IDIdentity verificationIdentity verificationAge verificationIdentity verification portalAge estimationAge verificationAge estimationeSignaturesYoti Hub

Update timeline

  1. investigating Jan 16, 2026, 06:32 AM UTC

    We are experiencing issues with all our services.

  2. investigating Jan 16, 2026, 06:41 AM UTC

    We are continuing to investigate this issue.

  3. investigating Jan 16, 2026, 07:02 AM UTC

    We are continuing to investigate this issue.

  4. identified Jan 16, 2026, 07:22 AM UTC

    We have identified the cause of this incident and we are working to restore the all our service as soon as possible.

  5. identified Jan 16, 2026, 07:30 AM UTC

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

  6. monitoring Jan 16, 2026, 07:49 AM UTC

    We have fixed all our services. Our engineers will monitor the situation until we declare the incident resolved.

  7. resolved Jan 16, 2026, 07:56 AM UTC

    The services is fully operational. This incident has been resolved.

  8. postmortem Jan 16, 2026, 09:28 AM UTC

    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 investigation, we found the issue was caused by an unexpected storage bottleneck within our infrastructure. One of our storage drives \(an OSD\) had not cleared out old data as it usually would, which led to it reaching its capacity limit. When this occurred, the drive automatically switched itself to a ‘read-only’ safety mode. While this impacted service availability, it is also a built-in feature designed specifically to protect the integrity of the data. We have now resolved the immediate issue and services are running normally. Our engineering team is currently investigating why the drive’s automated cleanup process did not trigger as expected, and we are looking closely at the system logic to ensure this remains an isolated incident. We sincerely apologise for any frustration or inconvenience this may have caused you today. Thank you for your patience while we get to the bottom of this.

Your product runs on more than Yoti

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →