The system is experiencing issues
Maintenance
Server Migrations - Amsterdam & Frankfurt

We are in the process of migrating our Frankfurt and Amsterdam servers to our own network. These will take place throughout April/May, from 4pm UTC each day except weekends where migrations will operate 24/7. Large accounts which are split to different new servers will be moved in advance.

For advanced users not using our DNS - there will be a new IP address. As with other migrations the old IP will continue to proxy HTTP requests for 1 week. The old server hostname will be repointed.

Larger hosting accounts will be migrated to separate servers to balance our systems. In these cases we will send a support ticket to you directly with further details.

Please also ensure any large accounts adhere to our fair usage guidelines.

In Progress:

Completed:

  • s1243.fra7 - s2898.fra1.stableserver.net - 192.250.229.27
  • s1369.fra7 - s2899.fra1.stableserver.net - 192.250.229.28
  • s1095.fra7 - s2892.fra1.stableserver.net - 192.250.229.24
  • s843.fra7 - s2872.fra1.stableserver.net - 192.250.229.19
  • s1141.fra7 - s2897.fra1.stableserver.net - 192.250.229.26
  • s1011.fra7 - s2873.fra1.stableserver.net - 192.250.229.20
  • s542.fra6 - s2901.fra1.stableserver.net - 192.250.229.30
  • s510.ams8 - s2909.fra1.stableserver.net - 192.250.229.37
  • s684.fra8 - s2907.fra1.stableserver.net - 192.250.229.36
  • s530.ams8 - s2910.fra1.stableserver.net - 192.250.229.38

The upcoming migration dates and new IPs are below.

Please note - due to hardware delivery delays we have needed to reschedule these migrations until June. We will send a further update nearer the time. Apologies for the delay.

  • s497.fra6 - s2900.fra1.stableserver.net - 192.250.229.29
  • s586.fra6 - s2902.fra1.stableserver.net - 192.250.229.31
  • s593.fra6 - s2903.fra1.stableserver.net - 192.250.229.32
  • s605.fra8 - s2904.fra1.stableserver.net - 192.250.229.33
  • s614.fra6 - IP TBC
  • s618.fra8 - s2906.fra1.stableserver.net - 192.250.229.35
  • s934.ams9 - IP TBC
Server Upgrades - Canada

We are upgrading all servers in our datacentre to new NVMe hardware. At the same time we are also updating the operating systems which have now reached end of life.

30th May delayed

  • dprhcp170:Old IP:108.60.24.81. New hostname:s2934.can1.stableserver.net,New IP:192.250.237.68
  • dprhcp008:Old IP:66.226.137.1. New hostname:s2934.can1.stableserver.net,New IP:192.250.237.68
  • dprhcp005:Old IP:66.226.128.1. New hostname:s2934.can1.stableserver.net,New IP:192.250.237.68
  • dprhcp163:Old IP:108.60.23.11. New hostname:s2933.can1.stableserver.net,New IP:192.250.237.67
  • dprhcp002:Old IP:66.226.146.1. New hostname:s2933.can1.stableserver.net,New IP:192.250.237.67
  • dprhcp004:Old IP:66.226.150.1. New hostname:s2933.can1.stableserver.net,New IP:192.250.237.67
  • dprhcp003:Old IP:66.226.148.1. New hostname:s2933.can1.stableserver.net,New IP:192.250.237.67
  • dprhcp159:Old IP:108.60.21.51. New hostname:s2933.can1.stableserver.net,New IP:192.250.237.67

31st May delayed

  • dprhcp210:Old IP:69.161.149.1. New hostname:s2932.can1.stableserver.net,New IP:192.250.237.66
  • dprhcp253:Old IP:69.161.159.41.New hostname:s2932.can1.stableserver.net,New IP:192.250.237.66
  • dprhcp211:Old IP:69.161.150.1. New hostname:s2931.can1.stableserver.net,New IP:192.250.237.65
  • dprhcp154:Old IP:108.60.21.1. New hostname:s2931.can1.stableserver.net,New IP:192.250.237.65
  • dprhcp209:Old IP:69.161.148.1. New hostname:s2930.can1.stableserver.net,New IP:192.250.237.64
  • dprhcp007:Old IP:66.226.134.1. New hostname:s2930.can1.stableserver.net,New IP:192.250.237.64
  • dprhcp310:Old IP:108.60.13.41. New hostname:s2928.can1.stableserver.net,New IP:192.250.237.63
  • dprhcp308:Old IP:108.60.13.21. New hostname:s2928.can1.stableserver.net,New IP:192.250.237.63

1st June delayed

  • dprhcp252:Old IP:69.161.159.21.New hostname:s2927.can1.stableserver.net,New IP:192.250.237.62
  • dprhcp208:Old IP:69.161.147.1. New hostname:s2927.can1.stableserver.net,New IP:192.250.237.62
  • dprhcp302:Old IP:69.161.142.11.New hostname:s2926.can1.stableserver.net,New IP:192.250.237.61
  • dprhcp166:Old IP:108.60.24.1. New hostname:s2926.can1.stableserver.net,New IP:192.250.237.61
  • dprhcp303:Old IP:69.161.142.21.New hostname:s2925.can1.stableserver.net,New IP:192.250.237.60
  • dprhcp157:Old IP:108.60.21.31. New hostname:s2925.can1.stableserver.net,New IP:192.250.237.60
  • dprhcp160:Old IP:108.60.21.61. New hostname:s2925.can1.stableserver.net,New IP:192.250.237.60

2nd June delayed

  • dprhcp251:Old IP:69.161.159.1.New hostname:s2924.can1.stableserver.net,New IP:192.250.237.59
  • dprhcp307:Old IP:108.60.13.11.New hostname:s2924.can1.stableserver.net,New IP:192.250.237.59
  • dprhcp306:Old IP:108.60.13.1. New hostname:s2924.can1.stableserver.net,New IP:192.250.237.59
  • dprhcp167:Old IP:108.60.24.21.New hostname:s2923.can1.stableserver.net,New IP:192.250.237.58
  • dprhcp155:Old IP:108.60.21.11.New hostname:s2923.can1.stableserver.net,New IP:192.250.237.58
  • dprhcp201:Old IP:108.60.22.1. New hostname:s2923.can1.stableserver.net,New IP:192.250.237.58
  • dprhcp156:Old IP:108.60.21.21.New hostname:s2923.can1.stableserver.net,New IP:192.250.237.58

3rd June delayed

  • dprhcp301:Old IP:69.161.142.1. New hostname:s2922.can1.stableserver.net,New IP:192.250.237.57
  • dprhcp203:Old IP:108.60.22.21. New hostname:s2922.can1.stableserver.net,New IP:192.250.237.57
  • dprhcp165:Old IP:108.60.23.31. New hostname:s2922.can1.stableserver.net,New IP:192.250.237.57
  • dprhcp309:Old IP:108.60.13.31. New hostname:s2921.can1.stableserver.net,New IP:192.250.237.56
  • dprhcp158:Old IP:108.60.21.41. New hostname:s2921.can1.stableserver.net,New IP:192.250.237.56
  • dprhcp305:Old IP:69.161.142.41.New hostname:s2921.can1.stableserver.net,New IP:192.250.237.56
  • dprhcp304:Old IP:69.161.142.31.New hostname:s2920.can1.stableserver.net,New IP:192.250.237.55
  • dprhcp161:Old IP:108.60.21.71. New hostname:s2920.can1.stableserver.net,New IP:192.250.237.55

Completed

  • dhrhcp03:Old IP:64.151.204.1. New hostname:s2939.can1.stableserver.net,New IP:192.250.237.73
  • dprhcp162:Old IP:108.60.23.1. New hostname:s2935.can1.stableserver.net,New IP:192.250.237.69
  • dprhcp006:Old IP:66.226.131.1. New hostname:s2939.can1.stableserver.net,New IP:192.250.237.73
  • dprhcp164:Old IP:108.60.23.21. New hostname:s2939.can1.stableserver.net,New IP:192.250.237.73
  • dprhcp001:Old IP:66.226.144.1. New hostname:s2939.can1.stableserver.net,New IP:192.250.237.73
  • dprhcp202:Old IP:108.60.22.11. New hostname:s2939.can1.stableserver.net,New IP:192.250.237.73
  • dprhcp009:Old IP:209.151.16.1. New hostname:s2938.can1.stableserver.net,New IP:192.250.237.72
  • dprhcp205:Old IP:69.161.144.1. New hostname:s2938.can1.stableserver.net,New IP:192.250.237.72
  • dprhcp204:Old IP:108.60.22.31. New hostname:s2938.can1.stableserver.net,New IP:192.250.237.72
  • dprhcp010:Old IP:209.151.19.1. New hostname:s2937.can1.stableserver.net,New IP:192.250.237.71
  • dprhcp169:Old IP:108.60.24.61. New hostname:s2937.can1.stableserver.net,New IP:192.250.237.71
  • dprhcp207:Old IP:69.161.146.1. New hostname:s2936.can1.stableserver.net,New IP:192.250.237.70
  • dprhcp206:Old IP:69.161.145.1. New hostname:s2935.can1.stableserver.net,New IP:192.250.237.69
  • dprhcp012:Old IP:209.151.25.1. New hostname:s2937.can1.stableserver.net,New IP:192.250.237.71
  • dprhcp168:Old IP:108.60.24.41. New hostname:s2935.can1.stableserver.net,New IP:192.250.237.69
  • dprhcp011:Old IP:209.151.22.1. New hostname:s2936.can1.stableserver.net,New IP:192.250.237.70
Shared server maintenance in bom1

On 6th June from 10PM IST we will need to reboot some shared servers in our bom1 data centre to facilitate a hardware upgrade. Affected servers are:

s785.bom1.mysecurecloudhost.com s803.bom1.mysecurecloudhost.com s804.bom1.mysecurecloudhost.com

Actual downtime should be minimal and our support agents will be available to answer any queries.

Stickied Incidents

13th June 2024

Unstable network at s1305.sgp1.mysecurecloudhost.com

We are currently investigating network instability on s1305.sgp1.mysecurecloudhost.com. Further updates will be provided shortly. Thank you for your patience.

  • Issue has been sorted. We're apologize for the inconvenience.

  • 11th June 2024

    venomx90.stableserver.net

    venomx90.stableserver.net experiencing issues with mysql. We are looking into it

  • The issue now has been resolved. Apologize for the inconvenience

  • 10th June 2024

    WebHostPython - Service Interruption

    Update @ 6:05 AM UTC: Our upstream network provider has confirmed a faulty network device that affected the connection to our racks. They are currently working on replacing the device and migrating our networks accordingly. This action is expected to prevent similar issues in the future.


    Update @ 5:30 AM UTC: After escalating the issue to our upstream network provider, we are observing network recovery and all services should be back to an operational state. However, we are continuing a thorough investigation to identify the root cause. Apologies for the inconvenience


    Update @ 4:45 AM UTC: Our team identified a potential network outage originating from the data center, which impacted the racks. We have reached out to our upstream network provider for assistance.


    We are monitoring the following servers are currently out of service :

    • da71venom.stableserver.net
    • da73venom.stableserver.net
    • da75venom.stableserver.net
    • da77venom.stableserver.net
    • da79venom.stableserver.net
    • ns55.stableserver.net
    • ns62venom.stableserver.net
    • ns65v.stableserver.net
    • ns71venom.stableserver.net
    • ns75venom.stableserver.net
    • ns77venom.stableserver.net
    • ns79.stableserver.net
    • ns83venom.stableserver.net
    • venomx90.stableserver.net
    • pls5.stableserver.net
    • Some virtual servers (msnode instance)

    Our team are currently investigating on the following server. We will provide an update as soon as we get more information.


  • The issue now has been resolved. Apologize for the inconvenience.

  • 5th June 2024

    DDOS on 2900.fra1.stableserver.net, s2909.fra1.stableserver.net and s605.fra8.mysecurecloudhost.com

    Update @ 23:12 UTC Monday - All services are operating normally. We have paused migrations tonight and will migrate the rest of the accounts on Tuesday evening. We will send emails confirming the new IP first.


    UPDATE - s605.fra8.mysecurecloudhost.com's accounts will be getting migrated over to a new server later today/tonight.

    2900.fra1.stableserver.net, s2909.fra1.stableserver.net and s605.fra8.mysecurecloudhost.com were under DDOS attacks today. We have taken steps to mitigate the issue, but users may experience slower than normal services on those servers.

    30th May 2024

    s787.bom1.mysecurecloudhost.com

    We are currently experiencing significant slowness on s787.bom1.mysecurecloudhost.com. Our technical team is actively investigating the issue.

  • The issue now have been resolved. Apologize for the inconvenience.

  • 26th May 2024

    Dallas Datacentre - Power Outage

    SUMMARY (latest update 1 Jun 14:30 EST)

    On Monday 27th May, the database we use in Dallas experienced a power outage due to extreme storms that knocked out power for much of Texas, compounded by two generator failures and then by difficulties for datacentre staff to work through the weather on Memorial day. Because of the sudden power outage we experienced significant data corruption and multiple instances of hardware failure we have been working through. Apologies for the delays in restoring service and in customer support response during this time. The current remaining issues are as follows:

    We have some isolated virtual servers that have corrupted MySQL. If you have a virtual server with issues please raise a ticket to help us find the issue faster.

    For the server ns65v, all missing domains are now restored. We will be replacing the system with a new, hardware NVMe RAID server as soon as possible, and migrating away from the affected datacentre. We will send a further update as soon as possible regarding these long term fixes.


    Update Sat 1 June: Issues on da75 have been resolved.

    Update @ 18:30 EST May 31st - Some database tables on the da75 server have corrupted indexes which affects some operations. To prevent data loss we are currently fixing affected databases which requires rebuilding the MySQL install. This is in progress.

    Update @ 15:50 EST May 29th - All accounts are now re-created on ns65v. Home directory files and email data were retrieved from the old server however due to the hardware failure, we needed to restore database contents from a backup taken on May 23rd / 24th, before the power outage. Apologies for the extended outage here.

    Update @ 11:50 EST May 29th -Some msnode instances may have issues still, we are investigating.

    Update @ 09:50 EST May 29th - The restore of ns65v is ongoing.

    Update @ 23:00 EST May 28th - The ns65v server has been reinstalled and accounts are restoring from backups. Home directory and email data for 98% of accounts was stored on a separate partition to the failed disk, and is therefore unaffected. However, database data is needing to be restored from backups for all accounts which is taking some time. The failed disk was also sent to a specialist recovery firm earlier today, however due to continued severe storms in the Dallas area, the recovery has not yet begun due to power outages to that firm's own systems. Please note this is unrelated to our operations - at this time the supply to all 3 of our Dallas datacentres is operating normally.


    Update @ 14:00 EST May 28th - We are continuing to work on the ns65v server. The primary OS storage disk has failed and is being reinstalled. Once this is complete we will be able to assess further. We do have backups stored on an external server, if you need a copy of your account (we can also deploy this to a new server directly) please contact us.

    da77venom.stableserver.net is operating normally. Crashed database tables have been repaired.


    Update @ 10:05 EST May 28th - The server da77venom.stableserver.net is now back online.


    Update @ 09:16 EST May 28th: We have restored services on most of the affected systems. There are 2 servers with ongoing issues and we are working on getting them up and running.

    • da77venom.stableserver.net
    • ns65v.stableserver.net (Hardware failure)

    Update @ 06:45 EST May 28th: We are continuing to work through filesystem issues and replace failed hardware.

    Update @ 16:44 EST Monday 27th May: The datacentre experienced a full power outage due to storms in the area. Recovery efforts are ongoing however are hampered by the scale of the outage with limited datacentre staff available to repair essential systems. Many services are restored and we are working to repair filesystems and restore connectivity to one rack which suffered multiple hardware failures. Apologies for the extended downtime, we are working as fast as possible to restore all systems.


    The following servers are currently being affected by the issue:

    • da71venom.stableserver.net
    • da73venom.stableserver.net
    • da77venom.stableserver.net - This server is online however MySQL corruption is being repaired.
    • ns55.stableserver.net
    • ns62venom.stableserver.net
    • ns65v.stableserver.net
    • ns71venom.stableserver.net
    • ns75venom.stableserver.net
    • ns79.stableserver.net
    • ns83venom.stableserver.net
    • venomx90.stableserver.net
    • pls5.stableserver.net
    • Virtual servers (msnode instance)

    We are currently investigating the matter and are trying to rectify it as soon as possible.

  • da75venom.stableserver.net - we've identified the root cause with some databases, and are currently working on a fix.

  • Issue with venomx92.stableserver.net have been resolved.

  • Issue with venomx90.stableserver.net have been resolved.

    Update: The issue has reoccured, we are investigating.

    Update #2: The issue has been resolved.

  • Issues with pls5.stableserver.net have been resolved.

  • We have resolved the issues with the following servers - da71venom and da72venom.

  • Our Data Center experienced a total power loss, which affected all connected services. Power has been successfully restored, and we are in the process of recovering all servers impacted by the outage. However, one network segment remains offline due to a hardware failure. We are currently working on bringing replacement hardware online to resolve this issue as quickly as possible

  • We have resolved problems with the following servers: ns75venom.stableserver.net ns71venom.stableserver.net da79venom.stableserver.net

    We're working on bringing back the remaining servers.

  • 22nd May 2024

    Outbound mail issues in BOM1

    Update - This is now resolved.


    We are currently investigating reports of issues affecting outbound mail delivery to certain servers at our Mumbai (BOM1) site. Further updates will be provided as we make progress. Thank you for your patience.

    Past Incidents

    13th June 2024

    Unstable network at s1305.sgp1.mysecurecloudhost.com

    We are currently investigating network instability on s1305.sgp1.mysecurecloudhost.com. Further updates will be provided shortly. Thank you for your patience.

  • Issue has been sorted. We're apologize for the inconvenience.

  • 11th June 2024

    venomx90.stableserver.net

    venomx90.stableserver.net experiencing issues with mysql. We are looking into it

  • The issue now has been resolved. Apologize for the inconvenience

  • 10th June 2024

    WebHostPython - Service Interruption

    Update @ 6:05 AM UTC: Our upstream network provider has confirmed a faulty network device that affected the connection to our racks. They are currently working on replacing the device and migrating our networks accordingly. This action is expected to prevent similar issues in the future.


    Update @ 5:30 AM UTC: After escalating the issue to our upstream network provider, we are observing network recovery and all services should be back to an operational state. However, we are continuing a thorough investigation to identify the root cause. Apologies for the inconvenience


    Update @ 4:45 AM UTC: Our team identified a potential network outage originating from the data center, which impacted the racks. We have reached out to our upstream network provider for assistance.


    We are monitoring the following servers are currently out of service :

    • da71venom.stableserver.net
    • da73venom.stableserver.net
    • da75venom.stableserver.net
    • da77venom.stableserver.net
    • da79venom.stableserver.net
    • ns55.stableserver.net
    • ns62venom.stableserver.net
    • ns65v.stableserver.net
    • ns71venom.stableserver.net
    • ns75venom.stableserver.net
    • ns77venom.stableserver.net
    • ns79.stableserver.net
    • ns83venom.stableserver.net
    • venomx90.stableserver.net
    • pls5.stableserver.net
    • Some virtual servers (msnode instance)

    Our team are currently investigating on the following server. We will provide an update as soon as we get more information.


  • The issue now has been resolved. Apologize for the inconvenience.

  • 5th June 2024

    DDOS on 2900.fra1.stableserver.net, s2909.fra1.stableserver.net and s605.fra8.mysecurecloudhost.com

    Update @ 23:12 UTC Monday - All services are operating normally. We have paused migrations tonight and will migrate the rest of the accounts on Tuesday evening. We will send emails confirming the new IP first.


    UPDATE - s605.fra8.mysecurecloudhost.com's accounts will be getting migrated over to a new server later today/tonight.

    2900.fra1.stableserver.net, s2909.fra1.stableserver.net and s605.fra8.mysecurecloudhost.com were under DDOS attacks today. We have taken steps to mitigate the issue, but users may experience slower than normal services on those servers.

    4th June 2024

    Server Issues on s882.use1.mysecurecloudhost.com

    Update @ 08:00 UTC June 4th : Our team has fixed the issues with WHM/cPanel account. All service should been restored. Apologies for the inconvenience happened.


    Update @ 04:00 UTC June 4th : The issue has been identified. Our team is working on a fix to resolve the issue as soon as possible.


    We are currently experiencing issue with the following server. Our team is working to investigate and resolve the matter as soon as possible. Thank you for your patience and understanding.

    1st June 2024

    Mumbai Networking Issues

    We are investigating a system issue with multiple servers in Mumbai. A hypervisor has gone offline which has taken a number of servers offline including:

    s813.bom1.mysecurecloudhost.com d2895.bom1.stableserver.net d2971.bom1.stableserver.net w2875.bom1.stableserver.net w3038.bom1.stableserver.net

    The hypervisor is being brought back online as quickly as possible.

  • Servers are coming back online now.

  • Database issues on customer VMs

    We've received reports of some customer servers having issues with mysql due to the recent issues in our Dallas data centre.

    If you are affected please contact support and we'll do our best to assist