itsmeDigitalID experienced a major incident on January 21, 2024 affecting Production - Identity - OIDC private key JWT and Production - Identity - OIDC private key JWT and 1 more component, lasting 2h 2m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jan 21, 2024, 08:00 AM UTC
Dear Partner, Since 02:00 APM CET, we are experiencing a technical problem, impacting between 20 and 50% of our transactions. Following services are impacted: Identity OIDC Client Secret, Sign CSC and the enrolment via eIDs. 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]
- identified Jan 21, 2024, 08:34 AM UTC
Dear Partner, Root cause has been identified. Microsoft Azure Resource Manager has a global incident impacting different Azure Regions. Our technical teams are monitoring the situation. We apologize for any inconvenience this may cause. Best regards, Operations Team [email protected]
- identified Jan 21, 2024, 08:45 AM UTC
Dear Partner, All enrolment methods are impacted. It is temporary not possible to create an itsme account. 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]
- monitoring Jan 21, 2024, 09:44 AM UTC
Dear Partner, The service has been restored. We are monitoring the situation. We apologize for any inconvenience this may have caused. Best regards, Operations Team [email protected]
- resolved Jan 21, 2024, 10:03 AM UTC
Dear Partner, The service has been restored. We apologize for any inconvenience this may have caused. Best regards, Operations Team [email protected]