- Detected by Pingoru
- Oct 01, 2026, 01:46 PM UTC
- Resolved
- Oct 01, 2026, 03:05 PM UTC
- Duration
- 1h 18m
Affected: BankID OIDC (Norway)
Timeline · 4 updates
-
investigating Oct 01, 2026, 01:46 PM UTC
Customers are reporting, and we have confirmed, that many requests to BankID are failing. Likely related to the use of scopes
-
identified Oct 01, 2026, 02:32 PM UTC
We have identified a workaround for some customers. If you are sending the "phone" scope, you may be able to work around the issue by removing the "phone" scope if you do not need the phone number in your application.
-
monitoring Oct 01, 2026, 03:02 PM UTC
Norwegian BankID reports they have fixed the issue. We have confirmed that the fix works for most customers. We are monitoring for remaining errors.
-
resolved Oct 01, 2026, 03:05 PM UTC
We have confirmed that the incident has been resolved for all customers.
Read the full incident report →
- Detected by Pingoru
- Sep 25, 2026, 10:45 AM UTC
- Resolved
- Sep 25, 2026, 12:12 PM UTC
- Duration
- 1h 27m
Affected: BankID Signing (Norway)
Timeline · 3 updates
-
investigating Sep 25, 2026, 10:49 AM UTC
There are currently issues with signing using Norwegian BankID.
-
monitoring Sep 25, 2026, 11:53 AM UTC
Operations seem to have stabilized. We are monitoring.
-
resolved Sep 25, 2026, 12:12 PM UTC
This incident has been resolved.
Read the full incident report →
Notice September 11, 2026 - Detected by Pingoru
- Sep 11, 2026, 12:57 PM UTC
- Resolved
- Sep 11, 2026, 12:57 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Sep 11, 2026, 01:37 PM UTC
From 14:57 to 15:02 CEST 50% requests for signatures failed, this was due to null-reference exception in proxy handling for criipto.id domains. idura.broker domains were unaffected. From 15:02 CEST to 15:35 about 0.1% requests for signatures failed, due to a sticky load balancer that was not rolled back correctly.
Read the full incident report →
Critical September 3, 2026 - Detected by Pingoru
- Sep 03, 2026, 05:11 AM UTC
- Resolved
- Sep 04, 2026, 02:45 PM UTC
- Duration
- 1d 9h
Affected: BankID Signing (Norway)
Timeline · 21 updates
Read the full incident report →
- Detected by Pingoru
- Aug 26, 2026, 01:45 PM UTC
- Resolved
- Aug 26, 2026, 02:35 PM UTC
- Duration
- 49m
Affected: Idura Signatures
Timeline · 3 updates
-
monitoring Aug 26, 2026, 02:23 PM UTC
Our main TSA is experiencing performance issues. We have a fallback TSA in place, however, in case of long running/large signature orders, the request might fail. Retrying should work.
-
monitoring Aug 26, 2026, 02:29 PM UTC
The main TSA performance seem to have stabilized. We are continuing to monitor the situation.
-
resolved Aug 26, 2026, 03:09 PM UTC
Performance has normalized.
Read the full incident report →
- Detected by Pingoru
- Aug 22, 2026, 05:49 AM UTC
- Resolved
- Aug 22, 2026, 06:27 AM UTC
- Duration
- 38m
Affected: Swedish Address Lookup
Timeline · 3 updates
-
investigating Aug 22, 2026, 05:49 AM UTC
We are currently seeing a high error rate for Swedish Address Lookup via SPAR. We are investigating.
-
identified Aug 22, 2026, 06:02 AM UTC
The issue appears to be a network-layer/firewall block of requests to SPAR, we are trying to get in contact with SPAR.
-
resolved Aug 22, 2026, 06:27 AM UTC
SPAR became operational again around 8:00. Exact root cause still unknown.
Read the full incident report →
- 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
-
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.
-
monitoring Jul 17, 2026, 01:03 PM UTC
MitID error rate is back to normal
-
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 →
- 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
-
investigating Jul 16, 2026, 08:58 AM UTC
We have been alerted and are investigating the issue.
-
investigating Jul 16, 2026, 09:04 AM UTC
Issue only related to the idura.broker domains
-
investigating Jul 16, 2026, 09:31 AM UTC
Global CloudFront issues. Investigating workaround remediation.
-
investigating Jul 16, 2026, 09:54 AM UTC
We have located a workaround and are actively working on getting it released.
-
investigating Jul 16, 2026, 10:49 AM UTC
We are still working on resolving the issue.
-
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.
-
monitoring Jul 16, 2026, 11:33 AM UTC
Error rate has dropped to 0%, we will continue to monitor
-
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 →
- Detected by Pingoru
- Jul 16, 2026, 07:50 AM UTC
- Resolved
- Jul 16, 2026, 07:50 AM UTC
- Duration
- —
Timeline · 1 update
-
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 →
- Detected by Pingoru
- Jun 10, 2026, 11:15 AM UTC
- Resolved
- Jun 10, 2026, 02:41 PM UTC
- Duration
- 3h 25m
Affected: BankID Signing (Norway)
Timeline · 9 updates
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 →
