Criipto experienced a critical incident on June 18, 2026 affecting Idura Signatures, lasting 11m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- 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.