Server Unreachable (Investigating)
  • Priority - Critical
  • Affecting Server - SSDSB06
  • 19:01 Switch has been replaced but server did not get back online; DC personal dispatched to the server for further investigation.
    19:25 There is a secondary issue with the network configuration which is not operating as it should be, they are working on this. 
    20:42  The DC techs are still working on the issue. Once we have more information we will update it here.
    20:57 Escalated as per instructions to DC management (informative to keep everyone in the loop) 
    21:25 after the broken switch there is still something not functioning correctly in the network; the network technicians are looking into the issue once more. 
    23:01 server was briefly online but in a wrong kernel version which caused other issues; we are still working on the issue. 

    23:18 Status Update: this issue started with a network issue in the DC, that is what we know, but unfortunately this may have started a list of chain reactions ; somewhere something else did go wrong; we where able to briefly start the system with an old centos kernel; which fortunately means that we can access the data if needed, the bad thing is that we where still not able to get the server working; we are trying to resolve this but for this we need a so called rescue system; a system which boots up a Linux OS which allows us to manually mount the server and boot it up to see what is happening as we are sitting behind the console. But also this functionality is not working. We keep working on this issue. If we can not resolve this issue by morning we will be forced to install a new server and start restores; something we would like to avoid. Our team is working hard to resolve the issue the soonest possible. 

  • Date - 16/02/2019 20:28
  • Last Updated - 17/02/2019 00:04
SSDSB04 Server Outage (Investigating)
  • Priority - Critical
  • Affecting Server - SSDSB06
  • Installation of a patch to prevent the Intel meltdown bug has resulted in the server crashing & it being unable to boot up.

    12:21am As SSDSB04 server will not even load past the initial boot screen we are currently restoring all accounts to a new server - SSDSB06.

    Our nameserver IPs have been updated:

    ns1.affordahost.net 62.138.16.101
    ns2.affordahost.net 198.20.101.186

    If you use your own custom nameservers you will need to update them to these IPs to restore access to your website.


  • Date - 05/01/2018 21:00
  • Last Updated - 06/01/2018 00:48

Server Status

Below is a real-time overview of our servers where you can check if there's any known issues.

Server Name HTTP FTP POP3 PHP Info Server Load Uptime
SSDSB06 PHP Info
UK1 PHP Info
UK2 PHP Info