Signatures down
Timeline · 1 update
- resolved May 06, 2026, 09:27 AM UTC
Signatures was down for 11:02 to 11:13 AM CEST, due to a misconfiguration in a CDN layer. We will be migrating our services to a more stable CDN over the coming months.
Criipto had 20 outages in the last 2 years totaling 38h 44m of downtime — averaging 0.8 incidents per month.
There were 20 Criipto outages since May 28, 2024 totaling 38h 44m of downtime. Each is summarised below — incident details, duration, and resolution information.
Signatures was down for 11:02 to 11:13 AM CEST, due to a misconfiguration in a CDN layer. We will be migrating our services to a more stable CDN over the coming months.
We are seeing a high error rate for our Signatures product, related to our TSA and QES provider Stø/BankID.
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.
TSA services have been restored - Signing with most eIDs is now working again. Signing with BankID is still down.
Signing with BankID is still down. BankID is investigating the issue.
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."
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.
The provider of Danish addresses ("CPR-kontoret") reports that the issue has been resolved.
We have reports of users failing to connect to *.criipto.id based domains. We are investigating.
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.
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.
We have reports from customers and our own testing that the network issue is resolved. We will continue to monitor.
This incident has been resolved.
The Verify service powering authentications is currently experiencing issues with an underlying infrastructure components. Service is degraded.
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.
This incident has been resolved.
IN Groupe reports that MitID Web sites and API services might experience instability.
Update from IN Groupe: The MitID Production infrastructure is still experiencing instability. We are working on solving the problem.
Update from IN Groupe: The MitID Production infrastructure is still experiencing instability. We are working on solving the problem. No ETAs provided.
Update from IN Groupe: The MitID Production infrastructure is still experiencing instability. We are working on solving the problem. No ETAs provided.
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)
IN Groupe reports that the incident has been resolved.
The provider of MitID; INGroupe reports that MitID is currently unavailable: https://www.digitaliser.dk/mitid/nyt-fra-mitid/2026/feb/driftsforstyrrelser-mitid
MitID should be operational again: https://www.digitaliser.dk/mitid/nyt-fra-mitid/2026/feb/driftsforstyrrelser-mitid
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)
Issues with connecting to the TSA provider appears to have resolved and signing operations are back to normal.
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
INGroupe reports that the issue is now solved
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.
NemLogin services appear to have restored, Local IdP and MitID Erhverv are working again.
We have observed issues connecting to Telia who helps power our FTN logins.
Connection issues to Telia have been resolved. FTN is now operational again.
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.
The issue has been identified and a fix is being implemented.
From IN Groupe, the operator of MitID: The MitID Production infrastructure is still unavailable. We are working on solving the problem. Incident: INC0772812. Start: 18.06.2025 04:55 CEST. Impact: MitID is unavailable. FURTHER INFORMATION When new information is available.
According to IN Groupe, we’re back up: MitID is now back to normal operation. Incident: INC0772812. Start: 18.06.2025 04:55 CEST. Stop: 18.06.2025 06:40 CEST.
We are currently investigating the issue.
The issue has been identified and we are applying a fix. The issue is isolated to MitID
Issue has been identified and resolved.
According to BankID BankAxept, the operator of Norwegian BankID, there are issues with the BankID app today. BankID with a code device is working as it should.
In line with the BankID status page (https://status.stoe.no/en), this has been changed to a major outage.
All Norwegian BankID systems are operational again
We are seeing an increasing rates due to a cloud storage service being unavailable. We are investigating and monitoring.
Underlying storage service had a spike of errors that resolved quickly after. Service is fully operational.
We're observing an increased error rate for Signatures API related to signing signatory links, we are investigating root causes and working on mitigations.
First mitigation has been deployed and we're working on a second mitigation now.
Error rate has decreased with initial deploy mitigation. We are now deploying our second mitigation that we hope will reduce error rates to regular levels.
We have deployed additional mitigations and error rate appears to have returned to normal levels.
We have received the following from NETS, the maintainers of the MitID Core system: ------------ The MitID Production infrastructure is experiencing instability We are working on solving the problem. Incident: INC0673763 Start: 07.10.2024 08:30 CEST Impact: Web sites and API services might experience instability, and users unable to login with MitID. FURTHER INFORMATION When new information is available. ------------
We have received the following update from NETS: ---------- The MitID Production infrastructure is still experiencing instability. All technical teams are gathered investigating to identify and correct the issue. Incident: INC0673763 Start: 07.10.2024 Impact: Web sites and API services might experience instability. End user login via MitID not possible. FURTHER INFORMATION When new information is available. ----------
We have received the following update from NETS: The incident has been resolved. Incident: INC0673763. Start: 07.10.2024 08:30 CEST. Stop: 07.10.2024 10:10 CEST.
Danish MitID is showing some instability and has been since 9:15. We will let you know as soon as it's back up or we get new information from the provider of MitID.
The incident has been resolved. We will provide a post-mortem we get more information from the provider of MitID.
From 04:20 to 07:20 (GMT+2) we observed 3 incidents, each one minute in length, of failing MitID logins. We have identified and mitigated the issue.
MitID was down for everybody for two hours due to a distributed denial of service attack