Degraded performance - no_bankid and no_bankid_netcentric on Express sign

Incident Report for Signicat

Resolved

This incident has been resolved.
Posted Apr 22, 2026 - 13:14 CEST

Monitoring

A fix has been implemented and we are seeing a climb in successrate. We will continue to montior
Posted Apr 22, 2026 - 12:43 CEST

Update

We are continuing to work on a fix for this issue.
Posted Apr 22, 2026 - 09:25 CEST

Update

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.
Posted Apr 21, 2026 - 19:59 CEST

Identified

The issue has been identified and a fix is being implemented.
Posted Apr 21, 2026 - 16:00 CEST

Update

We are continuing to investigate this issue.
Posted Apr 21, 2026 - 15:16 CEST

Update

We are continuing to investigate this issue.
Posted Apr 21, 2026 - 12:46 CEST

Update

We are continuing to investigate this issue.
Posted Apr 21, 2026 - 10:59 CEST

Investigating

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.
Posted Apr 21, 2026 - 09:48 CEST
This incident affected: Electronic Signing (Express Signature API).