Signicat Outage History

Signicat is up right now

Pingoru has recorded 183 incidents for Signicat: 183 in the last 12 months and 83 in the last 90 days.

Source: status.signicat.com

183incidents recorded
183last 12 months
83last 90 days
8 hourstypical duration
Incidents per month
02040AprMayJunJulAugSepOct28
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct16%
Pingoru began tracking Signicat in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202624172 of 720 (24%)
May 20262767 of 744 (9%)
June 20261137 of 720 (5%)
July 202623 of 744 (0%)
August 202626386 of 744 (52%)
September 202629310 of 720 (43%)
October 20262892 of 592 (16%)

Incidents, newest first

Minor June 11, 2026 Degraded performance - iDIN-itsme 1h 50m iDIN

Started Jun 11, 2026, 12:05 PM UTC· resolved Jun 11, 2026, 01:56 PM UTC

  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 →

Notice June 10, 2026 Scheduled third party maintenance - FTN-OP –

Started Jun 10, 2026, 09:00 PM UTC· resolved Jun 10, 2026, 09:00 PM UTC

  1. resolved Jun 11, 2026, 08:53 AM UTC

    Due to maintenance, OP identification methods was not available on 11 June 2026 23.15-00.00

Read the full incident report →

Minor June 10, 2026 Incident on 3rd party service - Data Verification - Source: KvK & KvK-Dataservice 24m Kamer Van Koophandel (KvK)

Started Jun 10, 2026, 08:15 AM UTC· resolved Jun 10, 2026, 08:40 AM UTC

  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 13m itsme

Started Jun 04, 2026, 02:26 PM UTC· resolved Jun 04, 2026, 02:40 PM UTC

  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 1h 32m eHerkenning

Started Jun 04, 2026, 07:35 AM UTC· resolved Jun 04, 2026, 09:08 AM UTC

  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 7h 59m Finnish Bank eIDs (FTN)

Started Jun 03, 2026, 08:00 PM UTC· resolved Jun 04, 2026, 04:00 AM UTC

  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 7m Sign API v2

Started Jun 02, 2026, 08:17 AM UTC· resolved Jun 02, 2026, 08:25 AM UTC

  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 →

Minor June 1, 2026 Incident on 3rd party service - eHerkenning 1h 23m eHerkenning

Started Jun 01, 2026, 10:27 AM UTC· resolved Jun 01, 2026, 11:51 AM UTC

  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 11h 33m Onboarding API - Signing, SignatureID QES

Started May 28, 2026, 07:12 PM UTC· resolved May 29, 2026, 06:46 AM UTC

  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 22h 18m iDIN

Started May 28, 2026, 01:30 PM UTC· resolved May 29, 2026, 11:48 AM UTC

  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 6h 37m WebID

Started May 28, 2026, 01:30 PM UTC· resolved May 28, 2026, 08:07 PM UTC

  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 2h 10m Sign API v2, Norwegian BankID

Started May 28, 2026, 01:27 PM UTC· resolved May 28, 2026, 03:37 PM UTC

  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 25, 2026 Degraded performance - Sign API v2 1h 33m Sign API v2

Started May 25, 2026, 01:45 PM UTC· resolved May 25, 2026, 03:19 PM UTC

  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 15h 45m Finnish Bank eIDs (FTN)

Started May 24, 2026, 03:40 PM UTC· resolved May 25, 2026, 07:25 AM UTC

  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 - MitID 28m MitID

Started May 21, 2026, 08:21 AM UTC· resolved May 21, 2026, 08:50 AM UTC

  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 1h 35m eHerkenning

Started May 20, 2026, 12:23 PM UTC· resolved May 20, 2026, 01:59 PM UTC

  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 3m Suomi.fi e-identification

Started May 20, 2026, 11:16 AM UTC· resolved May 20, 2026, 11:19 AM UTC

  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 23m Sign API v2

Started May 19, 2026, 01:08 PM UTC· resolved May 19, 2026, 01:31 PM UTC

  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 →

Notice May 18, 2026 Incident on 3rd party service - WebID –

Started May 18, 2026, 09:44 AM UTC· resolved May 18, 2026, 09:44 AM UTC

  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 →

Minor May 15, 2026 Degraded performance - CIAM/OwnIDP 2h 41m OwnIdP

Started May 15, 2026, 09:16 AM UTC· resolved May 15, 2026, 11:58 AM UTC

  1. investigating May 15, 2026, 09:16 AM UTC

    We are currently observing degraded performance with CIAM/OwnIDP. Incident response has been initiated and we are actively investigating the issue.

  2. monitoring May 15, 2026, 09:53 AM UTC

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

  3. resolved May 15, 2026, 11:58 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 13, 2026 Incident on 3rd party service - FTN OP Bank 1h 20m Finnish Bank eIDs (FTN)

Started May 13, 2026, 08:10 PM UTC· resolved May 13, 2026, 09:30 PM UTC

  1. monitoring May 13, 2026, 08:58 PM UTC

    An incident is currently affecting FTN OP Bank 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 May 14, 2026, 06:15 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 12, 2026 Incident on 3rd party service - eIDV-Provider: Onfido 32m eIDV Provider: Onfido

Started May 12, 2026, 12:41 PM UTC· resolved May 12, 2026, 01:13 PM UTC

  1. monitoring May 12, 2026, 12:41 PM UTC

    An incident is currently affecting Onfido for Identity Reports in UK jurisdiction. 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 May 12, 2026, 01:13 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 12, 2026 Degraded performance Signicat Platform 9m OpenID Connect, Sign API v2, Enterprise Sign API, SAML 2.0 and 5 more

Started May 12, 2026, 04:15 AM UTC· resolved May 12, 2026, 04:25 AM UTC

  1. investigating May 22, 2026, 09:15 AM UTC

    We might be experiencing issues and are currently investigating this issue.

  2. resolved May 22, 2026, 09:16 AM UTC

    This incident has been resolved.

Read the full incident report →

Major May 11, 2026 Outage - Signicat Platform outage 2h 7m ReuseID API, Portal and Portal API, Sign API v2, .beID and 28 more

Started May 11, 2026, 10:26 AM UTC· resolved May 11, 2026, 12:34 PM UTC

  1. investigating May 11, 2026, 10:26 AM UTC

    We might be experiencing issues and are currently investigating this issue.

  2. investigating May 11, 2026, 10:27 AM UTC

    We are continuing to investigate this issue.

  3. investigating May 11, 2026, 10:35 AM UTC

    We are continuing to investigate this issue.

  4. investigating May 11, 2026, 10:42 AM UTC

    We are continuing to investigate this issue.

  5. identified May 11, 2026, 10:57 AM UTC

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

  6. monitoring May 11, 2026, 11:57 AM UTC

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

  7. monitoring May 11, 2026, 12:17 PM UTC

    We are seeing an recovery to our products and services. We are monitoring additionally before resolving.

  8. resolved May 11, 2026, 12:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 7, 2026 Incident on 3rd party service - Data Verification - Source: KvK, KvK-Dataservice 4h 39m Kamer Van Koophandel (KvK)

Started May 07, 2026, 07:45 AM UTC· resolved May 07, 2026, 12:24 PM UTC

  1. monitoring May 07, 2026, 08:06 AM UTC

    An incident is currently affecting source: KvK, KvK-Dataservice for our product 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. monitoring May 07, 2026, 08:47 AM UTC

    We are continuing to monitor for any further issues.

  3. monitoring May 07, 2026, 11:12 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved May 07, 2026, 12:24 PM UTC

    This incident has been resolved.

Read the full incident report →