itsmeDigitalID incident

itsme® P2 Incident - eID enrolments not available

Resolved after 3 hours 34 minutes, affecting OIDC private key JWT and Production - Identity - OIDC private key JWT and 1 more, on February 16, 2026.

monitoring Feb 16, 2026, 09:47 AM UTC

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

Started: Feb 16, 2026, 09:28 AM UTC
Resolved: Feb 16, 2026, 01:02 PM UTC
Duration: 3h 34m
Detected by Pingoru: Feb 16, 2026, 09:28 AM UTC

Affected components

OIDC private key JWTProduction - Identity - OIDC private key JWTOIDC Client SecretProduction - Identity - OIDC Client SecretSOAPProduction - Identity - SOAPOASIS DSSProduction - Qualified Electronic Signature - OASIS DSSCSCProduction - Qualified Electronic Signature - CSC

Update timeline

investigating Feb 16, 2026, 09:28 AM UTC

Dear Partner, We are experiencing a technical problem, blocking the activation of an itsme account with an eID-card. Activation of an itsme account using the bank app or card(reader) is still possible. Our technical teams are investigating and working on a solution to resolve the issue as fast as possible. We apologize for any inconvenience this may cause. Best regards, Operations Team [email protected]
monitoring Feb 16, 2026, 09:47 AM UTC

A fix has been implemented and we are monitoring the results.
resolved Feb 16, 2026, 01:02 PM UTC

This incident has been resolved.

Your product runs on more than itsmeDigitalID

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