Resolved after 2 hours 52 minutes, affecting Idura Signatures, on July 16, 2026.
AWS has fixed the issue on their end before we managed to release our mitigation. Our mitigation took longer than initially expected.
Other major vendors with incidents that started within 30 minutes of this one
Affected components
Update timeline
- 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.
Your product runs on more than Criipto
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services