itsmeDigitalID incident

itsme® P1 Incident

Critical Resolved View vendor source →

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

Started
May 27, 2024, 08:08 AM UTC
Resolved
May 27, 2024, 09:10 AM UTC
Duration
1h 1m
Detected by Pingoru
May 27, 2024, 08:08 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 May 27, 2024, 08:08 AM UTC

    Dear Partner, Since about 09:45 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. investigating May 27, 2024, 08:53 AM UTC

    Dear Partner, The situation is improving after some corrective actions undertaken, we are checking further our systems heath and will keep you posted. Best regards, Operations Team [email protected]

  3. resolved May 27, 2024, 09:10 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]