itsmeDigitalID incident

itsme® P2 Incident

Major Resolved View vendor source →

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

Started
Jun 02, 2026, 07:28 AM UTC
Resolved
Jun 02, 2026, 08:00 AM UTC
Duration
31m
Detected by Pingoru
Jun 02, 2026, 07:28 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 Jun 02, 2026, 07:28 AM UTC

    Dear Partner, We are experiencing a technical problem, impacting between 12,5 and 25% 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. resolved Jun 02, 2026, 08:00 AM 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]