Critical incident

Codeweavers: System Availability

Affected: Codeweavers Platform

Current status of Codeweavers: Operational — live Codeweavers status

Timeline

1. Sep 14, 2026, 15:39 UTC
   investigating
   Dear Clients, We wish to inform you that we are currently experiencing a situation affecting the performance of our Codeweavers Platform. Users may encounter slower response times and reduced functionality. For example, some features may take longer to load than usual. Our team at Codeweavers Technical Support is actively investigating the issue to restore standard service levels as quickly as possible. We understand the inconvenience this may cause and appreciate your patience. Further updates will be provided once our investigation is complete. Thank you for your understanding. Kind Regards, The Codeweavers Technical Support Team
2. Sep 14, 2026, 15:54 UTC
   investigating
   Dear Clients, We are currently aware of an issue affecting some of our services and are actively investigating the cause. Initial indications suggest this may be related to a wider network connectivity issue within one of our external infrastructure providers. Their technical teams are currently working to identify the root cause and restore normal service as quickly as possible. Customers may experience intermittent service disruptions or an inability to access certain services while investigations are ongoing. We are monitoring the situation closely and working with our suppliers to minimise impact. Further updates will be provided as soon as more information becomes available. We apologise for any inconvenience caused and appreciate your patience. Kind Regards, The Codeweavers Technical Support Team
3. Sep 14, 2026, 16:19 UTC
   identified
   Dear Clients, We are continuing to investigate an issue affecting access to some of our services. Our teams remain engaged with the external infrastructure provider and are actively monitoring the situation while exploring any possible mitigation measures on our side. At this stage, there is no significant change to report, but our investigation is ongoing and we will provide further updates as soon as more information becomes available. We apologise for the continued disruption and appreciate your patience. Further updates will be posted here as they become available.
4. Sep 14, 2026, 16:51 UTC
   identified
   Dear Clients, We continue to work closely with our infrastructure provider regarding the ongoing service disruption. Based on our investigation to date, we have found no evidence of an issue within the Codeweavers platform itself, and current indications point to an issue within an upstream provider's environment. Progress has been made towards resolution, however some disruption remains while remediation work continues. We remain engaged with the provider's technical teams and are closely monitoring the situation as work progresses. We appreciate your continued patience and understanding. Further updates will be provided as soon as there are any significant developments. Kind Regards, The Codeweavers Technical Support Team
5. Sep 14, 2026, 17:10 UTC
   resolved
   Dear Clients, We are pleased to confirm that the issue affecting access to some of our services has now been resolved and service has been restored. Following remediation activity, services have returned to normal operation and we will continue to monitor the platform to ensure ongoing stability. We sincerely apologise for the disruption caused and would like to thank you for your patience and understanding while this issue was investigated and resolved. A root cause analysis will being undertaken, and we will provide a further update once this has been completed. Kind Regards, The Codeweavers Technical Support Team
6. Sep 16, 2026, 13:43 UTC
   postmortem
   Between approximately 16:29 and 18:00 BST, Codeweavers services were unavailable to most users. **Root cause** The incident was triggered by a network failure at an upstream provider to our data centre partner, which affected inbound and outbound traffic to parts of the internet. The loss of connectivity also affected some Codeweavers services, which required action by our infrastructure team to restore. **Impact** During this period, most users were unable to access Codeweavers services, and connections from our platform to third-party services were also disrupted. **Timeline \(BST\)** 16:29: Upstream network provider issue begins, disrupting traffic to and from our data centre. 16:39: Our teams identify the disruption and publish the first status update. 16:54: Cause narrowed to network connectivity at an external infrastructure provider. 17:19: Ongoing work with our data centre partner to restore connectivity. 17:45: Upstream connectivity restored; our infrastructure team begins restoring affected services. 17:59: Services restored. 18:10: Service stability confirmed and incident resolved. **Our response and next steps** * Our teams detected the disruption and began investigating ahead of any notification from our provider, and the first customer update was published within ten minutes of the issue starting. * This incident has been formally raised with our data centre partner. * Our migration to cloud infrastructure, currently in progress, is designed to provide greater network resilience than our current data centre arrangements. This concludes our investigation into this incident. We apologise for the disruption and thank you for your patience. Kind Regards, The Codeweavers Technical Support Team

Updates as published by Codeweavers (original).