Resolved -
No further issues have been encountered
Apr 13, 09:19 UTC
Update -
Full CDN redundancy has been restored as planned, and behaviour is under close monitoring. If no issues are encountered, we will close this issue.
Apr 8, 14:43 UTC
Update -
Our third party CDN provider has confirmed that a fix has been deployed and we are in the process of testing this before planning to restore full CDN redundancy tomorrow at around 10:00 UTC. Our team will be monitoring closely throughout this period.
Apr 7, 14:52 UTC
Update -
We are continuing to work with our CDN providers to troubleshoot the issue before restoring full CDN redundancy.
To provide some more details - the first reports of the issue were received on 4th March, with further reports on 9th-12th March. We were able to recreate and identify the issue on 16th March, with a mitigation put in place around 12:25 UTC on 16th March.
Mar 19, 10:20 UTC
Monitoring -
We identified an issue that affected the processing of some OCSP requests.
Mitigation steps have been implemented, and the service is currently operating normally. We are continuing to monitor the situation to ensure ongoing stability.
Mar 17, 02:02 UTC