Resolved -
This incident has been resolved.
Nov 27, 17:41 CET
Monitoring -
A fix has been implemented and we are monitoring the results.
Nov 27, 16:58 CET
Update -
We are seing an increase number of authentication errors when using mobile authentication.
Nov 27, 16:39 CET
Investigating -
We are observing degraded performance and an increase in errors on the authentication service. - Impact: A small percentage of users may encounter login error messages or prolonged wait times when attempting to sign in or access services that require re-authentication. - Action Required by User: We recommend retrying the login if you encounter an error.
Nov 27, 16:30 CET
Resolved -
This incident has been resolved.
Nov 26, 14:57 CET
Monitoring -
A fix has been implemented and we are monitoring the results.
Nov 26, 14:10 CET
Identified -
The issue has been identified and a fix is being implemented.
Nov 26, 12:37 CET
Investigating -
We are observing degraded performance and an increase in errors on the authentication service. - Impact: A small percentage of users may encounter login error messages or prolonged wait times when attempting to sign in or access services that require re-authentication. - Action Required by User: We recommend retrying the login if you encounter an error.
Our teams are working with the highest priority to diagnose and resolve this incident. We will provide a further update as soon as the root cause is confirmed.
Nov 26, 12:36 CET
Resolved -
The service has been fully restored and is functioning normally.
The incident was triggered by an uncontrolled restart of a critical server.
Impact: This resulted in a brief service downtime for all users, lasting approximately 1 to 2 minutes.
The high-availability mechanism automatically restored the service on a redundant node. The platform returned to a fully operational state.
Nov 25, 11:55 CET
Monitoring -
A fix has been implemented and we are monitoring the results.
Nov 25, 11:28 CET
Investigating -
We are currently experiencing a complete downtime of our platform. We are investigating the problem.
Nov 25, 11:25 CET