Signicat incident

Degraded performance - no_bankid and no_bankid_netcentric on Express sign

Minor Resolved View vendor source →

Signicat experienced a minor incident on April 21, 2026 affecting Express Signature API, lasting 1d 3h. The incident has been resolved; the full update timeline is below.

Started
Apr 21, 2026, 07:48 AM UTC
Resolved
Apr 22, 2026, 11:14 AM UTC
Duration
1d 3h
Detected by Pingoru
Apr 21, 2026, 07:48 AM UTC

Affected components

Express Signature API

Update timeline

  1. 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.

  2. investigating Apr 21, 2026, 08:59 AM UTC

    We are continuing to investigate this issue.

  3. investigating Apr 21, 2026, 10:46 AM UTC

    We are continuing to investigate this issue.

  4. investigating Apr 21, 2026, 01:16 PM UTC

    We are continuing to investigate this issue.

  5. identified Apr 21, 2026, 02:00 PM UTC

    The issue has been identified and a fix is being implemented.

  6. 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.

  7. identified Apr 22, 2026, 07:25 AM UTC

    We are continuing to work on a fix for this issue.

  8. 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

  9. resolved Apr 22, 2026, 11:14 AM UTC

    This incident has been resolved.