itsmeDigitalID incident

itsme® P2 Incident

Resolved after 1 hour 20 minutes, affecting OIDC private key JWT and OIDC Client Secret and 1 more, on July 30, 2024.

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]

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

OIDC private key JWTOIDC Client SecretSOAPOASIS DSSCSCEnrollment for Belgian citizenEnrollment for International citizenProfile information management for Belgian citizenProfile information management for International citizen

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]

Your product runs on more than itsmeDigitalID

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →