- Detected by Pingoru
- May 21, 2026, 09:14 AM UTC
- Resolved
- May 21, 2026, 10:08 AM UTC
- Duration
- 53m
Affected: BankID Signing (Norway)
Timeline · 6 updates
-
investigating May 21, 2026, 09:12 AM UTC
We are seeing an increased error rate from the CSC Signing API offered by BankID / Stø. Currently around 10% of requests are failing, we are investigating and monitoring.
-
investigating May 21, 2026, 09:14 AM UTC
Norwegian BankID signing is down, all requests to the CSC Signing API from BankID / Stø are failing.
-
investigating May 21, 2026, 09:30 AM UTC
Signing with Norwegian BankID is still down, all requests to BankID Signing are failing. The BankID team has acknowledged and they are working on the issue.
-
investigating May 21, 2026, 09:51 AM UTC
Status update from BankID / Stø: "The issue has been identified and a fix is being implemented"
-
monitoring May 21, 2026, 10:00 AM UTC
Error rate for BankID Signing has decreased in our own monitoring - We are waiting a formal update from the BankID taem.
-
resolved May 21, 2026, 10:08 AM UTC
BankID reports that a fix has been implemented.
Read the full incident report →
- Detected by Pingoru
- May 06, 2026, 09:27 AM UTC
- Resolved
- May 06, 2026, 09:02 AM UTC
- Duration
- —
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.
Read the full incident report →
- 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
-
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.
-
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.
-
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.
-
investigating Apr 24, 2026, 08:15 PM UTC
Signing with BankID is still down. BankID is investigating the issue.
-
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 →
- 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
-
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.
-
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 →
- 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
-
investigating Apr 07, 2026, 12:14 PM UTC
We have reports of users failing to connect to *.criipto.id based domains. We are investigating.
-
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.
-
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.
-
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.
-
resolved Apr 07, 2026, 02:01 PM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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.
-
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.
-
resolved Mar 31, 2026, 12:46 PM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
identified Mar 31, 2026, 07:24 AM UTC
IN Groupe reports that MitID Web sites and API services might experience instability.
-
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.
-
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.
-
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.
-
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)
-
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 - 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
-
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
-
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 - 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
-
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)
-
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 - 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
-
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
-
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 - 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
-
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.
-
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 - 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
-
investigating Nov 17, 2025, 07:56 PM UTC
We have observed issues connecting to Telia who helps power our FTN logins.
-
resolved Nov 17, 2025, 08:25 PM UTC
Connection issues to Telia have been resolved. FTN is now operational again.
-
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 →
- Detected by Pingoru
- Jun 18, 2025, 04:00 AM UTC
- Resolved
- Jun 18, 2025, 04:58 AM UTC
- Duration
- 58m
Affected: MitID (Denmark)
Timeline · 3 updates
-
identified Jun 18, 2025, 04:00 AM UTC
The issue has been identified and a fix is being implemented.
-
identified Jun 18, 2025, 04:44 AM UTC
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.
-
resolved Jun 18, 2025, 04:58 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- May 17, 2025, 10:50 AM UTC
- Resolved
- May 17, 2025, 11:31 AM UTC
- Duration
- 41m
Affected: Idura Verify Authentication Core
Timeline · 3 updates
-
investigating May 17, 2025, 10:50 AM UTC
We are currently investigating the issue.
-
identified May 17, 2025, 11:04 AM UTC
The issue has been identified and we are applying a fix. The issue is isolated to MitID
-
resolved May 17, 2025, 11:31 AM UTC
Issue has been identified and resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 02, 2025, 09:41 AM UTC
- Resolved
- Jan 02, 2025, 10:48 AM UTC
- Duration
- 1h 7m
Affected: BankID OIDC (Norway)
Timeline · 3 updates
-
identified Jan 02, 2025, 09:41 AM UTC
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.
-
identified Jan 02, 2025, 09:43 AM UTC
In line with the BankID status page (https://status.stoe.no/en), this has been changed to a major outage.
-
resolved Jan 02, 2025, 10:48 AM UTC
All Norwegian BankID systems are operational again
Read the full incident report →
- Detected by Pingoru
- Dec 25, 2024, 08:43 AM UTC
- Resolved
- Dec 25, 2024, 09:01 AM UTC
- Duration
- 17m
Affected: Idura Verify Authentication Core
Timeline · 2 updates
-
investigating Dec 25, 2024, 08:43 AM UTC
We are seeing an increasing rates due to a cloud storage service being unavailable. We are investigating and monitoring.
-
resolved Dec 25, 2024, 09:01 AM UTC
Underlying storage service had a spike of errors that resolved quickly after. Service is fully operational.
Read the full incident report →
- Detected by Pingoru
- Nov 01, 2024, 01:28 PM UTC
- Resolved
- Nov 01, 2024, 04:32 PM UTC
- Duration
- 3h 3m
Affected: Idura Signatures
Timeline · 4 updates
-
investigating Nov 01, 2024, 01:28 PM UTC
We're observing an increased error rate for Signatures API related to signing signatory links, we are investigating root causes and working on mitigations.
-
identified Nov 01, 2024, 01:56 PM UTC
First mitigation has been deployed and we're working on a second mitigation now.
-
identified Nov 01, 2024, 03:22 PM UTC
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.
-
resolved Nov 01, 2024, 04:32 PM UTC
We have deployed additional mitigations and error rate appears to have returned to normal levels.
Read the full incident report →
- Detected by Pingoru
- Oct 07, 2024, 07:39 AM UTC
- Resolved
- Oct 07, 2024, 09:36 AM UTC
- Duration
- 1h 57m
Affected: MitID (Denmark)
Timeline · 3 updates
-
identified Oct 07, 2024, 07:39 AM UTC
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. ------------
-
identified Oct 07, 2024, 07:53 AM UTC
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. ----------
-
resolved Oct 07, 2024, 09:36 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Jul 01, 2024, 08:14 AM UTC
- Resolved
- Jul 01, 2024, 08:31 AM UTC
- Duration
- 17m
Affected: MitID (Denmark)
Timeline · 2 updates
-
identified Jul 01, 2024, 08:14 AM UTC
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.
-
resolved Jul 01, 2024, 08:31 AM UTC
The incident has been resolved. We will provide a post-mortem we get more information from the provider of MitID.
Read the full incident report →
- Detected by Pingoru
- Jun 21, 2024, 05:27 AM UTC
- Resolved
- Jun 21, 2024, 02:30 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jun 21, 2024, 05:27 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- May 28, 2024, 03:21 PM UTC
- Resolved
- May 20, 2024, 11:00 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved May 28, 2024, 03:21 PM UTC
MitID was down for everybody for two hours due to a distributed denial of service attack
Read the full incident report →
