Dododox: Planned Maintenance

The server Dododox ( / will be rebooted at 8PM this Friday, 1 April 2022. While the server is rebooting, all websites and emails will be offline for up to 30 minutes.

We are rebooting the server in order to enable the new AccelerateWP and Smart Advice tools from CloudLinux.

Smart Advice is a new feature of the existing X-Ray tool in your cpanel that is designed to find and propose solutions to fix performance issues and speed up the performance of your WordPress website.

AccelerateWP is a suite of optimisation modules for WordPress. It allows you to find and troubleshoot performance issues at both the server and WordPress level.

If you’d like to find out more, please read the blog post at CloudLinux.

We will be beta testing these tools on Dododox before possibly rolling them out across our WordPress MAX server fleet.

Bopster: Planned Maintenance

One of the case fans on the server Bopster ( has failed, and this is causing the server to run hotter than normal.
To prevent hardware failure, and possible data loss, we have scheduled a fan replacement for Tuesday 29 March 2021 at 5:30PM

The server will be powered down at 5:20PM and will be offline for up to an hour for the fan replacement. During this time, all websites and email accounts hosted on Bopster will be offline.

We apologise for the inconvenience this will cause you.


Maintenance has completed successfully, and Bopster is back online without any issues.

Skizzle Offline

07:45AM There appears to be a networking issue with the server Skizzle ( / ) which has made it inaccessible. The datacentre technicians are currently working on the problem, but we do not have an ETR yet.

11:26AM Xneelo has FINALLY found and fixed the network problem, so everything should now be working as expected. Sincere apologies for the inconenience.

Connectivity problems

10:55 AM Xneelo appear to have fixed the network issue. Let’s hope it’s a permanent fix! Sincere apologies for the inconvenience this has caused affected clients.

08:20 AM Xneelo has confirmed that there is a problem in their Samrand datacentre, which they are working on:

08:04 AM The following servers are currently experiencing intermittent network connectivity problems:


We are investigating, and hope to have the problem fixed shortly.

Rhaegal High Load / Failure

09:46 We are seeing high loads on the server Rhaegal which is causing sites to time out. We are investigating and should have a fix soon.

10:04 We’ve have found the cause of the high load, and everything should be returning to normal with the next minute or so.

10:10 Our fix has not worked, so we are implementing another fix which requires a reboot of the server. All sites will be offline for at least the next 15 minutes while the server is rebooting.

10:45 Email sent to all clients on this server:

Dear client

The server Rhaegal which hosts the website for {DOMAIN} is offline. We have as yet been unable to find the root cause, but we suspect that it is a hardware failure. While the technicians investigate, we will begin restoring the {DOMAIN} website to the server Hoppler (IP address: ) in the event that the server Rhaegal cannot be restored to a working condition.

We will keep you updated while we work through this.

14:35 We are 30% through the restoration process. If your domain is not using our nameservers, please update its DNS to point to now.

15:30 We are still attempting to recover data from the crashed server, although the chances of that happening are not looking good. If we are unable to recover data from the server, then your email accounts and emails (which are never backed up by Texo) will be lost. As soon as your website is live again, please login to your cpanel and recreate any email accounts you need.

16:15 The restoration of websites to the new server is at 60% and should be done within another few hours

18:25 We have around 50 website left to restore

19:50 All websites have been restored to the new server. If you see any problems with your website, please submit a support ticket. If your domain is not using our nameservers, and you have not yet updated its A and WWW records to point to then please do so now.