itsmeDigitalID incident

itsme® P1 Incident

Resolved after 39 minutes, affecting OIDC private key JWT and Production - Identity - OIDC private key JWT and 1 more, on May 4, 2026.

resolved May 04, 2026, 12:18 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]

Started
May 04, 2026, 11:38 AM UTC
Resolved
May 04, 2026, 12:18 PM UTC
Duration
39m
Detected by Pingoru
May 04, 2026, 11:38 AM UTC

Affected components

OIDC private key JWTProduction - Identity - OIDC private key JWTOIDC Client SecretProduction - Identity - OIDC Client SecretSOAPProduction - Identity - SOAPOASIS DSSProduction - Qualified Electronic Signature - OASIS DSSCSCProduction - Qualified Electronic Signature - CSC

Update timeline

  1. investigating May 04, 2026, 11:38 AM UTC

    Dear Partner, Since 13:23 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 May 04, 2026, 11:46 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]

  3. resolved May 04, 2026, 12:18 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]

Your product runs on more than itsmeDigitalID

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →