EMERGENCY MAINTENANCE: FRANKFURT(EU6) CLOUD INFRASTRUCTURE

Impact: No impact to clients expected. There is a medium risk of brief period of network latency and or packet-loss.

Dear Client

The ISP has resolved issue with our Primary Circuit in EU6 that caused incident INC0013069 on January 19th. Engineers will fail back to primary circuit on the date and time below to restore full network capabilities. This type of maintenance has been performed in the past without impact, however there is a medium risk of brief latency and or packet loss during the fail-over.

Change Reference Number: CHG0008248
Frankfurt(EU6): Wednesday January 27th 09:00 PM Central European Time (20:00 UTC)
Expected Total Duration: 1 hour

Note this maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally
Posted on Jan 26, 18:18 UTC

SCHEDULED MAINTENANCE: NEW ZEALAND (AU11) CLOUD INFRASTRUCTURE

Impact: During fail-overs there is low risk of brief packet loss and or latency. These fail-overs are not state-full, so open client connections will reset. In addition the UI/API will be in Network Maintenance Mode for duration of maintenance. See notes below for restrictions.

Dear Client
On the date listed below engineers will be performing maintenance in the following cloud location. This maintenance is needed to perform upgrades to network devices supporting cloud services. During the maintenance, engineers will be performing vendor recommended software upgrades to these devices. Engineers will work on devices in a rolling fashion requiring multiple fail-overs. These fail-overs are not state-full, so open client connections will reset. In addition there is a low risk of brief packet-loss and or latency during failovers. The UI/API will be in Network Maintenance mode. See notes below for restrictions.

Change Reference Number: CHG0007094
New Zealand (AU11): Friday January 29th 09:00 PM Australia Eastern Daylight Time (10:00 UTC)
Expected Total Duration: 10 Hour

Note: Network Maintenance Mode :

1) The Admin UI and API will be available during the maintenance window, but users will be subject to the restrictions described in #2 below.
2) Starting at the beginning of maintenance event, the Admin UI and API will stop accepting any requests for actions related to Cloud Networks. This means users will not be able to deploy or make changes to Vlans, VIPs , ACLs or NATs. Please note that all deployed Cloud Servers and Networks will continue to function as normal - the system will simply block actions from being made using the Admin UI or API.
3) Except for the restrictions related to Cloud Networks all other Cloud functions will continue normally.
4) Once the maintenance is complete, the ability to take actions related to Cloud Networks will be restored.

This maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally.
Posted on Jan 15, 00:46 UTC

Impact: During fail-overs there is open session resets and a risk of brief packet loss and or latency. In addition the UI/API will be in Network Maintenance Mode for duration of maintenance. See notes below for restrictions.

Dear Client

On the date listed below engineers will be performing maintenance in the following cloud location. This maintenance is needed to perform upgrades to network devices supporting cloud services to address security vulnerabilities and bugs in current code. During the maintenance, engineers will be performing vendor recommended software upgrades to these devices. Engineers will work on devices in a rolling fashion These fail-overs are not state-full, so open client connections will reset. In addition there is a medium risk of brief packet-loss and or latency during failovers. The UI/API will be in Network Maintenance mode. See notes below for restrictions.

Change Reference Number: CHG0007100
London (EU8): Friday January 29th 09:00 PM Central European Time (20:00 UTC)
Expected Total Duration: 7 Hour

Note: Network Maintenance Mode :
1) The Admin UI and API will be available during the maintenance window, but users will be subject to the restrictions described in #2 below.
2) Starting at the beginning of maintenance event, the Admin UI and API will stop accepting any requests for actions related to Cloud Networks. This means users will not be able to deploy or make changes to Vlans, VIPs , ACLs or NATs. Please note that all deployed Cloud Servers and Networks will continue to function as normal - the system will simply block actions from being made using the Admin UI or API.
3) Except for the restrictions related to Cloud Networks all other Cloud functions will continue normally.
4) Once the maintenance is complete, the ability to take actions related to Cloud Networks will be restored.

This maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally.
Posted on Jan 12, 18:51 UTC

Impact: No client impact expected, however medium risk of disruptions to the following services. All services in following location, including but not limited to Cloud UI/API, Cloud and Manage Hosting Backup Services, CPNC, Cloud Services, and Managed Hosting Services.

Dear Client

On the dates and times listed below the Datacenter Vendor is performing power maintenance in our US EAST facility. This maintenance is needed to maintain proper power capacity for this facility. These power circuits support multiple devices in the location listed below. Although no impact to client services is expected, there is a medium risk of impact to all services including but not limited to Cloud UI/API, Cloud and Manage Hosting Backup Services, Cloud Services, and Managed Hosting Services.

Change Reference Number: CHG0008000
US EAST (NA9, ASH02): Saturday January 30th 03:00 AM US Pacific Standard Time (11:00 UTC)
Expected Total Duration: 18 Hours

Note this maintenance is specific only to the affected data center location and other Geographic Regions will continue to function normally
Posted on Jan 5, 17:09 UTC

SCHEDULED MAINTENANCE: JOHANESBURG (AF4) CLOUD INFRASTRUCTURE

Impact: During fail-overs there is low risk of brief packet loss and or latency. These fail-overs are not state-full, so open client connections will reset.
In addition the UI/API will be in Network Maintenance Mode for duration of maintenance. See notes below for restrictions.

Dear Client

On the date listed below engineers will be performing maintenance in the following cloud location. This maintenance is needed to perform upgrades to network devices supporting cloud services. During the maintenance, engineers will be performing vendor recommended software upgrades to these devices. Engineers will work on devices in a rolling fashion requiring multiple fail-overs. These fail-overs are not state-full, so open client connections will reset. In addition there is a low risk of brief packet-loss and or latency during failovers. The UI/API will be in Network Maintenance mode. See notes below for restrictions.

Change Reference Number: CHG0007104
Johannesburg: (AF4): Friday February 5th 08:00 PM South Africa Standard Time (18:00 PM UTC)
Expected Total Duration: 3 Hour

Note: Network Maintenance Mode :

1) The Admin UI and API will be available during the maintenance window, but users will be subject to the restrictions described in #2 below.
2) Starting at the beginning of maintenance event, the Admin UI and API will stop accepting any requests for actions related to Cloud Networks. This means users will not be able to deploy or make changes to Vlans, VIPs , ACLs or NATs. Please note that all deployed Cloud Servers and Networks will continue to function as normal - the system will simply block actions from being made using the Admin UI or API.
3) Except for the restrictions related to Cloud Networks all other Cloud functions will continue normally.
4) Once the maintenance is complete, the ability to take actions related to Cloud Networks will be restored.

This maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally
Posted on Jan 26, 21:14 UTC