itsmeDigitalID incident

itsme® P2 Incident

Minor Resolved View vendor source →

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

Started
Jul 30, 2024, 01:02 PM UTC
Resolved
Jul 30, 2024, 02:23 PM UTC
Duration
1h 20m
Detected by Pingoru
Jul 30, 2024, 01:02 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. identified Jul 30, 2024, 01:02 PM UTC

    Dear Partner, We are experiencing a technical problem, impacting about 20% of our OIDC transactions (image on WebPage not diplayed). A fix is ongoing. We apologize for any inconvenience this may cause. Best regards, Operations Team [email protected]

  2. monitoring Jul 30, 2024, 02:08 PM UTC

    Dear Partner, 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 Jul 30, 2024, 02:23 PM UTC

    Dear Partner, Monitoring showed that service has been fully restored, the incident is therefore closed. We apologize for any inconvenience this may have caused. Best regards, Operations Team [email protected]