itsmeDigitalID incident

itsme® P2 Incident

Resolved after 31 minutes, affecting OIDC private key JWT and Production - Identity - OIDC private key JWT and 1 more, on June 2, 2026.

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]

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

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

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]
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]

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.