Signicat Outage History

Signicat is up right now

Signicat had 79 outages in the last 2 years totaling 103h 0m of downtime — averaging 3.2 incidents per month.

There were 79 Signicat outages since February 24, 2026 totaling 103h 0m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://signicat.statuspage.io

Minor June 11, 2026

Incident on 3rd party service - FREG

Detected by Pingoru
Jun 11, 2026, 12:17 PM UTC
Resolved
Jun 12, 2026, 06:50 AM UTC
Duration
18h 33m
Affected: Folkeregisteret
Timeline · 4 updates
  1. monitoring Jun 11, 2026, 12:17 PM UTC

    An incident is currently affecting FREG Our 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.

  2. monitoring Jun 11, 2026, 02:17 PM UTC

    We are continuing to monitor the progression towards resolution. New updates can be expected when the issue is resolved, or Friday morning.

  3. monitoring Jun 11, 2026, 03:59 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Jun 12, 2026, 06:50 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 11, 2026

Degraded performance - iDIN-itsme

Detected by Pingoru
Jun 11, 2026, 12:05 PM UTC
Resolved
Jun 11, 2026, 01:56 PM UTC
Duration
1h 50m
Affected: iDIN
Timeline · 2 updates
  1. investigating Jun 11, 2026, 12:05 PM UTC

    We are currently observing degraded performance with iDIN-itsme. Incident response has been initiated and we are actively investigating the issue and working to restore normal operations.

  2. resolved Jun 11, 2026, 01:56 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 10, 2026

Incident on 3rd party service - Norwegian BankID - Sign

Detected by Pingoru
Jun 10, 2026, 11:42 AM UTC
Resolved
Jun 10, 2026, 03:05 PM UTC
Duration
3h 23m
Affected: Norwegian BankID
Timeline · 5 updates
  1. monitoring Jun 10, 2026, 11:42 AM UTC

    An incident is currently affecting Norwegian BankID - signature. Our 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.

  2. monitoring Jun 10, 2026, 12:47 PM UTC

    We are continuing to monitor for any further issues.

  3. monitoring Jun 10, 2026, 02:18 PM UTC

    Norwegian BankID are working on a fix for this issue

  4. monitoring Jun 10, 2026, 02:43 PM UTC

    Norwegian BankID has deployed a fix and are monitoring the results.

  5. resolved Jun 10, 2026, 03:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 10, 2026

Incident on 3rd party service - Data Verification - Source: KvK & KvK-Dataservice

Detected by Pingoru
Jun 10, 2026, 08:15 AM UTC
Resolved
Jun 10, 2026, 08:40 AM UTC
Duration
24m
Affected: Kamer Van Koophandel (KvK)
Timeline · 2 updates
  1. monitoring Jun 10, 2026, 09:18 AM UTC

    An incident is currently affecting Data Verification Our 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.

  2. resolved Jun 10, 2026, 09:19 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 4, 2026

Incident on 3rd party service - itsme

Detected by Pingoru
Jun 04, 2026, 02:26 PM UTC
Resolved
Jun 04, 2026, 02:40 PM UTC
Duration
13m
Affected: itsme
Timeline · 2 updates
  1. monitoring Jun 04, 2026, 02:48 PM UTC

    An incident was affecting itsme. Our connection towards this 3rd party service was running but not functioning properly as a result of their incident. Itsme reports that their services are up and running again, with downtime approximately 16:26-16:40 UTC+2 (Amsterdam).

  2. resolved Jun 04, 2026, 02:49 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 4, 2026

Incident on 3rd party service - eHerkenning KPN and Reconi

Detected by Pingoru
Jun 04, 2026, 07:35 AM UTC
Resolved
Jun 04, 2026, 09:08 AM UTC
Duration
1h 32m
Affected: eHerkenning
Timeline · 3 updates
  1. monitoring Jun 04, 2026, 07:35 AM UTC

    An incident is currently affecting eHerkenning KPN and Reconi Our 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.

  2. monitoring Jun 04, 2026, 08:10 AM UTC

    We are continuing to monitor for any further issues. KPN successrate are improving, Reconi are still experiencing issues.

  3. resolved Jun 04, 2026, 09:08 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 3, 2026

Third party maintenance - FTN S-Bank

Detected by Pingoru
Jun 03, 2026, 08:00 PM UTC
Resolved
Jun 04, 2026, 04:00 AM UTC
Duration
7h 59m
Affected: Finnish Bank eIDs (FTN)
Timeline · 2 updates
  1. monitoring Jun 04, 2026, 06:44 AM UTC

    Our eID connection towards this 3rd party service is running but might experience issues as a result of their maintenance.

  2. resolved Jun 04, 2026, 06:45 AM UTC

    The maintenance has been completed

Read the full incident report →

Minor June 2, 2026

Degraded performance - Sign v2. - Sign-UI

Detected by Pingoru
Jun 02, 2026, 08:17 AM UTC
Resolved
Jun 02, 2026, 08:25 AM UTC
Duration
7m
Affected: Sign API v2
Timeline · 2 updates
  1. investigating Jun 02, 2026, 08:17 AM UTC

    We are currently observing degraded performance with sign-ui, affecting integrations on api.signature.com. Incident response has been initiated and we are actively investigating the issue and working to restore normal operations.

  2. resolved Jun 02, 2026, 08:25 AM UTC

    After investigating further, the issue have been identified to be a false alarm.

Read the full incident report →

Notice June 1, 2026

Third party maintenance - itsme

Detected by Pingoru
Jun 01, 2026, 08:00 PM UTC
Resolved
Jun 01, 2026, 11:00 PM UTC
Duration
2h 59m
Affected: itsme
Timeline · 2 updates
  1. investigating Jun 02, 2026, 09:19 AM UTC

    Our eID connection towards this 3rd party service is running but might experience issues as a result of their maintenance.

  2. resolved Jun 02, 2026, 09:20 AM UTC

    The maintenance has been completed

Read the full incident report →

Minor June 1, 2026

Incident on 3rd party service - eHerkenning

Detected by Pingoru
Jun 01, 2026, 10:27 AM UTC
Resolved
Jun 01, 2026, 11:51 AM UTC
Duration
1h 23m
Affected: eHerkenning
Timeline · 3 updates
  1. monitoring Jun 01, 2026, 10:27 AM UTC

    An incident is currently affecting eHerkenning. Our 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.

  2. monitoring Jun 01, 2026, 11:35 AM UTC

    We are continuing to monitor for any further issues.

  3. resolved Jun 01, 2026, 11:51 AM UTC

    This incident has been resolved.

Read the full incident report →

Major May 28, 2026

Issue with the long term QES

Detected by Pingoru
May 28, 2026, 07:12 PM UTC
Resolved
May 29, 2026, 06:46 AM UTC
Duration
11h 33m
Affected: Onboarding API - SigningSignatureID QES
Timeline · 2 updates
  1. identified May 28, 2026, 07:12 PM UTC

    We are currently experiencing an issue with signing documents using long-term Qualified Electronic Signatures (QES). This has been reported to our third-party provider, who is actively investigating. We will provide updates as soon as we have more information.

  2. resolved May 29, 2026, 06:46 AM UTC

    This incident has been resolved.

Read the full incident report →

Major May 28, 2026

Incident on 3rd party service - iDIN

Detected by Pingoru
May 28, 2026, 01:30 PM UTC
Resolved
May 29, 2026, 11:48 AM UTC
Duration
22h 18m
Affected: iDIN
Timeline · 7 updates
  1. monitoring May 28, 2026, 11:12 PM UTC

    An incident is currently affecting iDIN Our 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.

  2. monitoring May 29, 2026, 07:45 AM UTC

    We are continuing to monitor for any further issues.

  3. monitoring May 29, 2026, 07:46 AM UTC

    We are continuing to monitor for any further issues.

  4. monitoring May 29, 2026, 08:05 AM UTC

    We are continuing to monitor for any further issues.

  5. monitoring May 29, 2026, 08:57 AM UTC

    We are seing improvements in our Dashboard and api.signicat.com-endpoints. id.signicat.com and Enterprise is still affected.

  6. monitoring May 29, 2026, 11:15 AM UTC

    All platforms are operational and we are seeing completed transactions. We will monitor a bit before resolving the incident.

  7. resolved May 29, 2026, 11:48 AM UTC

    This incident has been resolved.

Read the full incident report →

Major May 28, 2026

Incident on 3rd party service - WebID VideoID

Detected by Pingoru
May 28, 2026, 01:30 PM UTC
Resolved
May 28, 2026, 08:07 PM UTC
Duration
6h 37m
Affected: WebID
Timeline · 3 updates
  1. monitoring May 28, 2026, 02:25 PM UTC

    An incident is currently affecting WebID VideoID Our 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.

  2. monitoring May 28, 2026, 08:07 PM UTC

    We are continuing to monitor for any further issues.

  3. resolved May 28, 2026, 08:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 28, 2026

Degraded performance - Norwegian BankID B2B Sign

Detected by Pingoru
May 28, 2026, 01:27 PM UTC
Resolved
May 28, 2026, 03:37 PM UTC
Duration
2h 10m
Affected: Sign API v2Norwegian BankID
Timeline · 3 updates
  1. investigating May 28, 2026, 01:27 PM UTC

    We are currently observing degraded performance with Norwegian BankID B2B Sign. Incident response has been initiated and we are actively investigating the issue and working to restore normal operations.

  2. identified May 28, 2026, 02:00 PM UTC

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

  3. resolved May 28, 2026, 03:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 28, 2026

Incident on 3rd party service - DigID

Detected by Pingoru
May 28, 2026, 08:33 AM UTC
Resolved
May 28, 2026, 09:28 AM UTC
Duration
54m
Affected: DigiD
Timeline · 4 updates
  1. monitoring May 28, 2026, 08:33 AM UTC

    An incident is currently affecting DigID Our 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.

  2. monitoring May 28, 2026, 08:36 AM UTC

    We are continuing to monitor for any further issues.

  3. monitoring May 28, 2026, 08:38 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved May 28, 2026, 09:28 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 25, 2026

Degraded performance - Sign API v2

Detected by Pingoru
May 25, 2026, 01:45 PM UTC
Resolved
May 25, 2026, 03:19 PM UTC
Duration
1h 33m
Affected: Sign API v2
Timeline · 4 updates
  1. investigating May 25, 2026, 03:18 PM UTC

    We are currently observing degraded performance with Sign API v2, affecting integrations on api.signicat.com endpoints. Incident response has been initiated and we are actively investigating the issue and working to restore normal operations.

  2. identified May 25, 2026, 03:18 PM UTC

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

  3. monitoring May 25, 2026, 03:18 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved May 25, 2026, 03:19 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 24, 2026

Incident on 3rd party service - FTN affecting Saastopankki

Detected by Pingoru
May 24, 2026, 03:40 PM UTC
Resolved
May 25, 2026, 07:25 AM UTC
Duration
15h 45m
Affected: Finnish Bank eIDs (FTN)
Timeline · 3 updates
  1. monitoring May 24, 2026, 03:40 PM UTC

    An incident is currently affecting FTN - Saastopankki Our 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.

  2. monitoring May 25, 2026, 07:08 AM UTC

    We are continuing to monitor for any further issues.

  3. resolved May 25, 2026, 07:25 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 21, 2026

Incident on 3rd party service - Norwegian BankID

Detected by Pingoru
May 21, 2026, 09:37 AM UTC
Resolved
May 21, 2026, 10:16 AM UTC
Duration
39m
Affected: Norwegian BankID
Timeline · 3 updates
  1. monitoring May 21, 2026, 09:37 AM UTC

    An incident is currently affecting Norwegian BankID Our 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.

  2. monitoring May 21, 2026, 09:58 AM UTC

    We are continuing to monitor the situation. Please note that this only affects signing.

  3. resolved May 21, 2026, 10:16 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 21, 2026

Incident on 3rd party service - MitID

Detected by Pingoru
May 21, 2026, 08:21 AM UTC
Resolved
May 21, 2026, 08:50 AM UTC
Duration
28m
Affected: MitID
Timeline · 3 updates
  1. monitoring May 21, 2026, 08:35 AM UTC

    An incident is currently affecting MitID Our 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.

  2. monitoring May 21, 2026, 08:37 AM UTC

    We are continuing to monitor for any further issues.

  3. resolved May 21, 2026, 08:52 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 20, 2026

Third party maintenance - eHerkenning - KPN

Detected by Pingoru
May 20, 2026, 12:23 PM UTC
Resolved
May 20, 2026, 01:59 PM UTC
Duration
1h 35m
Affected: eHerkenning
Timeline · 3 updates
  1. monitoring May 20, 2026, 12:47 PM UTC

    Our eID connection towards this 3rd party service is running but might experience issues as a result of their maintenance.

  2. monitoring May 20, 2026, 01:47 PM UTC

    We are seeing normalized success rates. The product is fully operational again. Signicat will continue to monitor before resolving.

  3. resolved May 20, 2026, 01:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 20, 2026

Degraded performance - Suomi.fi e-identification

Detected by Pingoru
May 20, 2026, 11:16 AM UTC
Resolved
May 20, 2026, 11:19 AM UTC
Duration
3m
Affected: Suomi.fi e-identification
Timeline · 2 updates
  1. identified May 20, 2026, 11:16 AM UTC

    We are currently observing degraded performance with Suomi.fi e-identification. Incident response has been initiated and we are actively investigating the issue and working to restore normal operations.

  2. resolved May 20, 2026, 11:19 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 19, 2026

Degraded performance - Sign API V2

Detected by Pingoru
May 19, 2026, 01:08 PM UTC
Resolved
May 19, 2026, 01:31 PM UTC
Duration
23m
Affected: Sign API v2
Timeline · 4 updates
  1. investigating May 19, 2026, 01:08 PM UTC

    We are currently observing degraded performance with Sign API V2, affecting integrations on https://api.signicat.com/sign/ endpoints. Incident response has been initiated and we are actively investigating the issue and working to restore normal operations.

  2. identified May 19, 2026, 01:11 PM UTC

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

  3. monitoring May 19, 2026, 01:18 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved May 19, 2026, 01:31 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 19, 2026

Incident on 3rd party service - DigiD

Detected by Pingoru
May 19, 2026, 09:50 AM UTC
Resolved
May 19, 2026, 10:18 AM UTC
Duration
27m
Affected: DigiDDigiD CombiConnect
Timeline · 3 updates
  1. monitoring May 19, 2026, 09:50 AM UTC

    An incident is currently affecting DigiD Our 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.

  2. monitoring May 19, 2026, 10:11 AM UTC

    The success rate is improving, and we will continue to monitor.

  3. resolved May 19, 2026, 10:18 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 18, 2026

Incident on 3rd party service - WebID

Detected by Pingoru
May 18, 2026, 10:16 AM UTC
Resolved
May 18, 2026, 09:44 AM UTC
Duration
—
Timeline · 1 update
  1. resolved May 18, 2026, 10:16 AM UTC

    An incident affected WebID Our connection towards this 3rd party service was affected. Window: 11:44 CEST - 12:11 CEST

Read the full incident report →