itsmeDigitalID incident

itsme® P1 Incident - all services down

Critical Resolved View vendor source →

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

Started
Jun 04, 2026, 02:26 PM UTC
Resolved
Jun 04, 2026, 02:40 PM UTC
Duration
14m
Detected by Pingoru
Jun 04, 2026, 02:26 PM 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 Jun 04, 2026, 02:26 PM UTC

    Dear Partner, Since 4:20 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 Jun 04, 2026, 02:32 PM UTC

    Dear Partner, The service are restoring, we are monitoring the situation closely and will send new message when incident closure will be confirmed. Best regards, Operations Team [email protected]

  3. resolved Jun 04, 2026, 02:40 PM UTC

    Dear Partner, Our solution has been rolled out and the service has been restored. We apologize for any inconvenience this may have caused. Best regards, Operations Team [email protected]