itsmeDigitalID incident

itsme® P1 Incident

Critical Resolved View vendor source →

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

Started
May 06, 2024, 08:56 AM UTC
Resolved
May 06, 2024, 09:53 AM UTC
Duration
57m
Detected by Pingoru
May 06, 2024, 08:56 AM UTC

Affected components

Production - Identity - OIDC private key JWTProduction - Identity - OIDC private key JWTProduction - Qualified Electronic Signature - OASIS DSSProduction - Qualified Electronic Signature - OASIS DSSProduction - Account ManagementProduction - Account Management

Update timeline

  1. investigating May 06, 2024, 08:56 AM UTC

    Dear Partner, Please be informed that since 10:15 AM CET, we are experiencing issues on our infrastructure causing our systems to be instable. 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 06, 2024, 09:41 AM UTC

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

  3. resolved May 06, 2024, 09:53 AM UTC

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