Category: Virtual Private Servers

  • VZNode7 Currently Offline

    This virtuozzo node is currently offline. An engineer is on site and investigating . We will update this post with more information once we discover the issue.

    Effected services list: The following VE are effected:

    217.115.118.26

    217.115.117.22

    217.115.118.47

    217.115.117.170

    217.115.118.58

    217.115.118.57

    217.115.118.60

    217.115.117.16

    217.115.117.165

    217.115.118.25

    217.115.118.19

    217.115.118.84

    217.115.117.24

    217.115.117.33

    217.115.118.91

    217.115.117.167

    217.115.118.55

    217.115.118.18

    217.115.117.25

    217.115.118.56

    217.115.118.27

    217.115.118.79

    Update @ 14:35 Server is back up now, and normal service resumed. Apologies for the inconvenience.

  • Reboot vznode6 and vznode8 10 April 22:00 GMT

    Summary: Due to a discovered vulnerability in Microsoft .NET Framework both these servers need to be patched and rebooted as a matter of urgency. More info here

    Services affecting: Your VPS will remain off-line during the reboot process.

    Duration: 5-10 minutes

    Please note this will effect Windows VPS services only .

    Update @ 22:07: Both nodes were patched and rebooted. Containers are starting up and should be complete in a couple of minutes.

    Update @ 22:09: All containers are now running and this post will not receive any further updates.

  • VZNode2 Scheduled Maintenance

    Summary: We need to run some important software updates on this node. During the update process the node will need a reboot and all containers will be shutdown. The reboot process and container start-up should only last 5-10 minutes.

    When: Thursday 27th October 2011 22:00 GMT

    Service window: 25-30 minutes.

    Effected services list:

    217.115.117.151
    217.115.117.157
    217.115.117.163
    217.115.117.156
    217.115.117.195
    217.115.117.153
    217.115.117.158
    217.115.117.184
    217.115.117.180
    217.115.117.170
    217.115.117.196
    217.115.117.197
    217.115.117.167
    217.115.117.168
    217.115.117.177
    217.115.117.193
    217.115.117.173
    217.115.117.176
    217.115.117.198
    217.115.117.171
    217.115.117.175
    217.115.117.185
    217.115.117.159
    217.115.117.200
    217.115.117.187
    217.115.117.154
    217.115.117.166
    217.115.117.182

    Update: Unfortunately this has been postponed until a later date. We will reschedule and inform all affected customers .

  • vznode2 currently offline

    Summary: This virtuozzo node is currently offline. An engineer is on site and investigating . We will update this post with more information once we discover the issue .

    Update @ 15:01: The node needed a reboot . This is now underway. I will post another update once services are starting up again .

    Update @ 15:03: The server has completed the reboot and is now starting up each container. This will take 5-10 minutes before all containers are back online .

    Update @ 15:19: Most of the containers are now back online , just a few left and these are starting.

    Update @ 15:38: All services are restored but there will be some slowdown initially as the server processes additional load due to the outage. This will not last long however.

    Apologies for the inconvenience caused.

  • Problems with vznode3 17 June

    Summary: We are experiencing some issues with this node and are currently working to resolve this . We hope to have services restored in the next 15-20 minutes but will update this post with more info if we feel its going to take longer.

    Services affected: All containers on this node are effected. Users may be able to login but services will not be operable.

    VE affected: The following VE are affected.

    217.115.117.28
    217.115.117.100
    217.115.117.105
    217.115.117.106
    217.115.117.169
    217.115.117.44
    217.115.117.222
    217.115.117.131
    217.115.117.221
    217.115.117.223
    217.115.117.227
    217.115.117.228
    217.115.118.50
    217.115.117.19
    217.115.118.66
    217.115.118.782
    217.115.118.79
    217.115.118.82
    217.115.118.86

    Update@15:30: We have applied some fixes and have had to restart the node. Just waiting now for the server to restore connectivity. Will update shortly.

    Update@15:50: The system is still running a fsck or filesystem check. This needs to complete before services can resume .

    Update@18:50: We are contacting customers directly effected via email. Please open a support ticket if you have not received an email from us regarding this issue .