Signicat Outage History

Signicat is up right now

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

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

Source: https://signicat.statuspage.io

Minor May 15, 2026

Degraded performance - CIAM/OwnIDP

Detected by Pingoru
May 15, 2026, 09:16 AM UTC
Resolved
May 15, 2026, 11:58 AM UTC
Duration
2h 41m
Affected: OwnIdP
Timeline · 3 updates
  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

Detected by Pingoru
May 13, 2026, 08:10 PM UTC
Resolved
May 13, 2026, 09:30 PM UTC
Duration
1h 20m
Affected: Finnish Bank eIDs (FTN)
Timeline · 2 updates
  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

Detected by Pingoru
May 12, 2026, 12:41 PM UTC
Resolved
May 12, 2026, 01:13 PM UTC
Duration
32m
Affected: eIDV Provider: Onfido
Timeline · 2 updates
  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

Detected by Pingoru
May 12, 2026, 04:15 AM UTC
Resolved
May 12, 2026, 04:25 AM UTC
Duration
9m
Affected: OpenID ConnectSign API v2Enterprise Sign APISAML 2.0Express Signature APIAuthentication APIAssure APIMobileIDSignicat dashboard
Timeline · 2 updates
  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

Detected by Pingoru
May 11, 2026, 10:26 AM UTC
Resolved
May 11, 2026, 12:34 PM UTC
Duration
2h 7m
Affected: ReuseID APIPortal and Portal APISign API v2.beIDBuypassExpress Signature APIIdentity GatewayDigiDDigiD CombiConnecteHerkenningAssure APIEmail OTPEstonian ID CardFinnish Bank eIDs (FTN)Freja eIDSignicat Identity BrokeriDINitsmeOwnIdPMitIDMy SignicatSignicat dashboardMobileID (OIDC)mojeIDNorwegian BankIDPersonalausweisSamleikinSmart-IDSMS OTPSPIDSwedish BankIDSuomi.fi e-identification
Timeline · 8 updates
  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

Detected by Pingoru
May 07, 2026, 07:45 AM UTC
Resolved
May 07, 2026, 12:24 PM UTC
Duration
4h 39m
Affected: Kamer Van Koophandel (KvK)
Timeline · 4 updates
  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 →

Minor May 6, 2026

Incident on 3rd party service - Telia LT Mobile-ID

Detected by Pingoru
May 06, 2026, 03:53 PM UTC
Resolved
May 06, 2026, 05:15 PM UTC
Duration
1h 22m
Affected: SK Mobile-ID
Timeline · 2 updates
  1. monitoring May 07, 2026, 08:50 AM UTC

    The electronic use of Telia LT Mobile-ID was interrupted from 06.05.2026 18:53 to 06.05.2026 20:10. This may have caused problems using Telia LT Mobile-ID log-in to Internet banks and other e-services and digital signing.

  2. resolved May 07, 2026, 08:51 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 5, 2026

Degraded performance - Sign API v2 on mobile devices

Detected by Pingoru
May 05, 2026, 12:27 PM UTC
Resolved
May 05, 2026, 07:04 PM UTC
Duration
6h 37m
Affected: Sign API v2
Timeline · 6 updates
  1. investigating May 05, 2026, 12:27 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. investigating May 05, 2026, 01:22 PM UTC

    We are continuing to investigate this issue.

  3. identified May 05, 2026, 02:16 PM UTC

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

  4. identified May 05, 2026, 06:17 PM UTC

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

  5. monitoring May 05, 2026, 07:02 PM UTC

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

  6. resolved May 05, 2026, 07:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 4, 2026

Incident on 3rd party service - Freja eID

Detected by Pingoru
May 04, 2026, 09:00 AM UTC
Resolved
May 04, 2026, 09:26 AM UTC
Duration
26m
Affected: Freja eID
Timeline · 3 updates
  1. monitoring May 04, 2026, 09:10 AM UTC

    An incident is currently affecting Freja eID Our eID 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 04, 2026, 09:12 AM UTC

    Issue seem to be resolving, and we will continue to monitor the issue.

  3. resolved May 04, 2026, 09:26 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 30, 2026

Incident on 3rd party service - FTN- Op bank

Detected by Pingoru
Apr 30, 2026, 07:46 AM UTC
Resolved
Apr 30, 2026, 08:02 AM UTC
Duration
16m
Affected: Finnish Bank eIDs (FTN)
Timeline · 2 updates
  1. monitoring Apr 30, 2026, 07:54 AM UTC

    An incident is currently affecting FTN- Op Our eID 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 Apr 30, 2026, 01:19 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 26, 2026

Degraded performance - Digital Trust Platform

Detected by Pingoru
Apr 26, 2026, 11:40 AM UTC
Resolved
Apr 26, 2026, 01:09 PM UTC
Duration
1h 29m
Affected: eIDV Provider: Signicat PaperBankID AMLOnboarding API - eIDVOpenID ConnectDSF NorwayReuseID APIPortal and Portal APISign API v2Audkenni App.beIDEnterprise Sign APIeIDV Provider: OnfidoBrønnøysundOnboarding API - eID HubSAML 2.0DVV FinlandAssure APIUniversal APIBuypassExpress Signature APIeIDV Provider: ReadIDFolkeregisteretOnboarding API - SigningAuthentication APISPAR SwedeneIDV Provider: Signicat VideoIDDocuments GatewayInfotorgQualified Timestamps (QTSA)TrapetsMobileIDCzech Bank iDIdentity GatewayeIDV Provider: FaceTecDigiDDocumentServiceKamer Van Koophandel (KvK)PictureIDDocuments APIPasskeysPackagingServiceVideoIDSurePayDigiD CombiConnectIdentity APIData VerificationArchiveServiceeHerkenningSmileIDAssure APICreditsafeeParakstsEmail OTPWebIDDun & Bradstreet (formerly Bisnode)Estonian ID CardOpenRegisters (Kausate)SignatureID AESFinnish Bank eIDs (FTN)MobileIDSignatureID QESFreja eIDDigital Evidence ManagementSignicat Identity BrokerID-PorteniDINitsmeOwnIdPMitIDMy SignicatSignicat dashboardMobileID (OIDC)mojeIDNorwegian BankIDPersonalausweisSamleikinSithsSK Mobile-IDSmart-IDSMS OTPSPIDSwedish BankIDSuomi.fi e-identification
Timeline · 6 updates
  1. investigating Apr 26, 2026, 11:51 AM UTC

    We are currently observing degraded performance from our provider Google Cloud, possibly affecting services on DTP. Incident response has been initiated and we are working on determining if there is any impact.

  2. investigating Apr 26, 2026, 11:54 AM UTC

    We are continuing to investigate this issue.

  3. investigating Apr 26, 2026, 11:57 AM UTC

    We are continuing to investigate this issue.

  4. investigating Apr 26, 2026, 12:24 PM UTC

    We are seeing issues with several services. We are in touch with Google support, and they are investigating on their side.

  5. monitoring Apr 26, 2026, 12:49 PM UTC

    We see improvement and services are restored. We will continue monitoring to see if systems are stable.

  6. resolved Apr 26, 2026, 01:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 24, 2026

Incident on 3rd party service - Norwegian BankID CSC Signing

Detected by Pingoru
Apr 24, 2026, 06:31 PM UTC
Resolved
Apr 25, 2026, 10:29 AM UTC
Duration
15h 57m
Affected: Sign API v2Enterprise Sign APIExpress Signature API
Timeline · 2 updates
  1. monitoring Apr 24, 2026, 06:31 PM UTC

    An incident is currently affecting Norwegian BankID CSC Signing Our eID 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 Apr 25, 2026, 10:29 AM UTC

    This incident has been resolved.

Read the full incident report →

Major April 24, 2026

Partial outage - Data verification - DK-CPR

Detected by Pingoru
Apr 24, 2026, 11:56 AM UTC
Resolved
Apr 27, 2026, 11:46 AM UTC
Duration
2d 23h
Affected: Data Verification
Timeline · 7 updates
  1. investigating Apr 24, 2026, 11:56 AM UTC

    We are currently observing degraded performance with Data Verification data-source DK-CPR, 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. investigating Apr 24, 2026, 12:31 PM UTC

    We are continuing to investigate this issue.

  3. investigating Apr 24, 2026, 01:20 PM UTC

    We are continuing to investigate this issue in cooperation with the technicians at CPR.

  4. investigating Apr 25, 2026, 10:14 AM UTC

    Incident with source DK-CPR is not expected to be resolved until Monday 27th of April, due to lack of available support with the third party DK-CPR provider during the weekend.

  5. investigating Apr 27, 2026, 09:31 AM UTC

    Incident with source DK-CPR is still ongoing. DK-CPR technicians are working on resolving the issue as quickly as possible.

  6. monitoring Apr 27, 2026, 11:02 AM UTC

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

  7. resolved Apr 27, 2026, 11:46 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 24, 2026

Degraded perfomance - Dokobit Portal

Detected by Pingoru
Apr 24, 2026, 10:29 AM UTC
Resolved
Apr 24, 2026, 10:55 AM UTC
Duration
26m
Affected: Portal and Portal API
Timeline · 3 updates
  1. investigating Apr 24, 2026, 10:29 AM UTC

    We are currently experiencing issues with the Dokobit Portal and are working on a fix.

  2. monitoring Apr 24, 2026, 10:41 AM UTC

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

  3. resolved Apr 24, 2026, 10:55 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 22, 2026

Incident on 3rd party service - Onfido

Detected by Pingoru
Apr 22, 2026, 03:43 PM UTC
Resolved
Apr 22, 2026, 04:16 PM UTC
Duration
32m
Affected: eIDV Provider: Onfido
Timeline · 3 updates
  1. monitoring Apr 22, 2026, 04:14 PM UTC

    An incident is currently affecting Onfido Our eID 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 Apr 22, 2026, 04:16 PM UTC

    The situation seems to have improved. We will continue to monitor for any further issues.

  3. resolved Apr 22, 2026, 04:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 16, 2026

Incident on 3rd party service - FTN Danskebank

Detected by Pingoru
Apr 16, 2026, 01:59 PM UTC
Resolved
Apr 16, 2026, 03:26 PM UTC
Duration
1h 27m
Affected: Finnish Bank eIDs (FTN)
Timeline · 2 updates
  1. monitoring Apr 16, 2026, 01:59 PM UTC

    An incident is currently affecting FTN Danskebank Our eID 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 Apr 16, 2026, 03:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical April 15, 2026

Service disruption affecting Sign API v2

Detected by Pingoru
Apr 15, 2026, 03:25 PM UTC
Resolved
Apr 15, 2026, 05:29 PM UTC
Duration
2h 3m
Affected: Sign API v2
Timeline · 4 updates
  1. investigating Apr 15, 2026, 03:25 PM UTC

    We are currently observing a service disruption with Sign API v2. Incident response has been initiated and we are actively investigating the issue and working to restore normal operations.

  2. investigating Apr 15, 2026, 04:24 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Apr 15, 2026, 04:55 PM UTC

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

  4. resolved Apr 15, 2026, 05:29 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 15, 2026

Incident on 3rd party service - Data Verification source: Creditsafe

Detected by Pingoru
Apr 15, 2026, 09:40 AM UTC
Resolved
Apr 15, 2026, 10:20 AM UTC
Duration
39m
Affected: Creditsafe
Timeline · 2 updates
  1. monitoring Apr 15, 2026, 09:40 AM UTC

    An incident is currently affecting Data Verification source: Creditsafe 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 Apr 15, 2026, 10:20 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 13, 2026

Degraded performance - Data Verification source: Creditsafe

Detected by Pingoru
Apr 13, 2026, 01:02 PM UTC
Resolved
Apr 14, 2026, 08:07 AM UTC
Duration
19h 5m
Affected: Creditsafe
Timeline · 6 updates
  1. investigating Apr 13, 2026, 01:02 PM UTC

    We are currently observing degraded performance with Data Verification - Creditsafe, 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. monitoring Apr 13, 2026, 01:27 PM UTC

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

  3. monitoring Apr 13, 2026, 01:54 PM UTC

    We are continuing to monitor for any further issues.

  4. identified Apr 13, 2026, 04:43 PM UTC

    Parts of our source with Creditsafe is working, but service has not yet been fully restored. We have identified the issue and is working towards an resolution.

  5. identified Apr 14, 2026, 07:53 AM UTC

    Parts of our source with Creditsafe is working, but service has not yet been fully restored. We have identified the issue and is working towards an resolution.

  6. resolved Apr 14, 2026, 08:07 AM UTC

    The incident has been resolved.

Read the full incident report →

Minor April 13, 2026

Incident on 3rd party service - eHerkenning - KPN and Reconi

Detected by Pingoru
Apr 13, 2026, 10:28 AM UTC
Resolved
Apr 13, 2026, 01:34 PM UTC
Duration
3h 5m
Affected: eHerkenning
Timeline · 4 updates
  1. monitoring Apr 13, 2026, 10:28 AM UTC

    An incident is currently affecting eHerkenning Our eID 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 Apr 13, 2026, 11:45 AM UTC

    We are continuing to monitor for any further issues.

  3. monitoring Apr 13, 2026, 01:00 PM UTC

    We are seeing the method having recovered. We will continue to monitor for a bit before resolving.

  4. resolved Apr 13, 2026, 01:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 11, 2026

Maintenance on 3rd party service - FTN OP

Detected by Pingoru
Apr 11, 2026, 09:25 PM UTC
Resolved
Apr 12, 2026, 09:20 AM UTC
Duration
11h 54m
Affected: Finnish Bank eIDs (FTN)
Timeline · 2 updates
  1. monitoring Apr 11, 2026, 09:25 PM UTC

    An incident is currently affecting FTN OP Our eID 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 Apr 12, 2026, 09:20 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 9, 2026

Degraded performance - MitID Private for Business

Detected by Pingoru
Apr 09, 2026, 10:01 PM UTC
Resolved
Apr 10, 2026, 02:27 PM UTC
Duration
16h 25m
Affected: MitID
Timeline · 2 updates
  1. investigating Apr 10, 2026, 03:04 PM UTC

    We are currently observing degraded performance with MitID Private for Business, affecting integrations on id.signciat.com and api.signicat.com endpoints. Incident response has been initiated and we are actively investigating the issue and working to restore normal operations.

  2. resolved Apr 10, 2026, 03:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 5, 2026

Incident on 3rd party service - DigiD and DigiD app

Detected by Pingoru
Apr 05, 2026, 03:17 PM UTC
Resolved
Apr 05, 2026, 04:51 PM UTC
Duration
1h 33m
Affected: DigiDDigiD CombiConnect
Timeline · 2 updates
  1. monitoring Apr 05, 2026, 03:17 PM UTC

    An incident is currently affecting DigiD and DigiD app. Our eID 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 Apr 05, 2026, 04:51 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 3, 2026

Incident on 3rd party service - eHerkenningen - KPN and Reconi

Detected by Pingoru
Apr 03, 2026, 08:21 AM UTC
Resolved
Apr 03, 2026, 10:22 AM UTC
Duration
2h 1m
Affected: eHerkenning
Timeline · 4 updates
  1. monitoring Apr 03, 2026, 08:21 AM UTC

    An incident is currently affecting eHerkenningen Our eID 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 Apr 03, 2026, 09:49 AM UTC

    We are continuing to monitor for any further issues.

  3. monitoring Apr 03, 2026, 10:04 AM UTC

    We are seeing a return to Operational status. We will continue to monitor to ensure stability.

  4. resolved Apr 03, 2026, 10:22 AM UTC

    This incident has been resolved.

Read the full incident report →