Criipto Outage History

Criipto is up right now

Pingoru has recorded 53 incidents for Criipto: 31 in the last 12 months and 13 in the last 90 days.

Source: status.criipto.com

53incidents recorded
31last 12 months
13last 90 days
3 hourstypical duration
Incidents per month
048AprMayJunJulAugSepOct8
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct2%
Pingoru began tracking Criipto in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026317 of 720 (2%)
May 202621 of 744 (0%)
June 202624 of 720 (1%)
July 202634 of 744 (1%)
August 202622 of 744 (0%)
September 2026336 of 720 (5%)
October 2026812 of 514 (2%)

Incidents, newest first

Major October 19, 2026 Problems with cloud infrastructure 54m Danish Address Lookup, Idura Signatures, Swedish Address Lookup

Started Oct 19, 2026, 09:08 AM UTC· resolved Oct 19, 2026, 10:03 AM UTC

  1. investigating Oct 19, 2026, 09:08 AM UTC

    We are currently investigating this issue.

  2. monitoring Oct 19, 2026, 09:15 AM UTC

    API calls have normalized. We are awaiting provider confirmation that the issue has been resolved.

  3. resolved Oct 19, 2026, 10:03 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical October 12, 2026 Issues with Norwegian BankID and signing 2h 44m BankID OIDC (Norway), BankID Signing (Norway)

Started Oct 12, 2026, 10:44 AM UTC· resolved Oct 12, 2026, 01:28 PM UTC

  1. investigating Oct 12, 2026, 10:44 AM UTC

    Follow along at https://status.stoe.no/.

  2. monitoring Oct 12, 2026, 12:49 PM UTC

    Follow along at https://status.stoe.no/.

  3. resolved Oct 12, 2026, 01:28 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical October 9, 2026 Swedish BankID outage 25m BankID (Sweden)

Started Oct 09, 2026, 04:58 PM UTC· resolved Oct 09, 2026, 05:24 PM UTC

  1. investigating Oct 09, 2026, 04:58 PM UTC

    We see severely reduced authentication completions with Swedish BankID. We are investigating the root cause.

  2. monitoring Oct 09, 2026, 05:04 PM UTC

    Swedish BankID has confirmed that the root cause is an outage on their end. We are monitoring the situation. You can follow their investigation at https://status.bankid.com/incidents/y96hpkty3p55

  3. monitoring Oct 09, 2026, 05:12 PM UTC

    We are starting to see improvement and some authentications are now completing.

  4. monitoring Oct 09, 2026, 05:18 PM UTC

    We are seeing normal traffic patterns and are waiting for Swedish BankID to confirm that the outage is resolved.

  5. resolved Oct 09, 2026, 05:24 PM UTC

    Swedish BankID has now confirmed that the outage is resolved.

Read the full incident report →

Critical October 9, 2026 Problems with Norwegian BankID signing 1h 35m BankID Signing (Norway)

Started Oct 09, 2026, 10:04 AM UTC· resolved Oct 09, 2026, 11:39 AM UTC

  1. investigating Oct 09, 2026, 10:04 AM UTC

    All requests for BankID signing seems to fail.

  2. monitoring Oct 09, 2026, 11:30 AM UTC

    Service seems to have stabilized.

  3. resolved Oct 09, 2026, 11:39 AM UTC

    This incident has been resolved.

Read the full incident report →

Major October 7, 2026 Increased error rate on Norwegian BankID signing 39m BankID Signing (Norway)

Started Oct 07, 2026, 12:28 PM UTC· resolved Oct 07, 2026, 01:08 PM UTC

  1. investigating Oct 07, 2026, 12:28 PM UTC

    We see an increased error rate.

  2. investigating Oct 07, 2026, 12:36 PM UTC

    The error rate has further increased. Follow along at https://status.stoe.no/

  3. monitoring Oct 07, 2026, 12:51 PM UTC

    Error rate seem to have gone down. Follow along at https://status.stoe.no/.

  4. resolved Oct 07, 2026, 01:08 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical October 7, 2026 Dutch Idin not available 1h 16m iDIN (Netherlands)

Started Oct 07, 2026, 07:46 AM UTC· resolved Oct 07, 2026, 09:02 AM UTC

  1. monitoring Oct 07, 2026, 07:46 AM UTC

    Dutch Idin is not available due to an outage at the Idin provider.

  2. resolved Oct 07, 2026, 09:02 AM UTC

    The Idin provider has now resolved the issue.

Read the full incident report →

Critical October 5, 2026 Temporary closure of all CPR office access 2h 56m Danish Address Lookup

Started Oct 05, 2026, 07:17 AM UTC· resolved Oct 05, 2026, 10:14 AM UTC

  1. monitoring Oct 05, 2026, 07:37 AM UTC

    Due to an ongoing breach investigation conducted by the Danish CPR office, all private sector access to address lookups has been temporarily revoked. This is not due to a breach at Idura. See the CPR office status page at https://cprdkprod.statuspage.io/ for more details.

  2. monitoring Oct 05, 2026, 08:24 AM UTC

    Update on impact: The expected impact is that authentications still succeed and that ID tokens contain no address claims. If you are experiencing a different failure mode, please contact support.

  3. monitoring Oct 05, 2026, 10:02 AM UTC

    The CPR office reports that private sector address lookup access has been restored. We are monitoring to confirm, but expect that the incident will be resolved soon.

  4. resolved Oct 05, 2026, 10:14 AM UTC

    The CPR office has restored access and we have confirmed that address data is now being received again.

Read the full incident report →

Major October 1, 2026 BankID requests failing for many customers 1h 18m BankID OIDC (Norway)

Started Oct 01, 2026, 01:46 PM UTC· resolved Oct 01, 2026, 03:05 PM UTC

  1. 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

  2. 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.

  3. 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.

  4. 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 →

Minor September 25, 2026 Issues signing with Norwegian BankID 1h 27m BankID Signing (Norway)

Started Sep 25, 2026, 10:45 AM UTC· resolved Sep 25, 2026, 12:12 PM UTC

  1. investigating Sep 25, 2026, 10:49 AM UTC

    There are currently issues with signing using Norwegian BankID.

  2. monitoring Sep 25, 2026, 11:53 AM UTC

    Operations seem to have stabilized. We are monitoring.

  3. resolved Sep 25, 2026, 12:12 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 11, 2026 Signatures partially unavailable 38m

Started Sep 11, 2026, 12:57 PM UTC· resolved Sep 11, 2026, 01:35 PM UTC

  1. 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 Norwegian BankID signing is down 1d 9h BankID Signing (Norway)

Started Sep 03, 2026, 05:11 AM UTC· resolved Sep 04, 2026, 02:45 PM UTC

  1. investigating Sep 03, 2026, 05:16 AM UTC

    Norwegian BankID is currently experiencing issues with BankID CSC Signing, WYSIWYS, Timestamp in production resulting in a 100% impact

  2. identified Sep 03, 2026, 05:43 AM UTC

    The issue has been identified, and a fix is currently being implemented. The failure rate remains unchanged while mitigation efforts are ongoing.

  3. identified Sep 03, 2026, 06:02 AM UTC

    We are continuing to work on a fix for this issue.

  4. identified Sep 03, 2026, 06:45 AM UTC

    They are continuing to work on a fix for this issue.

  5. identified Sep 03, 2026, 07:29 AM UTC

    They are continuing to work on a fix for this issue.

  6. identified Sep 03, 2026, 08:17 AM UTC

    The issue has been identified, and a fix is currently being implemented. The failure rate remains unchanged while mitigation efforts are ongoing.

  7. identified Sep 03, 2026, 08:40 AM UTC

    They are continuing to work on a fix for this issue.

  8. identified Sep 03, 2026, 09:12 AM UTC

    They are continuing to work on a fix for this issue.

  9. identified Sep 03, 2026, 11:11 AM UTC

    They are continuing to work on a fix for this issue. Update will be provide the next update in 2 hours.

  10. identified Sep 03, 2026, 01:50 PM UTC

    A fix has been implemented for BankID Signing B2B and Qualified Timestamp, and both services are now operating normally. They are continuing to work on restoring the remaining affected services and will provide the next update in 2 hours.

  11. identified Sep 03, 2026, 06:44 PM UTC

    They are continuing to work on restoring the BankID CSC Signing and WYSIWYS services. They will provide a further update as more information becomes available.

  12. monitoring Sep 03, 2026, 06:53 PM UTC

    A fix has been implemented and we are monitoring the results.

  13. monitoring Sep 03, 2026, 06:53 PM UTC

    We are continuing to monitor for any further issues.

  14. identified Sep 03, 2026, 08:24 PM UTC

    They are continuing to work on restoring the BankID CSC Signing and WYSIWYS services. They will provide a further update as more information becomes available.

  15. identified Sep 04, 2026, 05:14 AM UTC

    They are continuing to work on restoring the BankID CSC Signing and WYSIWYS services. They will provide the next update in 2 hours.

  16. identified Sep 04, 2026, 07:18 AM UTC

    They are continuing to work on restoring the BankID CSC Signing and WYSIWYS services. They will provide the next update in 2 hours

  17. identified Sep 04, 2026, 10:17 AM UTC

    They are working intensively to restore the services and will provide the next update within two hours.

  18. identified Sep 04, 2026, 11:49 AM UTC

    A fix has been implemented, and mitigation efforts are underway to fully restore the affected services. Users may experience periodic instability until service restoration is complete.

  19. identified Sep 04, 2026, 02:18 PM UTC

    A fix has been implemented, and mitigation efforts are underway to fully restore the affected services. Users may experience periodic instability until service restoration is complete. They will provide the next update in 2 hours

  20. monitoring Sep 04, 2026, 02:47 PM UTC

    A fix has been implemented and we are monitoring the results.

  21. resolved Sep 04, 2026, 03:36 PM UTC

    The signing services (CSC & WYSIWYS) has been operating normally since 12:15 PM today. While the service is currently stable, we will continue to monitor it closely over the weekend and during the coming days.

Read the full incident report →

Minor August 26, 2026 Degraded performance for Signatures 49m Idura Signatures

Started Aug 26, 2026, 01:45 PM UTC· resolved Aug 26, 2026, 02:35 PM UTC

  1. 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.

  2. monitoring Aug 26, 2026, 02:29 PM UTC

    The main TSA performance seem to have stabilized. We are continuing to monitor the situation.

  3. resolved Aug 26, 2026, 03:09 PM UTC

    Performance has normalized.

Read the full incident report →

Critical August 22, 2026 High error rate for SPAR (Swedish Address Lookup) 38m Swedish Address Lookup

Started Aug 22, 2026, 05:49 AM UTC· resolved Aug 22, 2026, 06:27 AM UTC

  1. 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.

  2. 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.

  3. 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 →

Major July 17, 2026 High MitID error rate 1h 15m MitID (Denmark)

Started Jul 17, 2026, 12:46 PM UTC· resolved Jul 17, 2026, 02:01 PM UTC

  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 - signing issues 2h 52m Idura Signatures

Started Jul 16, 2026, 08:58 AM UTC· resolved Jul 16, 2026, 11:50 AM UTC

  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 →

Major July 16, 2026 Signatures down –

Started Jul 16, 2026, 07:50 AM UTC· resolved Jul 16, 2026, 07:50 AM UTC

  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 →

Critical June 10, 2026 Increased error rate for NO BankID Signing 3h 25m BankID Signing (Norway)

Started Jun 10, 2026, 11:15 AM UTC· resolved Jun 10, 2026, 02:41 PM UTC

  1. investigating Jun 10, 2026, 11:15 AM UTC

    We are seeing errors for 25% of requests to the Norwegian BankID Signing API, we are investigating.

  2. investigating Jun 10, 2026, 11:20 AM UTC

    All requests to Norwegian BankID Signing are now failing. We are investigating and have reached out to NO BankID

  3. investigating Jun 10, 2026, 11:24 AM UTC

    Norwegian BankID/Stø have received our support request - They report they are seeing issues and are looking into them.

  4. identified Jun 10, 2026, 11:36 AM UTC

    Norwegian BankID/Stø report that they have identified the issue and are working on a fix.

  5. identified Jun 10, 2026, 12:12 PM UTC

    Norwegian BankID/Stø have reported that they are continuing to work on a fix for this issue.

  6. identified Jun 10, 2026, 01:22 PM UTC

    Norwegian BankID have reported that they are continuing to work on a fix for this issue.

  7. identified Jun 10, 2026, 02:24 PM UTC

    Norwegian BankID have reported that they are continuing to work on a fix for this issue.

  8. monitoring Jun 10, 2026, 02:37 PM UTC

    Our monitoring shows less errors from Norwegian BankID Signing, we are waiting from official word from BankID.

  9. resolved Jun 10, 2026, 02:41 PM UTC

    Norwegian BankID has provided an update: "A fix has been implemented and we are monitoring the results."

Read the full incident report →

Critical April 24, 2026 High error rate for Signatures 12h 24m Idura Signatures, BankID Signing (Norway)

Started Apr 24, 2026, 06:09 PM UTC· resolved Apr 25, 2026, 06:34 AM UTC

  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 2h 24m Danish Address Lookup

Started Apr 10, 2026, 07:42 AM UTC· resolved Apr 10, 2026, 10:06 AM UTC

  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 1h 46m Idura Verify Authentication Core, Idura Signatures

Started Apr 07, 2026, 12:14 PM UTC· resolved Apr 07, 2026, 02:01 PM UTC

  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 3h 11m Idura Verify Authentication Core

Started Mar 31, 2026, 09:34 AM UTC· resolved Mar 31, 2026, 12:46 PM UTC

  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 5h 2m MitID (Denmark)

Started Mar 31, 2026, 07:24 AM UTC· resolved Mar 31, 2026, 12:27 PM UTC

  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 56m MitID (Denmark)

Started Feb 27, 2026, 10:30 AM UTC· resolved Feb 27, 2026, 11:27 AM UTC

  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 4m Idura Signatures

Started Jan 22, 2026, 09:40 AM UTC· resolved Jan 22, 2026, 09:45 AM UTC

  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 3h 22m MitID (Denmark)

Started Jan 12, 2026, 08:46 AM UTC· resolved Jan 12, 2026, 12:09 PM UTC

  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 →