Signicat incident
Degraded performance - no_bankid and no_bankid_netcentric on Express sign
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.
Looking to track Signicat downtime and outages?
Pingoru polls Signicat's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Signicat reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Signicat alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required