itsmeDigitalID experienced a critical incident on December 27, 2025 affecting Production - Identity - OIDC private key JWT and Production - Identity - OIDC private key JWT and 1 more component, lasting 6h 7m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Dec 27, 2025, 04:24 PM UTC
Dear Partner, Since 5:05 PM 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]
- investigating Dec 27, 2025, 04:57 PM UTC
Dear Partner, Our technical team has found the point of failure but we need support from Azure to address / solve the issue. It is currently difficult to indicate when the problem will be resolved, we will keep you posted on progress. We apologize for any inconvenience this may cause. Best regards, Operations Team [email protected]
- investigating Dec 27, 2025, 06:01 PM UTC
Dear Partner, We are still working on the issue to get it solved and will keep you informed of our progress. We apologize for any inconvenience this may cause. Best regards, Operations Team [email protected]
- investigating Dec 27, 2025, 06:59 PM UTC
Dear Partner, We are still working with our Cloud provider to solve the issue ; we are not yet able to provide a timing to have the problem resolved. We apologize for any inconvenience this may cause. Best regards, Operations Team [email protected]
- identified Dec 27, 2025, 08:17 PM UTC
Dear Partner, Our technical team is rolling out solution; service is being progressively restored, we will keep you posted of next steps. We apologize for any inconvenience this may cause. Best regards, Operations Team [email protected]
- resolved Dec 27, 2025, 10:31 PM UTC
Dear Partner, All services are anew available excepted Qualified Electonic Signature - CSC. We apologize for any inconvenience this may have caused. Best regards, Operations Team [email protected]