Is Criipto down?
Last checked 6m agoNo incidents right now.
Criipto is operational right now. Last checked 6m ago; the most recent incident resolved 13d ago.
Real-time Criipto status, recent outages, and incident history — pulled directly from Criipto's official status page at https://status.criipto.com every 5 minutes. Pingoru tracks 16 Criipto services and has captured 8 incidents in the last 90 days (99.37% uptime). Get email, Slack, Discord, or webhook alerts the moment Criipto reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- 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.
Latest: 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 add…
-
-
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.
Latest: A problem with AWS CloudFront Origins resulted in requests towards Signatures were not being able to hit our API.
-
- 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.
Latest: AWS has fixed the issue on their end before we managed to release our mitigation. Our mitigation took longer than initially expected.
-
- Idura Signatures
Timeline · 3 updates
- identified · Jun 18, 2026, 03:12 PM UTC
We are seeing an issue with signatures after deploying a new release to our Azure hosted endpoints. We are rolling back the release as fast as possible. Our AWS hosted endpoint: https://docs.idura.app/signatures/graphql/endpoints/ appears unaffected.
- monitoring · Jun 18, 2026, 03:15 PM UTC
The latest release has now been rolled back and errors have stopped. We will be investigating why this error was not caught in preproduction.
- resolved · Jun 18, 2026, 03:23 PM UTC
The release issue did not affect end user signing, it only affected the closing of signature orders. We did not catch this in pre-release QA as closing was only tested against our AWS based hosting platform. We have amended our QA procedure and automated E2E tests to make sure both signing and closing are testing against both hosting platforms.
Latest: The release issue did not affect end user signing, it only affected the closing of signature orders. We did not catch this in pre-release QA as closing was only tested against our …
-
- BankID Signing (Norway)
Timeline · 9 updates
- 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.
- 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
- 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.
- identified · Jun 10, 2026, 11:36 AM UTC
Norwegian BankID/Stø report that they have identified the issue and are working on a fix.
- 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.
- identified · Jun 10, 2026, 01:22 PM UTC
Norwegian BankID have reported that they are continuing to work on a fix for this issue.
- identified · Jun 10, 2026, 02:24 PM UTC
Norwegian BankID have reported that they are continuing to work on a fix for this issue.
- 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.
- 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."
Latest: Norwegian BankID has provided an update: "A fix has been implemented and we are monitoring the results."
-
See the full Criipto outage history
2 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Criipto outage history →Or sign up free to get alerts when Criipto breaks · 10 free monitors · No credit card
- High MitID error rate ResolvedStarted Jul 17, 2026, 12:46 PM UTC · Resolved Jul 17, 2026, 02:01 PM UTC · 1h 15m
- Signatures down ResolvedStarted Jul 16, 2026, 11:52 AM UTC · Resolved Jul 16, 2026, 07:50 AM UTC · —
- Signatures - signing issues ResolvedStarted Jul 16, 2026, 09:31 AM UTC · Resolved Jul 16, 2026, 11:50 AM UTC · 2h 18m
- Signatures down ResolvedStarted Jun 18, 2026, 03:12 PM UTC · Resolved Jun 18, 2026, 03:23 PM UTC · 11m
- Started Jun 10, 2026, 11:15 AM UTC · Resolved Jun 10, 2026, 02:41 PM UTC · 3h 25m
- Started May 21, 2026, 09:14 AM UTC · Resolved May 21, 2026, 10:08 AM UTC · 53m
- Signatures down ResolvedStarted May 06, 2026, 09:27 AM UTC · Resolved May 06, 2026, 09:02 AM UTC · —