itsmeDigitalID incident

itsme® P1 Incident

Critical Resolved View vendor source →

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

Started
Sep 03, 2024, 01:01 PM UTC
Resolved
Sep 03, 2024, 02:11 PM UTC
Duration
1h 9m
Detected by Pingoru
Sep 03, 2024, 01:01 PM 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 Sep 03, 2024, 01:01 PM UTC

    Dear Partner, Since 14:50 PM CET, we are experiencing a technical problem, impacting 50% 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. identified Sep 03, 2024, 01:14 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Sep 03, 2024, 01:52 PM UTC

    Dear Partner, Our solution is being rolled out and the service is restoring. We are monitoring the situation closely and will confirm once fully restored. We apologize for any inconvenience this may have caused. Best regards, Operations Team [email protected]

  4. monitoring Sep 03, 2024, 02:06 PM UTC

    Dear Partner, Our 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]

  5. resolved Sep 03, 2024, 02:11 PM 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]