Our eID connection towards this 3rd party service is running but might experience issues as a result of their maintenance.
Upcoming scheduled maintenance notice for BankID App: One of our vendors will be performing a scheduled maintenance activity. During this maintenance window, users may experience brief interruptions in activation and authentication when using the app. Posted on
Jan 08, 2026 - 10:50 CET
Resolved -
This incident has been resolved.
Jan 15, 14:10 CET
Update -
OP has confirmed that they are currently experiencing technical issues. We will continue to monitor their progress towards a resolution.
Jan 15, 12:53 CET
Update -
We are seeing an increased successrate and are continuing to monitor the situation.
Jan 15, 11:11 CET
Monitoring -
We are continuing to monitor their progression towards a resolution.
Jan 15, 10:09 CET
Identified -
Our eID connection towards this 3rd party service is running but is not functioning properly as a result of their incident.
We are monitoring their progression towards resolution.
Jan 15, 09:30 CET
Completed -
The scheduled maintenance has been completed.
Jan 15, 02:00 CET
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 15, 00:00 CET
Scheduled -
Delivery platform: OpenID connect will have a maintenance. There will be a down time of approximate 30 minutes during the maintenance activity.
Completed -
The scheduled maintenance has been completed.
Jan 5, 23:00 CET
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 5, 22:00 CET
Scheduled -
Assure Databases need to perform maintenance, and we expect some degraded performance during this time. We do not expect it take long, but service window is kept open for one hour, in case needed.
Jan 5, 12:32 CET
Resolved -
This incident has been resolved.
Jan 2, 15:57 CET
Monitoring -
A fix has been implemented and we are monitoring the results.
Jan 2, 15:29 CET
Update -
We are continuing to work on a fix for this issue.
Jan 2, 14:59 CET
Identified -
The issue has been identified and a fix is being implemented.
Jan 2, 13:37 CET
Investigating -
We are currently observing degraded performance with Itsme QES sign, affecting integrations on id.signicat.com endpoints. Incident response has been initiated and we are actively investigating the issue and working to restore normal operations.
Jan 2, 13:12 CET
Resolved -
This incident has been resolved.
Jan 1, 15:14 CET
Monitoring -
A fix has been implemented and we are monitoring the results.
Jan 1, 14:43 CET
Identified -
The issue has been identified and a fix is being implemented.
Jan 1, 14:31 CET
Update -
We are continuing to investigate this issue.
Jan 1, 14:13 CET
Investigating -
We are currently observing degraded performance with Sign, affecting integrations on api.signicat.com, id.signicat.com and express.signicat.com endpoints. Incident response has been initiated and we are actively investigating the issue and working to restore normal operations.
Jan 1, 14:05 CET
Resolved -
This incident has been resolved.
Jan 1, 15:13 CET
Monitoring -
A fix has been implemented and we are monitoring the results.
Jan 1, 14:43 CET
Identified -
The issue has been identified and a fix is being implemented.
Jan 1, 14:31 CET
Update -
We are continuing to investigate this issue.
Jan 1, 14:00 CET
Update -
We are continuing to investigate this issue.
Jan 1, 13:33 CET
Investigating -
We are currently observing degraded performance with FTN and MitID, affecting integrations on api.signicat and id.signicat endpoints. Incident response has been initiated and we are actively investigating the issue and working to restore normal operations.
Jan 1, 13:09 CET
Resolved -
This incident has been resolved.
Jan 1, 14:40 CET
Monitoring -
A fix has been implemented and we are monitoring the results.
Jan 1, 13:40 CET
Investigating -
We are currently observing degraded performance with Sign- Qualified Timestamps (QTSA), affecting integrations on Enterprise, api.signicat.com and dokobit.signicat.com endpoints. Incident response has been initiated and we are actively investigating the issue and working to restore normal operations.
Jan 1, 11:33 CET