itsmeDigitalID incident

itsme® P1 Incident

Major Resolved View vendor source →

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

Started
Mar 10, 2025, 11:24 AM UTC
Resolved
Mar 10, 2025, 11:50 AM UTC
Duration
25m
Detected by Pingoru
Mar 10, 2025, 11:24 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 Mar 10, 2025, 11:24 AM UTC

    Dear Partner, Since 12h05 CET today, we are experiencing a technical problem, impacting about 50% 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 Mar 10, 2025, 11:50 AM UTC

    Dear Partner, Our solution has been rolled out and the service has been restored at 12h30 today. We apologize for any inconvenience this may have caused. Best regards, Operations Team [email protected]