ResDiary experienced a critical incident on June 11, 2025 affecting UK/Europe and API and 1 more component, lasting 6h 24m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 11, 2025, 03:52 AM UTC
We are currently investigating this issue.
- identified Jun 11, 2025, 05:53 AM UTC
The issue has been identified and a fix is being implemented.
- identified Jun 11, 2025, 07:05 AM UTC
We are continuing to work on a fix for this issue.
- identified Jun 11, 2025, 07:34 AM UTC
We are continuing to work on a fix for this issue.
- identified Jun 11, 2025, 08:54 AM UTC
We've identified a fix and are in the process of deploying it.
- monitoring Jun 11, 2025, 09:24 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 11, 2025, 10:17 AM UTC
This incident has been resolved.
- postmortem Jun 16, 2025, 01:50 PM UTC
We were alerted to degraded performance across our services at 04:37am on June 11th 2025. Our Engineers responded to the alert immediately, with additional engineers being called in at 05:52am. A full investigation has been completed into the cause, and steps needed to safeguard our services moving forward: _Root Cause_ An Azure CDN endpoint that our system is reliant on failed, without any warning from the 3rd party. On 11th of June 2025 the Let’s Encrypt SSL certificate for \`\*.azureedge.net\` expired leading all secure traffic to be blocked. The PowerShell command “Install-PackageProvider” which was used in a start-up script for the application uses the CDN endpoint "[onegetcdn.azureedge.net](https://onegetcdn.azureedge.net/)", which was impacted by the expired SSL certificate. This was the root cause of the incident. _Corrective actions Taken_ We are removing any instances of the Install-PackageProvider command in our scripts and migrating them to [AnyPackage](https://github.com/anypackage/anypackage) \(Install-Module\) which is more actively maintained. Measures are also being taken to improve pipeline build times. The ultimate goal to safeguard our services is to re-platform away from VMSS, which is currently being investigated and planned. We sincerely apologise for the disruption to service experienced, and will take every precaution and measure needed to avoid such incidents moving forward. Thanks, ResDiary.