itsmeDigitalID incident

itsme® P1 Incident -SOAP services

Major Resolved View vendor source →

itsmeDigitalID experienced a major incident on February 25, 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
Feb 25, 2026, 07:17 PM UTC
Resolved
Feb 25, 2026, 07:45 PM UTC
Duration
27m
Detected by Pingoru
Feb 25, 2026, 07:17 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 Feb 25, 2026, 07:17 PM UTC

    Dear Partner, Since about 6 PM CET, we are experiencing a technical problem, impacting our SOAP 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. identified Feb 25, 2026, 07:27 PM UTC

    Dear Partner, Our technical teams found the root cause and a solution will be rolled out. We expect the service to be restored shortly. We apologize for any inconvenience this may cause. Best regards, Operations Team [email protected]

  3. monitoring Feb 25, 2026, 07:41 PM 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 Feb 25, 2026, 07:45 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]