itsmeDigitalID incident

itsme® P1 Incident

Critical Resolved View vendor source →

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

Started
Dec 10, 2025, 08:54 AM UTC
Resolved
Dec 10, 2025, 09:49 AM UTC
Duration
55m
Detected by Pingoru
Dec 10, 2025, 08:54 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 Dec 10, 2025, 08:54 AM UTC

    Dear Partner, Since 9:40 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. investigating Dec 10, 2025, 09:29 AM UTC

    Dear Partner, Our technical teams are still investigating the issue, systems are recovering; we will keep you posted once full service will be back. We apologize for any inconvenience this may cause. Best regards, Operations Team [email protected]

  3. monitoring Dec 10, 2025, 09:36 AM UTC

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

  4. resolved Dec 10, 2025, 09:49 AM UTC

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