This issue is now fully resolved, though we are continuing to monitor this closely. Our sincere apologies for the inconvenience this has caused.
Capulet is now back online. We have completed the networking configuration and verified that the server is fully operational and reachable.
There are still several aspects of this incident that we are working to review and fully understand, and we will share a fuller update in due course.
In the meantime, if you notice anything not behaving as expected, please let us know and we will look into it straight away. Thank you for your patience throughout.
We have successfully brought the server back up on alternative hardware, and it is now powered on and running. Our engineers are completing the final networking configuration to bring it fully back into service, which we expect to finish shortly. We will confirm here as soon as the server is fully restored and reachable. Thank you for your continued patience.
A further update on this server. We are continuing to work through all recovery options to restore service, but as this is an issue at the hardware level, it is taking some time.
For context, we have experienced multiple near-concurrent hardware failures affecting different servers. Some have been recovered, while others have not yet, and each is behaving differently, so we are working through them individually to find the right recovery path. Alongside this, we are working with our data centre to understand the underlying cause.
This server remains a priority and our engineers are actively working to restore it.
This server is currently unavailable due to a physical infrastructure issue at our London data centre. Our engineers are investigating as a top priority and are working to identify and resolve the cause.
We don’t yet have an estimated time for restoration. Given the nature of the issue, we want to be upfront that this may be an extended incident. Restoring service safely is our focus.
We’re sorry for the disruption and appreciate your patience, we will keep you updated as work progresses.
We have identified an issue with the web service on Capulet. We are currently investigating.