itsmeDigitalID incident

itsme® P1 Incident

Resolved after 1 hour 31 minutes, affecting OIDC private key JWT and Production - Identity - OIDC private key JWT and 1 more, on January 5, 2026.

resolved Jan 05, 2026, 10:08 PM UTC

Dear Partner, Our systems are now stable and incident is closed. We apologize for any inconvenience this may have caused. Best regards, Operations Team [email protected]

Started
Jan 05, 2026, 08:37 PM UTC
Resolved
Jan 05, 2026, 10:08 PM UTC
Duration
1h 31m
Detected by Pingoru
Jan 05, 2026, 08:37 PM 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

  1. investigating Jan 05, 2026, 08:37 PM UTC

    Dear Partner, Since 9:10 PM CET, we are experiencing a technical problem, impacting 25% or more of our transactions. 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]

  2. monitoring Jan 05, 2026, 09:16 PM UTC

    Dear Partner, The root cause of the incident has been identified and corrective actions have been set in place, we are monitoring our systems and will keep you posted. We are monitoring the situation closely. We apologize for any inconvenience this may have caused. Best regards, Operations Team [email protected]

  3. resolved Jan 05, 2026, 10:08 PM UTC

    Dear Partner, Our systems are now stable and incident is closed. We apologize for any inconvenience this may have caused. Best regards, Operations Team [email protected]

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.

Add your stack →