Idura Incident History

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.

MitID error rate is back to normal

We are seeing a high error rate from MitID endpoints. This is affecting an increasing number of logins. We are investigating.

A problem with AWS CloudFront Origins resulted in requests towards Signatures were not being able to hit our API.

AWS has fixed the issue on their end before we managed to release our mitigation. Our mitigation took longer than initially expected.

Error rate has dropped to 0%, we will continue to monitor

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.

We are still working on resolving the issue.

We have located a workaround and are actively working on getting it released.

Global AWS CloudFront issues. Investigating workaround remediation. https://health.aws.amazon.com/health/status

Issue only related to the idura.broker domains

We have been alerted and are investigating the issue.