Signicat Outage History

Signicat is up right now

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

Source: https://signicat.statuspage.io

Minor March 30, 2026

Issue with connectivity to KvK provider

Detected by Pingoru
Mar 30, 2026, 07:03 PM UTC
Resolved
Mar 31, 2026, 09:02 AM UTC
Duration
13h 59m
Affected: Kamer Van Koophandel (KvK)
Timeline · 4 updates
  1. identified Mar 30, 2026, 07:03 PM UTC

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

  2. investigating Mar 30, 2026, 07:05 PM UTC

    We are currently investigating this issue.

  3. monitoring Mar 31, 2026, 07:55 AM UTC

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

  4. resolved Mar 31, 2026, 09:02 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 26, 2026

Degraded performance - Document Service - Document management affected

Detected by Pingoru
Mar 26, 2026, 12:18 PM UTC
Resolved
Mar 27, 2026, 12:29 PM UTC
Duration
1d
Affected: DocumentService
Timeline · 5 updates
  1. investigating Mar 26, 2026, 12:18 PM UTC

    We are currently observing degraded performance with Document Service, affecting integrations on id.signicat.com endpoints. Incident response has been initiated and we are actively investigating the issue and working to restore normal operations. Degraded performance for Documents (Legacy service) for a limited number of customers. Signing is working but management of these are affected.

  2. identified Mar 26, 2026, 12:50 PM UTC

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

  3. identified Mar 26, 2026, 05:09 PM UTC

    We are continuing to work on a fix for this issue. We expect to have a new update tomorrow at 09:00 CET.

  4. identified Mar 27, 2026, 08:00 AM UTC

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

  5. resolved Mar 27, 2026, 12:29 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical March 23, 2026

Service Disruption

Detected by Pingoru
Mar 23, 2026, 11:47 AM UTC
Resolved
Mar 23, 2026, 02:56 PM UTC
Duration
3h 8m
Affected: OpenID ConnectSign API v2.beIDAssure APIBuypassExpress Signature APIAuthentication APIDigiDDigiD CombiConnecteHerkenningAssure APIEmail OTPEstonian ID CardFinnish Bank eIDs (FTN)Freja eIDSignicat Identity BrokeriDINitsmeMitIDSignicat dashboardMobileID (OIDC)mojeIDExpress Authentication APINorwegian BankIDPersonalausweisSamleikinSmart-IDSMS OTPSPIDSwedish BankIDSuomi.fi e-identification
Timeline · 6 updates
  1. investigating Mar 23, 2026, 11:47 AM UTC

    We are currently investigating an issue affecting several components, see list of components affected.

  2. identified Mar 23, 2026, 12:02 PM UTC

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

  3. monitoring Mar 23, 2026, 12:20 PM UTC

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

  4. monitoring Mar 23, 2026, 12:31 PM UTC

    We see significant improvement after the fix was implemented. We will continue investigating the issue and monitor the situation closely.

  5. monitoring Mar 23, 2026, 02:36 PM UTC

    Our services are operational, but we are continuing to monitor closely.

  6. resolved Mar 23, 2026, 02:56 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 18, 2026

Investgating Degraded performance - iDIN on id.signicat.com

Detected by Pingoru
Mar 18, 2026, 07:13 AM UTC
Resolved
Mar 18, 2026, 08:40 AM UTC
Duration
1h 26m
Affected: iDIN
Timeline · 4 updates
  1. investigating Mar 18, 2026, 07:13 AM UTC

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

  2. investigating Mar 18, 2026, 07:59 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Mar 18, 2026, 08:15 AM UTC

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

  4. resolved Mar 18, 2026, 10:14 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 17, 2026

Identity Broker operational

Detected by Pingoru
Mar 17, 2026, 05:43 PM UTC
Resolved
Mar 17, 2026, 05:43 PM UTC
Duration
Affected: Signicat Identity Broker
Timeline · 1 update
  1. resolved Mar 17, 2026, 05:43 PM UTC

    Operational since approx. 3:30 PM UTC.

Read the full incident report →

Critical March 17, 2026

Service Disruption - Multiple methods

Detected by Pingoru
Mar 17, 2026, 02:03 PM UTC
Resolved
Mar 17, 2026, 04:17 PM UTC
Duration
2h 13m
Affected: Portal and Portal API.beIDBuypassExpress Signature APIDigiDeHerkenningAssure APIEmail OTPEstonian ID CardFinnish Bank eIDs (FTN)Freja eIDiDINitsmeOwnIdPMitIDMy SignicatSignicat dashboardMobileID (OIDC)mojeIDNorwegian BankIDPersonalausweisSamleikinSmart-IDSMS OTPSPIDSwedish BankIDSuomi.fi e-identification
Timeline · 8 updates
  1. investigating Mar 17, 2026, 02:03 PM UTC

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

  2. investigating Mar 17, 2026, 02:28 PM UTC

    We are continuing to investigate the ongoing incident. Signicat is treating this as an all-hands on deck situation, and we are giving it our highest priorities and resources.

  3. investigating Mar 17, 2026, 02:53 PM UTC

    We are continuing to investigate this issue.

  4. investigating Mar 17, 2026, 03:12 PM UTC

    We are continuing to investigate this issue.

  5. investigating Mar 17, 2026, 03:20 PM UTC

    We are continuing to investigate this issue. Work is ongoing to resolve issues, and we are seeing signs of improvement.

  6. investigating Mar 17, 2026, 03:30 PM UTC

    We have implemented a fix and see significant improvement. We will continue investigating the issue and monitor the situation closely.

  7. monitoring Mar 17, 2026, 03:48 PM UTC

    Our services are operational, but we are continuing to monitor closely.

  8. resolved Mar 17, 2026, 04:17 PM UTC

    This incident is resolved. We are working with our providers to find the exact cause. We are also working on another mitigation on our side, in the event this issue appears again.

Read the full incident report →

Major March 17, 2026

Degraded performance

Detected by Pingoru
Mar 17, 2026, 12:07 PM UTC
Resolved
Mar 17, 2026, 12:44 PM UTC
Duration
37m
Affected: .beIDBuypassExpress Signature APIDigiDeHerkenningAssure APIEmail OTPEstonian ID CardFinnish Bank eIDs (FTN)Freja eIDSignicat Identity BrokeriDINitsmeOwnIdPMitIDMy SignicatSignicat dashboardMobileID (OIDC)mojeIDNorwegian BankIDPersonalausweisSamleikinSmart-IDSMS OTPSPIDSwedish BankIDSuomi.fi e-identification
Timeline · 3 updates
  1. investigating Mar 17, 2026, 12:07 PM UTC

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

  2. monitoring Mar 17, 2026, 12:27 PM UTC

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

  3. resolved Mar 17, 2026, 12:44 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 17, 2026

Degraded performance - Multiple methods

Detected by Pingoru
Mar 17, 2026, 07:20 AM UTC
Resolved
Mar 17, 2026, 07:25 AM UTC
Duration
5m
Affected: .beIDBuypassExpress Signature APIDigiDeHerkenningAssure APIEmail OTPEstonian ID CardFinnish Bank eIDs (FTN)Freja eIDSignicat Identity BrokeriDINitsmeOwnIdPMitIDMy SignicatSignicat dashboardMobileID (OIDC)mojeIDNorwegian BankIDPersonalausweisSamleikinSmart-IDSMS OTPSPIDSwedish BankIDSuomi.fi e-identification
Timeline · 4 updates
  1. investigating Mar 17, 2026, 08:00 AM UTC

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

  2. identified Mar 17, 2026, 08:00 AM UTC

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

  3. monitoring Mar 17, 2026, 08:00 AM UTC

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

  4. resolved Mar 17, 2026, 08:00 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 16, 2026

Incident on 3rd party service Swedish BankID

Detected by Pingoru
Mar 16, 2026, 01:46 AM UTC
Resolved
Mar 16, 2026, 01:52 AM UTC
Duration
5m
Affected: Swedish BankID
Timeline · 3 updates
  1. investigating Mar 16, 2026, 07:45 AM UTC

    We are currently investigating this issue.

  2. identified Mar 16, 2026, 07:45 AM UTC

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

  3. resolved Mar 16, 2026, 07:46 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 13, 2026

Incident on 3rd party service - FTN S-pankki

Detected by Pingoru
Mar 13, 2026, 01:58 PM UTC
Resolved
Mar 13, 2026, 06:09 PM UTC
Duration
4h 10m
Affected: Finnish Bank eIDs (FTN)
Timeline · 3 updates
  1. monitoring Mar 13, 2026, 01:58 PM UTC

    An incident is currently affecting FTN S-pankki 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 Mar 13, 2026, 03:03 PM UTC

    We are continuing to monitor for any further issues.

  3. resolved Mar 13, 2026, 08:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 12, 2026

Incident on 3rd party service - BankID AML API

Detected by Pingoru
Mar 12, 2026, 10:53 AM UTC
Resolved
Mar 12, 2026, 12:50 PM UTC
Duration
1h 57m
Affected: BankID AML
Timeline · 2 updates
  1. monitoring Mar 12, 2026, 01:14 PM UTC

    An incident is currently affecting BankID AML API 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 Mar 12, 2026, 01:14 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 12, 2026

Incident on 3rd party service - Norwegian BankID and ID-Porten

Detected by Pingoru
Mar 12, 2026, 09:28 AM UTC
Resolved
Mar 12, 2026, 10:56 AM UTC
Duration
1h 28m
Affected: ID-PortenNorwegian BankID
Timeline · 4 updates
  1. monitoring Mar 12, 2026, 09:28 AM UTC

    An incident is currently affecting Norwegian BankID and ID-porten 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 Mar 12, 2026, 09:55 AM UTC

    Norwegian BankID is experiencing issues with BankID App authentications. Users are unable to authenticate when selecting the BankID app as their login method. Please note that authentication using kodebrikke (code device) is functioning normally. Their team has identified the issue and is working on restoring functionality for BankID App users. We will continue to monitor their progression towards resolution.

  3. monitoring Mar 12, 2026, 10:30 AM UTC

    A fix has been implemented by Norwegian BankID and we see an increase in successful transactions from 10:49 CET. We are continuing to monitor for any further issues.

  4. resolved Mar 12, 2026, 10:56 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 11, 2026

Degraded performance - Dokobit Portal - AWS

Detected by Pingoru
Mar 11, 2026, 09:00 AM UTC
Resolved
Mar 11, 2026, 02:50 PM UTC
Duration
5h 49m
Affected: Portal and Portal APIUniversal API
Timeline · 4 updates
  1. investigating Mar 11, 2026, 02:42 PM UTC

    We have observing degraded performance with Dokobit Portal, affecting integrations with PDF template crate/edit, PDF template fill and SignicatID onboarding process. Incident response has been initiated and we are actively investigating the issue and working to restore normal operations.

  2. identified Mar 11, 2026, 02:44 PM UTC

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

  3. monitoring Mar 11, 2026, 02:44 PM UTC

    A fix has been implemented, but it requires a clearing of browser cache. clear your browser cache. To fix the PDFTron error, please clear your browser cache: 1. Open browser settings: Chrome/Edge/Firefox: Click the three dots → Settings → Privacy & Security → Clear browsing data 2. Select cache to clear: Choose Cached images and files (cookies can remain) 3. Clear and reload: Click Clear data Reload the page Shortcut: Windows: Ctrl + Shift + Delete Mac: Cmd + Shift + Delete

  4. resolved Mar 11, 2026, 02:50 PM UTC

    The incident has been resolved. Users might have to clear browser cache on individual browsers. To clear your browser cache: 1. Open browser settings: Chrome/Edge/Firefox: Click the three dots → Settings → Privacy & Security → Clear browsing data 2. Select cache to clear: Choose Cached images and files (cookies can remain) 3. Clear and reload: Click Clear data Reload the page Shortcut: Windows: Ctrl + Shift + Delete Mac: Cmd + Shift + Delete

Read the full incident report →

Minor March 11, 2026

Degraded performance - eHerkenning KPN

Detected by Pingoru
Mar 11, 2026, 07:00 AM UTC
Resolved
Mar 11, 2026, 09:05 AM UTC
Duration
2h 5m
Affected: eHerkenning
Timeline · 3 updates
  1. investigating Mar 11, 2026, 07:00 AM UTC

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

  2. identified Mar 11, 2026, 07:53 AM UTC

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

  3. resolved Mar 11, 2026, 09:46 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 9, 2026

Degraded performance - Assure - VideoID

Detected by Pingoru
Mar 09, 2026, 10:25 AM UTC
Resolved
Mar 09, 2026, 11:07 AM UTC
Duration
41m
Affected: VideoID
Timeline · 3 updates
  1. investigating Mar 09, 2026, 11:06 AM UTC

    We are currently observing degraded performance with VideoID, 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 Mar 09, 2026, 11:06 AM UTC

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

  3. resolved Mar 09, 2026, 11:07 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 8, 2026

Incident on 3rd party service - FTN (Nordea)

Detected by Pingoru
Mar 08, 2026, 09:12 AM UTC
Resolved
Mar 08, 2026, 09:26 AM UTC
Duration
14m
Affected: Finnish Bank eIDs (FTN)
Timeline · 2 updates
  1. monitoring Mar 08, 2026, 09:12 AM UTC

    An incident is currently affecting FTN (Nordea) 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 Mar 08, 2026, 09:26 AM UTC

    This incident has been resolved.

Read the full incident report →

Major March 5, 2026

Incident on 3rd party service - Assure API: VideoID

Detected by Pingoru
Mar 05, 2026, 02:39 PM UTC
Resolved
Mar 05, 2026, 03:07 PM UTC
Duration
28m
Affected: eIDV Provider: Signicat VideoIDVideoID
Timeline · 2 updates
  1. monitoring Mar 05, 2026, 04:05 PM UTC

    An incident is currently affecting Assure API: VideoID 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 Mar 05, 2026, 04:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 2, 2026

Incident on 3rd party service - POP Pankki, Säästöpankki and OmaSp

Detected by Pingoru
Mar 02, 2026, 09:12 PM UTC
Resolved
Mar 02, 2026, 09:40 PM UTC
Duration
28m
Affected: Finnish Bank eIDs (FTN)
Timeline · 2 updates
  1. monitoring Mar 02, 2026, 09:12 PM UTC

    An incident is currently affecting POP Pankki, Säästöpankki and OmaSp 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 Mar 02, 2026, 10:35 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 2, 2026

Incident on 3rd party service - IDIN

Detected by Pingoru
Mar 02, 2026, 04:09 PM UTC
Resolved
Mar 02, 2026, 05:49 PM UTC
Duration
1h 39m
Affected: Assure APIiDIN
Timeline · 2 updates
  1. monitoring Mar 02, 2026, 04:09 PM UTC

    An incident is currently affecting IDIN 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 Mar 02, 2026, 05:49 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 2, 2026

Degraded performance - VideoID

Detected by Pingoru
Mar 02, 2026, 02:38 PM UTC
Resolved
Mar 02, 2026, 03:02 PM UTC
Duration
24m
Affected: VideoID
Timeline · 2 updates
  1. investigating Mar 02, 2026, 03:32 PM UTC

    We are currently observing degraded performance with VideoID, 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. resolved Mar 02, 2026, 03:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 26, 2026

Investigating performance - Express Sign

Detected by Pingoru
Feb 26, 2026, 03:25 PM UTC
Resolved
Feb 26, 2026, 03:54 PM UTC
Duration
29m
Affected: BankID AMLExpress Signature API
Timeline · 3 updates
  1. investigating Feb 26, 2026, 03:25 PM UTC

    We are currently looking into the performance for Express Sign.

  2. investigating Feb 26, 2026, 03:25 PM UTC

    We are continuing to investigate this issue.

  3. resolved Feb 26, 2026, 03:54 PM UTC

    This incident has been resolved.

Read the full incident report →

Major February 25, 2026

Incident on 3rd party service - FTN (S-Pankki)

Detected by Pingoru
Feb 25, 2026, 10:49 AM UTC
Resolved
Feb 25, 2026, 11:35 AM UTC
Duration
46m
Affected: Finnish Bank eIDs (FTN)
Timeline · 2 updates
  1. monitoring Feb 25, 2026, 10:49 AM UTC

    An incident is currently affecting FTN (S-Pankki). 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 Feb 25, 2026, 11:35 AM UTC

    This incident has been resolved.

Read the full incident report →

Looking to track Signicat downtime and outages?

Pingoru polls Signicat's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Signicat reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Signicat alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Signicat for free

5 free monitors · No credit card required