The system is experiencing issues

Past Incidents

10th October 2024

VPSCheap outage

VPSCheap nodes are currently offline, we're replacing failed PDU.

  • The issue is now resolved.

    • 9th October 2024

    d1277.dxb3.mysecurecloudhost.com

    We are investigating an issue on d1277.dxb3.mysecurecloudhost.com.

    2nd October 2024

    RFO - Shared Servers Outage

    Across our systems we operate real-time kernel patching for urgent vulnerabilities with the KernelCare system. These patches are rolled out in stages across our systems. An update released on October 1st caused a number of our servers to crash and require a reboot. Apologies for the disruption. As soon as the cause was isolated the bad patch was removed. The affected servers were:

    s1012.use1.mysecurecloudhost.com s1013.use1.mysecurecloudhost.com s1014.use1.mysecurecloudhost.com s1022.use1.mysecurecloudhost.com s1024.use1.mysecurecloudhost.com s1025.use1.mysecurecloudhost.com s1040.use1.mysecurecloudhost.com s1043.use1.mysecurecloudhost.com s1049.use1.mysecurecloudhost.com s1055.use1.mysecurecloudhost.com s1057.use1.mysecurecloudhost.com s1058.use1.mysecurecloudhost.com s1062.use1.mysecurecloudhost.com s1066.use1.mysecurecloudhost.com s1072.use1.mysecurecloudhost.com s1073.use1.mysecurecloudhost.com s1080.usc1.mysecurecloudhost.com s1081.usc1.mysecurecloudhost.com s1082.usc1.mysecurecloudhost.com s1083.usc1.mysecurecloudhost.com s1086.usc1.mysecurecloudhost.com s1087.usc1.mysecurecloudhost.com s1088.usc1.mysecurecloudhost.com s1089.usc1.mysecurecloudhost.com s1094.usc1.mysecurecloudhost.com s1096.usc1.mysecurecloudhost.com s1099.usc1.mysecurecloudhost.com s1100.usc1.mysecurecloudhost.com s1104.usc1.mysecurecloudhost.com s1105.usc1.mysecurecloudhost.com s1110.use1.mysecurecloudhost.com s1111.use1.mysecurecloudhost.com s1112.use1.mysecurecloudhost.com s1113.use1.mysecurecloudhost.com s1114.use1.mysecurecloudhost.com s1115.use1.mysecurecloudhost.com s1116.usc1.mysecurecloudhost.com s1235.usc1.mysecurecloudhost.com s1246.usc1.mysecurecloudhost.com s1295.sgp1.mysecurecloudhost.com s1296.sgp1.mysecurecloudhost.com s1301.sgp1.mysecurecloudhost.com s1302.sgp1.mysecurecloudhost.com s1305.sgp1.mysecurecloudhost.com s1306.sgp1.mysecurecloudhost.com s1309.sgp1.mysecurecloudhost.com s1310.sgp1.mysecurecloudhost.com s1314.sgp1.mysecurecloudhost.com s1316.sgp1.mysecurecloudhost.com s1320.sgp1.mysecurecloudhost.com s1321.sgp1.mysecurecloudhost.com s1323.sgp1.mysecurecloudhost.com s1324.sgp1.mysecurecloudhost.com s1327.sgp1.mysecurecloudhost.com s1351.use1.mysecurecloudhost.com s1354.use1.mysecurecloudhost.com s1362.use1.mysecurecloudhost.com s2960.sgp1.stableserver.net s2962.sgp1.stableserver.net s2967.sgp1.stableserver.net s2968.sgp1.stableserver.net s2969.sgp1.stableserver.net s3281.sgp1.stableserver.net

    s784.bom1.mysecurecloudhost.com - DDoS Attack

    The server is experiencing a DDoS attack. Our scrubber is already in place on the route, and our team is currently checking.

  • The attack has stopped, the DDoS scrubbers were mitigating majority of the attack, however some flood traffic was still making it through affecting connectivity for periods of time.

    We are analysing the attack pattern to better mitigate this type of DDoS attack in the future.