Medius experienced a major incident on October 29, 2025 affecting Cloud02 and Cloud03 and 1 more component, lasting 16h 44m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 29, 2025, 04:15 PM UTC
We are currently investigating an issue with resource loading from our Content Delivery Network (CDN) in Microsoft Azure. This may cause problems accessing or loading parts of the application. Our engineering team is working with priority to identify the root cause and restore full functionality. Users may experience degraded performance or failures when opening the application until this is resolved.
- identified Oct 29, 2025, 05:04 PM UTC
Our team has identified the issue and is actively implementing a workaround to restore stable access to the application, while Microsoft works on a permanent fix on their side.
- identified Oct 29, 2025, 05:46 PM UTC
We take the performance and reliability of our services seriously, and we regret to inform you of an incident impacting all Clouds within our environment. The issue stems from a partial content disruption related to our content delivery network (CDN) provider. While our team has implemented an effective workaround to mitigate the impact, users may notice slightly increased load times. Rest assured, this temporary change should not result in significant performance issues. The fix for the underlying concern has been identified and is currently pending delivery from our CDN provider. We remain actively engaged with the provider to expedite resolution, ensuring normal operations are restored swiftly and seamlessly. Continuous improvement remains our priority, and we are determined to minimize disruptions and uphold the high standards you expect from us. Thank you for your understanding and patience as we work diligently to resolve this matter. We will continue to keep you updated and appreciate your confidence in us during this time. Please do not hesitate to contact us or any further disruptions noticed
- identified Oct 29, 2025, 05:51 PM UTC
We are actively monitoring introduced fix and testing functionality. Still awaiting permanent fix from our provider.
- monitoring Oct 29, 2025, 05:52 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Oct 30, 2025, 08:59 AM UTC
This incident has been resolved.