Signicat incident
Degraded performance - no_bankid and no_bankid_netcentric on Express sign
Resolved after 1 day 3 hours, affecting Express Signature API, on April 21, 2026.
A fix has been implemented and we are seeing a climb in successrate. We will continue to montior
Affected components
Update timeline
- investigating Apr 21, 2026, 07:48 AM UTC
We are currently observing degraded performance with no_bankid and no_bankid_netcentric on Express sign, affecting integrations on api.signicat.com and signicat.io endpoints. Incident response has been initiated and we are actively investigating the issue and working to restore normal operations.
- investigating Apr 21, 2026, 08:59 AM UTC
We are continuing to investigate this issue.
- investigating Apr 21, 2026, 10:46 AM UTC
We are continuing to investigate this issue.
- investigating Apr 21, 2026, 01:16 PM UTC
We are continuing to investigate this issue.
- identified Apr 21, 2026, 02:00 PM UTC
The issue has been identified and a fix is being implemented.
- identified Apr 21, 2026, 05:59 PM UTC
We expect a fix for this issue to be ready tomorrow (22.04.2026) We will come back with an update at 09:00 CEST.
- identified Apr 22, 2026, 07:25 AM UTC
We are continuing to work on a fix for this issue.
- monitoring Apr 22, 2026, 10:43 AM UTC
A fix has been implemented and we are seeing a climb in successrate. We will continue to montior
- resolved Apr 22, 2026, 11:14 AM UTC
This incident has been resolved.
Your product runs on more than Signicat
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services