Live  /  IDnow  /  Incident

IDnow: Service Disruption

IDnow · idnow.deResolved2026-10-26 01:01 UTC
Public — what happened

Summary

IDnow said it experienced a service disruption beginning at 00:05 UTC on 2026-10-26, without specifying which features or customers were affected. By 00:23 UTC the company said it had found the problem and was working on a fix, and at 00:46 UTC it said the fix was in place and it was watching the results. The incident was marked resolved at 01:01 UTC, and IDnow did not describe a cause.

Affected

VideoIdent, eID, AutoIdent, AutoIdent QES, POS, eSign, InstantSign, eSign Wallet

As listed on IDnow’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach IDnow against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for IDnow: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the IDnow report →

More from IDnow

Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.

The full archive is on the IDnow status & history page.

Related: IDnow status & history. SquidGrid is not affiliated with IDnow.