Signicat Outage History

Started Aug 31, 2026, 09:27 AM UTC· resolved Sep 10, 2026, 12:22 PM UTC

1. investigating Aug 31, 2026, 09:27 AM UTC

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

2. monitoring Aug 31, 2026, 09:38 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.

3. monitoring Sep 01, 2026, 07:04 AM UTC

   We are currently observing degraded performance with eHerkenning.

4. monitoring Sep 01, 2026, 01:58 PM UTC

   We are observing degraded performance with eHerkenning.

5. monitoring Sep 01, 2026, 03:52 PM UTC

   We are currently experiencing an issue affecting the eHerkenning - Reconi and KPN. Our engineering teams are actively working to resolve the issue as quickly as possible. We sincerely apologize for any inconvenience caused and will provide our next update by 09:00 CEST tomorrow.

6. monitoring Sep 02, 2026, 07:05 AM UTC

   The degraded performance with eHerkenning is ongoing. We are awaiting further feedback from KPN regarding their progress toward resolution while actively monitoring the service.

7. monitoring Sep 02, 2026, 10:02 AM UTC

   The degraded performance with eHerkenning remains ongoing. We continue to monitor the service connection closely and are awaiting further updates from the provider.

8. monitoring Sep 02, 2026, 01:45 PM UTC

   We are seeing improvements in success rates, and we will continue to monitor.

9. monitoring Sep 02, 2026, 04:07 PM UTC

   Success rates have improved, but the incident remains open as we work toward full stabilization. Monitoring is ongoing, and our next update will be posted tomorrow by 09:00 CEST.

10. monitoring Sep 03, 2026, 01:00 PM UTC

    This incident is still ongoing. We are actively working together with the provider to get this issue resolved.

11. monitoring Sep 03, 2026, 04:42 PM UTC

    There are still issues with the product and we are working together with the provider to get this issue resolved. Next update can be expected on 04.09 10:00 CEST or sooner if we get new information.

12. monitoring Sep 04, 2026, 08:02 AM UTC

    This incident is still ongoing. We are actively working together with the provider to get this issue resolved.

13. monitoring Sep 04, 2026, 02:02 PM UTC

    This incident is still ongoing. We are actively working together with the provider to get this issue resolved.

14. monitoring Sep 07, 2026, 07:13 AM UTC

    This incident is still ongoing. We are actively working together with the provider to get this issue resolved.

15. monitoring Sep 07, 2026, 01:33 PM UTC

    This incident is still ongoing. We are actively working together with the provider to get this issue resolved.

16. monitoring Sep 09, 2026, 07:45 AM UTC

    This incident is still ongoing. We are actively working together with the provider to get this issue resolved.

17. monitoring Sep 10, 2026, 10:44 AM UTC

    The issue has been resolved and we are seeing improvements. We will continue to monitor.

18. resolved Sep 10, 2026, 12:22 PM UTC

    The issue have been resolved

Read the full incident report →

Started Aug 31, 2026, 07:48 AM UTC· resolved Aug 31, 2026, 10:11 AM UTC

1. monitoring Aug 31, 2026, 07:48 AM UTC

   An incident is currently affecting BankID AML 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 Aug 31, 2026, 08:57 AM UTC

   Success rates are improving. We will continue monitoring closely.

3. resolved Aug 31, 2026, 10:11 AM UTC

   The issue has been resolved

Read the full incident report →

Started Aug 30, 2026, 07:28 PM UTC· resolved Aug 30, 2026, 07:45 PM UTC

1. monitoring Aug 30, 2026, 07:28 PM 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. resolved Aug 30, 2026, 07:45 PM UTC

   The incident have been resolved.

Read the full incident report →

Started Aug 29, 2026, 10:03 PM UTC· resolved Aug 30, 2026, 01:12 AM UTC

1. monitoring Aug 29, 2026, 10:03 PM UTC

   An incident is currently affecting Finnish Bank eIDs (FTN) - Nordea 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 Aug 30, 2026, 01:12 AM UTC

   The incident have been resolved.

Read the full incident report →

Started Aug 28, 2026, 06:42 PM UTC· resolved Aug 28, 2026, 06:52 PM UTC

1. identified Aug 28, 2026, 06:42 PM UTC

   MobileID is experiencing intermittent stability issues

2. resolved Aug 28, 2026, 06:52 PM UTC

   Issue has been resolved

Read the full incident report →

Started Aug 27, 2026, 11:12 AM UTC· resolved Aug 27, 2026, 01:39 PM UTC

1. identified Aug 27, 2026, 11:12 AM UTC

   We are working on a fix for an issue with t-rank-evry.

2. monitoring Aug 27, 2026, 12:46 PM UTC

   We have released a fix and we are currently monitoring the release.

3. resolved Aug 27, 2026, 01:39 PM UTC

   Incident has been resolved

Read the full incident report →

Started Aug 27, 2026, 03:20 AM UTC· resolved Aug 27, 2026, 07:01 AM UTC

1. identified Aug 27, 2026, 03:20 AM UTC

   We are seeing delays in validations through Portal and Portal API and are working on resolving the issue.

2. resolved Aug 27, 2026, 07:01 AM UTC

   The delayed validations are now starting.

Read the full incident report →

Started Aug 26, 2026, 11:57 AM UTC· resolved Aug 26, 2026, 12:49 PM UTC

1. monitoring Aug 26, 2026, 11:57 AM UTC

   An incident is currently affecting 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 Aug 26, 2026, 12:49 PM UTC

   The incident have been resolved.

Read the full incident report →

Started Aug 25, 2026, 05:55 PM UTC· resolved Aug 26, 2026, 07:35 AM UTC

1. identified Aug 25, 2026, 05:55 PM UTC

   KvK Service Interruption We are currently experiencing an issue affecting the source KvK in our data verification service. Our engineering teams are actively working to resolve the underlying configuration as quickly as possible. We sincerely apologize for any inconvenience caused and will provide our next update by 09:00 CEST tomorrow.

2. identified Aug 26, 2026, 07:11 AM UTC

   We are continuing to work on a fix for this issue

3. resolved Aug 26, 2026, 07:35 AM UTC

   The incident have been resolved

Read the full incident report →

Started Aug 24, 2026, 08:09 PM UTC· resolved Aug 25, 2026, 01:57 PM UTC

1. investigating Aug 24, 2026, 08:09 PM UTC

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

2. investigating Aug 24, 2026, 08:12 PM UTC

   Express Signature API is affected by BankID AML API having degraded performance.

3. monitoring Aug 24, 2026, 09:19 PM UTC

   The incident is currently affecting BankID AML API, again affecting our Express Signature API. 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.

4. resolved Aug 25, 2026, 01:57 PM UTC

   The issue is resolved.

Read the full incident report →

Started Aug 24, 2026, 02:41 AM UTC· resolved Aug 24, 2026, 06:32 AM UTC

1. monitoring Aug 24, 2026, 02:41 AM UTC

   An incident is currently affecting FTN IdP Säästöpankki. 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 Aug 24, 2026, 06:32 AM UTC

   The incident have been resolved.

Read the full incident report →

Started Aug 24, 2026, 02:39 AM UTC· resolved Aug 24, 2026, 07:15 AM UTC

1. monitoring Aug 24, 2026, 02:39 AM UTC

   An incident is currently affecting ID-Porten 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 Aug 24, 2026, 06:35 AM UTC

   We are continuing to monitor the situation. Some availability have been restored.

3. resolved Aug 24, 2026, 07:15 AM UTC

   The incident have been resolved.

Read the full incident report →

Started Aug 22, 2026, 10:18 PM UTC· resolved Aug 23, 2026, 04:43 PM UTC

1. investigating Aug 22, 2026, 10:18 PM UTC

   An incident is currently affecting Säästöpankki 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. identified Aug 23, 2026, 10:39 AM UTC

   Säästöpankki and OmaSp is undergoing planned maintenance today until 14:00 CEST, causing a temporary full outage.

3. identified Aug 23, 2026, 12:42 PM UTC

   Säästöpankki and OmaSp has extended the maintenance window to 18:00 CEST.

4. resolved Aug 23, 2026, 04:43 PM UTC

   Services are restored.

Read the full incident report →

Started Aug 20, 2026, 08:15 PM UTC· resolved Aug 20, 2026, 09:49 PM UTC

1. monitoring Aug 20, 2026, 08:15 PM UTC

   An incident is currently affecting Norwegian BankID CSC (Signing) 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 Aug 20, 2026, 09:31 PM UTC

   We are seeing successful signatures with Norwegian BankID CSC. We will continue to monitor the service for potential issues.

3. resolved Aug 20, 2026, 09:49 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 20, 2026, 07:55 AM UTC· resolved Aug 20, 2026, 02:02 PM UTC

1. investigating Aug 20, 2026, 07:55 AM UTC

   We are currently observing degraded performance with DigID, 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 Aug 20, 2026, 09:05 AM UTC

   An incident is currently affecting DigID. We have identified that 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.

3. monitoring Aug 20, 2026, 11:32 AM UTC

   We are still experiencing issues related to this 3rd party incident.

4. resolved Aug 20, 2026, 02:02 PM UTC

   We have been monitoring and have seen that the issue is now resolved and the resolution is persistant.

Read the full incident report →

Started Aug 19, 2026, 08:40 PM UTC· resolved Aug 19, 2026, 11:10 PM UTC

1. monitoring Aug 19, 2026, 08:40 PM UTC

   An incident is currently affecting NBID CSC (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 Aug 19, 2026, 11:02 PM UTC

   We are seeing successful signatures with NBID CSC. We will continue to monitor the service for potential issues.

3. resolved Aug 19, 2026, 11:10 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 19, 2026, 07:54 PM UTC· resolved Aug 19, 2026, 11:17 PM UTC

1. monitoring Aug 19, 2026, 07:54 PM UTC

   An incident is currently affecting DigiD and DigiD CombiConnect 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 Aug 19, 2026, 10:28 PM UTC

   We are seeing some successful transactions. We are continuing to monitor their progression towards resolution.

3. resolved Aug 19, 2026, 11:17 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 18, 2026, 02:23 PM UTC· resolved Aug 18, 2026, 02:45 PM UTC

1. monitoring Aug 18, 2026, 02:23 PM UTC

   An incident is currently affecting eHerkenning - Reconi and KPN 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 Aug 18, 2026, 02:45 PM UTC

   Incident has been resolved. Successrate for Reconi and KPN are back to normal.

Read the full incident report →

Started Aug 17, 2026, 08:45 AM UTC· resolved Aug 17, 2026, 09:34 AM UTC

1. investigating Aug 17, 2026, 08:45 AM UTC

   We are currently observing degraded performance with Swedish BankID, 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 Aug 17, 2026, 09:11 AM UTC

   We have applied a fix for this issue and will be monitoring before resolving the issue.

3. resolved Aug 17, 2026, 09:34 AM UTC

   We have completed our monitoring and the issue was addressed by a fix.

Read the full incident report →

Started Aug 13, 2026, 10:19 AM UTC· resolved Aug 13, 2026, 01:13 PM UTC

1. identified Aug 13, 2026, 10:19 AM UTC

   We are currently observing degraded performance with 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. resolved Aug 13, 2026, 01:13 PM UTC

   The incident is resolved.

Read the full incident report →

Started Aug 12, 2026, 08:08 AM UTC· resolved Aug 25, 2026, 10:54 AM UTC

1. monitoring Aug 12, 2026, 08:08 AM UTC

   An incident is currently affecting Data Verification, with it's sources DVV and Norwegian Folkeregisteret. 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. investigating Aug 12, 2026, 08:22 AM UTC

   We're currently observing degraded performance in Data Verification dependent on sources DVV and Norwegian Folkeregisteret. Incident response has been initiated and we are actively investigating the issue and working to restore normal operations.

3. identified Aug 12, 2026, 08:51 AM UTC

   We've identified the cause of the issue and are working to resolve it.

4. identified Aug 12, 2026, 11:56 AM UTC

   We've identified the cause of the issue and are working to resolve it. Issues related to Norwegian Folkeregisteret are resolved.

5. identified Aug 12, 2026, 12:09 PM UTC

   We've identified the cause of the issue and are working to resolve it. Issues related to Norwegian Folkeregisteret and ID-porten are resolved.

6. identified Aug 12, 2026, 12:53 PM UTC

   We've identified the cause of the issue and are working to resolve it. Issues related to Norwegian Folkeregisteret, ID-porten and DVV are resolved. We are awaiting resolution for Kamer Van Koophandel (KvK).

7. identified Aug 17, 2026, 11:31 AM UTC

   The incident is still ongoing and is currently affecting Data Verification source KvK. We are expecting this to take a longer time to resolve and will keep the statuspage updated on a daily basis.

8. identified Aug 18, 2026, 07:30 AM UTC

   We are still working of a fix for this issue

9. identified Aug 19, 2026, 10:57 AM UTC

   We are still working of a fix for this issue

10. identified Aug 24, 2026, 07:54 AM UTC

    We are still working on a fix for this issue.

11. identified Aug 25, 2026, 08:32 AM UTC

    The incident is still ongoing and is currently affecting Data Verification source KvK. We are expecting this to take a longer time to resolve and will keep the statuspage updated on a daily basis.

12. monitoring Aug 25, 2026, 09:37 AM UTC

    We have applied a fix for this issue and will be monitoring to verify that it works.

13. resolved Aug 25, 2026, 10:54 AM UTC

    The incident is now resolved.

Read the full incident report →

Started Aug 03, 2026, 07:20 PM UTC· resolved Aug 04, 2026, 10:47 AM UTC

1. monitoring Aug 03, 2026, 07:20 PM UTC

   An incident has been affecting ID-Porten and Info-soruce: NO-FREG throughout the day. Our connection towards this 3rd party service is running but is not functioning properly as a result of their incident. Recent information is that most services are operational, however users might experience instability and increased response times. Ref: https://status.digdir.no/incidents/d7hvqmf2yr3l We are monitoring their progression towards resolution.

2. monitoring Aug 03, 2026, 11:05 PM UTC

   The incident is still ongoing, and we are continuing to monitor their progression towards resolution. The next update will be around 09:00 CEST.

3. monitoring Aug 04, 2026, 07:06 AM UTC

   The incident is still ongoing, and we are continuing to monitor their progression towards resolution.

4. monitoring Aug 04, 2026, 08:55 AM UTC

   The incident is still ongoing, and we are continuing to monitor their progression towards resolution.

5. monitoring Aug 04, 2026, 10:33 AM UTC

   We are seeing improvements in success rate and are continuing to monitor the situation.

6. resolved Aug 04, 2026, 10:47 AM UTC

   The incident is resolved.

Read the full incident report →

Started Jul 27, 2026, 03:46 PM UTC· resolved Jul 27, 2026, 05:36 PM UTC

1. investigating Jul 27, 2026, 03:46 PM UTC

   An incident is currently affecting bankid aml signing. 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 Jul 27, 2026, 05:36 PM UTC

   All components are resolved, but we are still monitoring the situation.

Read the full incident report →

Started Jul 17, 2026, 08:37 AM UTC· resolved Jul 17, 2026, 09:57 AM UTC

1. investigating Jul 17, 2026, 08:37 AM UTC

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

2. monitoring Jul 17, 2026, 08:53 AM 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.

3. monitoring Jul 17, 2026, 09:35 AM UTC

   iDIN is operational again and we will continue to monitor

4. resolved Jul 17, 2026, 09:57 AM UTC

   The issue has been resolved

Read the full incident report →

Started Jun 11, 2026, 12:17 PM UTC· resolved Jun 12, 2026, 06:50 AM UTC

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 →