itsmeDigitalID incident

itsme® P1 Incident

Notice Resolved View vendor source →

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

Started
Aug 26, 2024, 07:43 AM UTC
Resolved
Aug 26, 2024, 08:22 AM UTC
Duration
38m
Detected by Pingoru
Aug 26, 2024, 07:43 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 Aug 26, 2024, 07:43 AM UTC

    Dear Partner, Since about 09:30 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 Aug 26, 2024, 08:09 AM 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]

  3. resolved Aug 26, 2024, 08:22 AM UTC

    Dear Partner, We herewith confirm that our services are back to normal since 10h00 AM. We apologize for any inconvenience this may have caused. Best regards, Operations Team [email protected]