itsmeDigitalID incident

itsme® P1 Incident

Critical Resolved View vendor source →

itsmeDigitalID experienced a critical incident on April 20, 2026 affecting Production - Identity - OIDC private key JWT and Production - Identity - OIDC private key JWT and 1 more component, lasting 27m. The incident has been resolved; the full update timeline is below.

Started
Apr 20, 2026, 07:31 AM UTC
Resolved
Apr 20, 2026, 07:59 AM UTC
Duration
27m
Detected by Pingoru
Apr 20, 2026, 07:31 AM UTC

Affected components

Production - Identity - OIDC private key JWTProduction - Identity - OIDC private key JWTProduction - Identity - OIDC Client SecretProduction - Identity - OIDC Client SecretProduction - Identity - SOAPProduction - Identity - SOAPProduction - Qualified Electronic Signature - OASIS DSSProduction - Qualified Electronic Signature - OASIS DSSProduction - Qualified Electronic Signature - CSCProduction - Qualified Electronic Signature - CSC

Update timeline

  1. investigating Apr 20, 2026, 07:31 AM UTC

    Dear Partner, Since 09:25 AM 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 Apr 20, 2026, 07:52 AM UTC

    Dear Partner, Our technical teams found the root cause, our systems are recovering but we are carefully checking the stability of our environments. We will send you further communication when the issue will be fully resolved. We apologize for any inconvenience this may cause. Best regards, Operations Team [email protected]

  3. resolved Apr 20, 2026, 07:59 AM UTC

    Dear Partner, Our services have been restored. We apologize for any inconvenience this may have caused. Best regards, Operations Team [email protected]