itsmeDigitalID incident

itsme® P1 Incident

Critical Resolved View vendor source →

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

Started
Jun 19, 2024, 07:07 AM UTC
Resolved
Jun 19, 2024, 07:41 AM UTC
Duration
34m
Detected by Pingoru
Jun 19, 2024, 07:07 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 Jun 19, 2024, 07:07 AM UTC

    Dear Partner, Since approximately 08:55 AM 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 Jun 19, 2024, 07:20 AM UTC

    Dear Partner, A 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 Jun 19, 2024, 07:41 AM UTC

    Dear Partner, Monitoring shows that our systems are stable since our solution has been rolled out and this incident is therefore closed. We apologize for any inconvenience this may have caused. Best regards, Operations Team [email protected]