Criipto Outage History

Criipto is up right now

Criipto had 14 outages in the last 2 years totaling 37h 21m of downtime — averaging 0.6 incidents per month.

There were 14 Criipto outages since September 8, 2025 totaling 37h 21m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.criipto.com

Major July 17, 2026

High MitID error rate

Detected by Pingoru
Jul 17, 2026, 12:46 PM UTC
Resolved
Jul 17, 2026, 02:01 PM UTC
Duration
1h 15m
Affected: MitID (Denmark)
Timeline · 3 updates
  1. investigating Jul 17, 2026, 12:46 PM UTC

    We are seeing a high error rate from MitID endpoints. This is affecting an increasing number of logins. We are investigating.

  2. monitoring Jul 17, 2026, 01:03 PM UTC

    MitID error rate is back to normal

  3. resolved Jul 17, 2026, 02:01 PM UTC

    We have linked the MitID issues with a combination of appswitch hints and the introduction of MitID CIBA resulting in a parameter combination that MitID rejected. We have added additional telemetry to detect similar issues in the future as well as regression tests against future issues of the same nature.

Read the full incident report →

Major July 16, 2026

Signatures down

Detected by Pingoru
Jul 16, 2026, 11:52 AM UTC
Resolved
Jul 16, 2026, 07:50 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Jul 16, 2026, 11:52 AM UTC

    A problem with AWS CloudFront Origins resulted in requests towards Signatures were not being able to hit our API.

Read the full incident report →

Major July 16, 2026

Signatures - signing issues

Detected by Pingoru
Jul 16, 2026, 09:31 AM UTC
Resolved
Jul 16, 2026, 11:50 AM UTC
Duration
2h 18m
Affected: Idura Signatures
Timeline · 8 updates
  1. investigating Jul 16, 2026, 08:58 AM UTC

    We have been alerted and are investigating the issue.

  2. investigating Jul 16, 2026, 09:04 AM UTC

    Issue only related to the idura.broker domains

  3. investigating Jul 16, 2026, 09:31 AM UTC

    Global CloudFront issues. Investigating workaround remediation.

  4. investigating Jul 16, 2026, 09:54 AM UTC

    We have located a workaround and are actively working on getting it released.

  5. investigating Jul 16, 2026, 10:49 AM UTC

    We are still working on resolving the issue.

  6. monitoring Jul 16, 2026, 11:30 AM UTC

    AWS is restoring their services to normal behaviour. Our workaround is on the way, but facing a few issues related to duplicate resource naming. We are continuing to prepare the work-around incase it becomes necessary but we are now seeing better error rates from CloudFront, so our mitigation may not be necessary.

  7. monitoring Jul 16, 2026, 11:33 AM UTC

    Error rate has dropped to 0%, we will continue to monitor

  8. resolved Jul 16, 2026, 11:50 AM UTC

    AWS has fixed the issue on their end before we managed to release our mitigation. Our mitigation took longer than initially expected.

Read the full incident report →

Critical April 24, 2026

High error rate for Signatures

Detected by Pingoru
Apr 24, 2026, 06:09 PM UTC
Resolved
Apr 25, 2026, 06:34 AM UTC
Duration
12h 24m
Affected: Idura SignaturesBankID Signing (Norway)
Timeline · 5 updates
  1. investigating Apr 24, 2026, 06:09 PM UTC

    We are seeing a high error rate for our Signatures product, related to our TSA and QES provider Stø/BankID.

  2. investigating Apr 24, 2026, 06:50 PM UTC

    Our underlying TSA provider (Stø/BankID) is still down, which is affecting all signing operations. BankID QES/CSC is still down, which is affecting Norwegian BankID signing operations.

  3. investigating Apr 24, 2026, 08:09 PM UTC

    TSA services have been restored - Signing with most eIDs is now working again. Signing with BankID is still down.

  4. investigating Apr 24, 2026, 08:15 PM UTC

    Signing with BankID is still down. BankID is investigating the issue.

  5. resolved Apr 25, 2026, 06:34 AM UTC

    Issues with the TSA provided by BankID was resolved around 22:15 CEST Issues with Signing provided by BankID was resolved around 05:27 CEST BankID reports that the "The outage in BankID Signing was experienced due to a maintenance."

Read the full incident report →

Notice April 10, 2026

Danish Address lookup is down

Detected by Pingoru
Apr 10, 2026, 07:42 AM UTC
Resolved
Apr 10, 2026, 10:06 AM UTC
Duration
2h 24m
Affected: Danish Address Lookup
Timeline · 2 updates
  1. identified Apr 10, 2026, 07:42 AM UTC

    The provider of Danish addresses ("CPR-kontoret") has acknowledged the problem affecting many of its customers. The are currently working on a fix, with no communicated ETA. Fingers crossed.

  2. resolved Apr 10, 2026, 10:06 AM UTC

    The provider of Danish addresses ("CPR-kontoret") reports that the issue has been resolved.

Read the full incident report →

Major April 7, 2026

Connection issues to criipto.id domains

Detected by Pingoru
Apr 07, 2026, 12:14 PM UTC
Resolved
Apr 07, 2026, 02:01 PM UTC
Duration
1h 46m
Affected: Idura Verify Authentication CoreIdura Signatures
Timeline · 5 updates
  1. investigating Apr 07, 2026, 12:14 PM UTC

    We have reports of users failing to connect to *.criipto.id based domains. We are investigating.

  2. investigating Apr 07, 2026, 12:35 PM UTC

    We are continuing to investigate. Multiple network locations are unable to connect to Idura/Criipto domains, while some succeed, and we are still observing succesful logins.

  3. investigating Apr 07, 2026, 01:06 PM UTC

    Users report, and Idura staff confirms, that mobile connections appear unaffected. Multiple network locations still fail, likely due to a faulty network location in Azure.

  4. monitoring Apr 07, 2026, 01:43 PM UTC

    We have reports from customers and our own testing that the network issue is resolved. We will continue to monitor.

  5. resolved Apr 07, 2026, 02:01 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 31, 2026

Verify degraded

Detected by Pingoru
Mar 31, 2026, 09:34 AM UTC
Resolved
Mar 31, 2026, 12:46 PM UTC
Duration
3h 11m
Affected: Idura Verify Authentication Core
Timeline · 3 updates
  1. investigating Mar 31, 2026, 09:34 AM UTC

    The Verify service powering authentications is currently experiencing issues with an underlying infrastructure components. Service is degraded.

  2. monitoring Mar 31, 2026, 09:58 AM UTC

    Between 11:30 and 11:39 (Copenhagen time), a system component exhibited intermittent erroneous behavior. 25 logins failed to complete succesfully during the time window. We continue to monitor the behavior closely.

  3. resolved Mar 31, 2026, 12:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical March 31, 2026

MitID instability

Detected by Pingoru
Mar 31, 2026, 07:24 AM UTC
Resolved
Mar 31, 2026, 12:27 PM UTC
Duration
5h 2m
Affected: MitID (Denmark)
Timeline · 6 updates
  1. identified Mar 31, 2026, 07:24 AM UTC

    IN Groupe reports that MitID Web sites and API services might experience instability.

  2. identified Mar 31, 2026, 08:16 AM UTC

    Update from IN Groupe: The MitID Production infrastructure is still experiencing instability. We are working on solving the problem.

  3. identified Mar 31, 2026, 09:09 AM UTC

    Update from IN Groupe: The MitID Production infrastructure is still experiencing instability. We are working on solving the problem. No ETAs provided.

  4. identified Mar 31, 2026, 10:05 AM UTC

    Update from IN Groupe: The MitID Production infrastructure is still experiencing instability. We are working on solving the problem. No ETAs provided.

  5. identified Mar 31, 2026, 11:34 AM UTC

    Update from IN Groupe: Update from IN Groupe: The MitID Production infrastructure is still experiencing instability. We are working on solving the problem. (Same update as previous updates, no new information or ETA)

  6. resolved Mar 31, 2026, 12:27 PM UTC

    IN Groupe reports that the incident has been resolved.

Read the full incident report →

Critical February 27, 2026

MitID is down

Detected by Pingoru
Feb 27, 2026, 10:30 AM UTC
Resolved
Feb 27, 2026, 11:27 AM UTC
Duration
56m
Affected: MitID (Denmark)
Timeline · 2 updates
  1. identified Feb 27, 2026, 10:30 AM UTC

    The provider of MitID; INGroupe reports that MitID is currently unavailable: https://www.digitaliser.dk/mitid/nyt-fra-mitid/2026/feb/driftsforstyrrelser-mitid

  2. resolved Feb 27, 2026, 11:27 AM UTC

    MitID should be operational again: https://www.digitaliser.dk/mitid/nyt-fra-mitid/2026/feb/driftsforstyrrelser-mitid

Read the full incident report →

Critical January 22, 2026

Signatures API down

Detected by Pingoru
Jan 22, 2026, 09:40 AM UTC
Resolved
Jan 22, 2026, 09:45 AM UTC
Duration
4m
Affected: Idura Signatures
Timeline · 2 updates
  1. investigating Jan 22, 2026, 09:40 AM UTC

    Signing via the Signatures API is currently available as the underlying TSA service has experienced a service disruption. We are investigating and establishing contact with the TSA provider (Stø / BankID BankAxept)

  2. resolved Jan 22, 2026, 09:45 AM UTC

    Issues with connecting to the TSA provider appears to have resolved and signing operations are back to normal.

Read the full incident report →

Critical January 12, 2026

MitID down

Detected by Pingoru
Jan 12, 2026, 08:46 AM UTC
Resolved
Jan 12, 2026, 12:09 PM UTC
Duration
3h 22m
Affected: MitID (Denmark)
Timeline · 2 updates
  1. investigating Jan 12, 2026, 08:46 AM UTC

    Message from INGroupe: The MitID Production infrastructure is experiencing instability We are working on solving the problem. Incident: INC0868119 Start: 12.01.2026 @ 09:00 CET

  2. resolved Jan 12, 2026, 12:09 PM UTC

    INGroupe reports that the issue is now solved

Read the full incident report →

Critical November 25, 2025

Issues with MitID Erhverv

Detected by Pingoru
Nov 25, 2025, 05:21 PM UTC
Resolved
Nov 25, 2025, 06:00 PM UTC
Duration
39m
Affected: MitID Business (Erhverv)
Timeline · 2 updates
  1. investigating Nov 25, 2025, 05:21 PM UTC

    We are currently seeing an issue connecting to the NemLogin services that power MitID Erhverv and Local IdP. This affects users ability to login with MitID Erhverv, MitID for private citizens is not affected.

  2. resolved Nov 25, 2025, 06:00 PM UTC

    NemLogin services appear to have restored, Local IdP and MitID Erhverv are working again.

Read the full incident report →

Critical November 17, 2025

FTN down

Detected by Pingoru
Nov 17, 2025, 07:56 PM UTC
Resolved
Nov 17, 2025, 08:25 PM UTC
Duration
28m
Affected: FTN (Finland)
Timeline · 3 updates
  1. investigating Nov 17, 2025, 07:56 PM UTC

    We have observed issues connecting to Telia who helps power our FTN logins.

  2. resolved Nov 17, 2025, 08:25 PM UTC

    Connection issues to Telia have been resolved. FTN is now operational again.

  3. postmortem Nov 18, 2025, 09:11 AM UTC

    We have received the following details from Telia: > Last night we experienced couple of huge denial of service attacks between > > 2025-11-17 20:31:44 EET à 20:43:10 EET > > and also > > 2025-11-17 23:07:44 EET à 23:15:10 EET. > > Our defensing mechanism has probably been the reason for this outage. I will report this to our DDoS team. Sounds like a IP range whitelisting problem to me. As a future guard against this problem, Telia have now explicitly allow-listed our outbound IP addresses.

Read the full incident report →