All Systems Operational
AC - Canberra ? Operational
Dimension Data Public CaaS Portal ? Operational
Public CaaS AC2 ? Operational
Cloud Backup Operational
Cloud Monitoring Operational
Cloud NAS ? Operational
CPNC ? Operational
AF - Johannesburg Operational
Dimension Data Public CaaS Portal ? Operational
Managed Hosting JNB01 Operational
Public CaaS AF1 ? Operational
Public CaaS - AF3 ? Operational
Cloud Backup Operational
Cloud Monitoring Operational
Cloud NAS ? Operational
CSfM AF1 ? Operational
CSfS AF4 ? Operational
CSfS AF5 ? Operational
CPNC ? Operational
EMaaS AF1 ? Operational
Hosted UC AF3 ? Operational
Services Portal AF1 ? Operational
Dimension Data CaaS Portal AU Operational
AU - Melbourne Operational
Managed Hosting MEL01 ? Operational
Public CaaS AU2 ? Operational
Public CaaS AU10 ? Operational
Cloud Backup Operational
Cloud Monitoring Operational
Cloud NAS ? Operational
CPNC ? Operational
CSfM AU2 ? Operational
AU - New Zealand Operational
Managed Hosting HLZ01 ? Operational
Public CaaS AU8 ? Operational
Public CaaS AU11 ? Operational
Cloud Backup Operational
Cloud Monitoring Operational
Cloud NAS ? Operational
CPNC ? Operational
CSfM AU8 ? Operational
Hosted UC AU11 ? Operational
Hosted UC AU12 ? Operational
AU - Sydney Operational
Managed Hosting SYD01 ? Operational
Public CaaS AU1 ? Operational
Public CaaS AU6 ? Operational
Public CaaS AU9 ? Operational
Cloud Backup Operational
Cloud Monitoring Operational
Cloud NAS ? Operational
CPNC ? Operational
CSFM AU1 ? Operational
EMaaS AU9 ? Operational
Hosted UC AU9 ? Operational
Services Portal AU1 ? Operational
Hosted Desktop SYD01 Operational
Dimension Data Public CaaS Portal AP ? Operational
AP - Hong Kong Operational
Managed Hosting HKG01 ? Operational
Public CaaS AP2 ? Operational
Public CaaS AP5 ? Operational
Cloud Backup Operational
Cloud Monitoring Operational
Cloud NAS ? Operational
CSfM AP2 ? Operational
Services Portal AP2 ? Operational
AP - Malaysia Operational
Managed Hosting KUL01 Operational
Public CAAS AP13 ? Operational
Cloud Backup Operational
Cloud Monitoring Operational
CSFS AP14 ? Operational
AP - Singapore Operational
Managed Hosting SIN01 Operational
Public CaaS AP3 ? Operational
Cloud Backup Operational
Cloud Monitoring Operational
Cloud NAS Operational
CSfM AP3 ? Operational
CSfS AP9 ? Operational
CSfS AP10 ? Operational
Services Portal AP3 Operational
CaaS AP6 ? Operational
CaaS AP7 ? Operational
AP - Tokyo Operational
Managed Hosting HND01 ? Operational
Public Cloud AP1 ? Operational
Public CaaS - AP4 ? Operational
Cloud Backup Operational
Cloud Monitoring Operational
Cloud NAS ? Operational
CSfM AP1 ? Operational
CA - Canada ? Operational
Managed Hosting YYZ01 ? Operational
Dimension Data CaaS Portal Operational
Public CaaS CA1 ? Operational
Public CaaS CA2 ? Operational
Cloud Backup Operational
Cloud Monitoring Operational
Cloud NAS ? Operational
CPNC ? Operational
Dimension Data Public CaaS Portal EU ? Operational
EU - Amsterdam Operational
Managed Hosting AMS01 ? Operational
Public CaaS EU1 ? Operational
Public CaaS EU7 ? Operational
Cloud Backups Operational
Cloud Monitoring Operational
Cloud NAS ? Operational
CPNC ? Operational
EU - Belgium Operational
CaaS EU9 ? Operational
CPNC ? Operational
EU - Germany Operational
Managed Hosting FRA01 ? Operational
Public CaaS EU6 ? Operational
Cloud Backup Operational
Cloud Monitoring Operational
Cloud NAS ? Operational
CPNC ? Operational
EU - United Kingdom Operational
Managed Hosting LHR02 ? Operational
Managed Hosting LHR03 ? Operational
Public CaaS EU2 ? Operational
Public CaaS EU8 ? Operational
Cloud Backup Operational
Cloud Monitoring Operational
Cloud NAS ? Operational
CPNC ? Operational
CSfM EU2 ? Operational
EMaaS EU8 ? Operational
Services Portal EU2 ? Operational
IL - Israel Operational
Dimension Data CaaS Portal Operational
CaaS IL1 Operational
CaaS IL2 Operational
Cloud Backup Operational
CPNC ? Operational
Dimension Data Public CaaS Portal NA ? Operational
NA - US East ? Operational
Managed Hosting ASH01 ? Operational
Managed Hosting ASH02 ? Operational
Managed Hosting PCI01 ? Operational
Public CaaS NA1 ? Operational
Public CaaS NA5 ? Operational
Public CaaS NA9 ? Operational
Cloud Backup Operational
Cloud NAS Operational
Cloud Monitoring Operational
CPNC ? Operational
CSfM NA5 ? Operational
EMaaS NA9 ? Operational
Hosted UC NA9 ? Operational
Services Portal NA5 ? Operational
NA - US West ? Operational
Managed Hosting SJC03 ? Operational
Managed Hosting - SNU01 ? Operational
Managed Hosting PCI02 ? Operational
Public CaaS - NA3 ? Operational
Public CaaS - NA12 ? Operational
Cloud Backup Operational
Cloud Monitoring Operational
Cloud NAS ? Operational
CPNC ? Operational
CSfM - NA3 ? Operational
IT & Operational Systems ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
Impact: During this maintenance clients will not be able to log into the Cloud UI/API or Client to Site VPN service for up to 30 minutes. No impact to client cloud servers or networks expected.

Dear Client

In preparation for future improvements Engineers will be implementing new LDAP services for the UI/API in the location listed below. During this maintenance clients will not be able to log into the Cloud UI/API or Client to Site VPN service for up to 30 minutes. No impact to client cloud servers or networks expected. This change will improve UI/API response times, as well as allow us to implement future security improvements.

Change Reference Number: CHM121939128
Asia-Pacific (All AP Locations): Tuesday July 23rd 09:00 PM Japan Standard (12:00 UTC)
Expected Total Duration: 1 Hours

Note this maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally.
Posted on Jul 18, 20:56 UTC
The DRS for Cloud feature is being enabled sometime during Tuesday, July 23rd to support migrations from the US - East MCP 1.0 (NA1) to the US - East 3 - MCP 2.0 (NA9) location.

CloudControl Change Id: OEC-11584
Time: During Tuesday July 23rd business day
Expected Total Duration: Users can identify availability as described in Identify Hardware Specifications and Capabilities Available in a Data Center Location - https://docs.mcp-services.net/x/nAAu

This new feature allows the implement real-time replication of the disk state of multiple Cloud Servers to another location in the same Geographic Region, with the ability to restore multiple Target servers to the disk state of their paired Source servers at an identical point-in-time.

The initial DRS for Cloud rollout is being deployed to support users who wish to migrate their Cloud Servers from MCP 1.0 to MCP 2.0 locations. As such, the replication being enabled in this rollout is unidirectional: users can replicate only from the MCP 1.0 to the MCP 2.0 location. There is an additional hourly usage element recorded for use of the feature.

IMPORTANT NOTE: The DRS feature is only visible in the UI to Primary Administrators and users with the DRS role.

For details, see:

Introduction to DRS for Cloud - https://docs.mcp-services.net/x/qgE8
MCP 1.0 to 2.0 Self-Service Migration - https://docs.mcp-services.net/x/RgOy
How to Create a DRS Consistency Group - https://docs.mcp-services.net/x/sAE8
How to Start a DRS Preview for a Consistency Group - https://docs.mcp-services.net/x/uwE8
How to Initiate a Failover for a DRS Consistency Group - https://docs.mcp-services.net/x/vwE8

There is no CloudControl UI or API downtime nor impact to any existing Cloud Servers and Networks due to this change. This notification is for informational purposes only.
Posted on Jul 18, 13:33 UTC
The DRS for Cloud feature is being enabled sometime during Tuesday, July 23rd to support migrations from the US - East 2 MCP 1.0 (NA5) to the US - East 3 - MCP 2.0 (NA9) location.

CloudControl Change Id: OEC-11585
Time: During Tuesday July 23rd business day
Expected Total Duration: Users can identify availability as described in Identify Hardware Specifications and Capabilities Available in a Data Center Location - https://docs.mcp-services.net/x/nAAu

This new feature allows the implement real-time replication of the disk state of multiple Cloud Servers to another location in the same Geographic Region, with the ability to restore multiple Target servers to the disk state of their paired Source servers at an identical point-in-time.

The initial DRS for Cloud rollout is being deployed to support users who wish to migrate their Cloud Servers from MCP 1.0 to MCP 2.0 locations. As such, the replication being enabled in this rollout is unidirectional: users can replicate only from the MCP 1.0 to the MCP 2.0 location. There is an additional hourly usage element recorded for use of the feature.

IMPORTANT NOTE: The DRS feature is only visible in the UI to Primary Administrators and users with the DRS role.

For details, see:

Introduction to DRS for Cloud - https://docs.mcp-services.net/x/qgE8
MCP 1.0 to 2.0 Self-Service Migration - https://docs.mcp-services.net/x/RgOy
How to Create a DRS Consistency Group - https://docs.mcp-services.net/x/sAE8
How to Start a DRS Preview for a Consistency Group - https://docs.mcp-services.net/x/uwE8
How to Initiate a Failover for a DRS Consistency Group - https://docs.mcp-services.net/x/vwE8

There is no CloudControl UI or API downtime nor impact to any existing Cloud Servers and Networks due to this change. This notification is for informational purposes only.
Posted on Jul 18, 13:38 UTC
The DRS for Cloud feature is being enabled sometime during Tuesday, July 23rd to support migrations from the Sydney MCP 1.0 (AU1) to the Sydney MCP 2.0 (AU9) location.

CloudControl Change Id: OEC-11587
Time: After Tuesday July 23rd business day
Expected Total Duration: Users can identify availability as described in Identify Hardware Specifications and Capabilities Available in a Data Center Location - https://docs.mcp-services.net/x/nAAu

This new feature allows the implement real-time replication of the disk state of multiple Cloud Servers to another location in the same Geographic Region, with the ability to restore multiple Target servers to the disk state of their paired Source servers at an identical point-in-time.

The initial DRS for Cloud rollout is being deployed to support users who wish to migrate their Cloud Servers from MCP 1.0 to MCP 2.0 locations. As such, the replication being enabled in this rollout is unidirectional: users can replicate only from the MCP 1.0 to the MCP 2.0 location. There is an additional hourly usage element recorded for use of the feature.

IMPORTANT NOTE: The DRS feature is only visible in the UI to Primary Administrators and users with the DRS role.

For details, see:

Introduction to DRS for Cloud - https://docs.mcp-services.net/x/qgE8
MCP 1.0 to 2.0 Self-Service Migration - https://docs.mcp-services.net/x/RgOy
How to Create a DRS Consistency Group - https://docs.mcp-services.net/x/sAE8
How to Start a DRS Preview for a Consistency Group - https://docs.mcp-services.net/x/uwE8
How to Initiate a Failover for a DRS Consistency Group - https://docs.mcp-services.net/x/vwE8

There is no CloudControl UI or API downtime nor impact to any existing Cloud Servers and Networks due to this change. This notification is for informational purposes only.
Posted on Jul 18, 13:51 UTC
The DRS for Cloud feature is being enabled sometime during Tuesday, July 23rd to support migrations from the US - West MCP 1.0 (NA3) to the US - West - MCP 2.0 (NA12) location.

CloudControl Change Id: OEC-11586
Time: During Tuesday July 23rd business day
Expected Total Duration: Users can identify availability as described in Identify Hardware Specifications and Capabilities Available in a Data Center Location - https://docs.mcp-services.net/x/nAAu

This new feature allows the implement real-time replication of the disk state of multiple Cloud Servers to another location in the same Geographic Region, with the ability to restore multiple Target servers to the disk state of their paired Source servers at an identical point-in-time.

The initial DRS for Cloud rollout is being deployed to support users who wish to migrate their Cloud Servers from MCP 1.0 to MCP 2.0 locations. As such, the replication being enabled in this rollout is unidirectional: users can replicate only from the MCP 1.0 to the MCP 2.0 location. There is an additional hourly usage element recorded for use of the feature.

IMPORTANT NOTE: The DRS feature is only visible in the UI to Primary Administrators and users with the DRS role.

For details, see:

Introduction to DRS for Cloud - https://docs.mcp-services.net/x/qgE8
MCP 1.0 to 2.0 Self-Service Migration - https://docs.mcp-services.net/x/RgOy
How to Create a DRS Consistency Group - https://docs.mcp-services.net/x/sAE8
How to Start a DRS Preview for a Consistency Group - https://docs.mcp-services.net/x/uwE8
How to Initiate a Failover for a DRS Consistency Group - https://docs.mcp-services.net/x/vwE8

There is no CloudControl UI or API downtime nor impact to any existing Cloud Servers and Networks due to this change. This notification is for informational purposes only.
Posted on Jul 18, 13:47 UTC
Impact: During this maintenance clients will not be able to log into the Cloud UI/API or Client to Site VPN service for up to 30 minutes. No impact to client cloud servers or networks expected.

Dear Client

In preparation for future improvements Engineers will be implementing new LDAP services for the UI/API in the location listed below. During this maintenance clients will not be able to log into the Cloud UI/API or Client to Site VPN service for up to 30 minutes. No impact to client cloud servers or networks expected. This change will improve UI/API response times, as well as allow us to implement future security improvements.

Change Reference Number: CHM121939167
Johannesburg: (All AF Locations): Tuesday July 23rd 08:00 PM South Africa Standard Time (18:00 PM UTC)
Expected Total Duration: 1 Hours

Note this maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally.
Posted on Jul 18, 21:01 UTC
Impact: During this maintenance clients will not be able to log into the Cloud UI/API or Client to Site VPN service for up to 30 minutes. No impact to client cloud servers or networks expected.

Dear Client

In preparation for future improvements Engineers will be implementing new LDAP services for the UI/API in the location listed below. During this maintenance clients will not be able to log into the Cloud UI/API or Client to Site VPN service for up to 30 minutes. No impact to client cloud servers or networks expected. This change will improve UI/API response times, as well as allow us to implement future security improvements.

Change Reference Number: CHM121939223
North America : (All NA Locations): Thursday July 25th 09:00 PM US Pacific Daylight Time (26/7 04:00 UTC)
Expected Total Duration: 1 Hours

Note this maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally.
Posted on Jul 18, 23:06 UTC
Impact: The UI/API will be in Network Maintenance Mode for duration of maintenance see note below for restrictions.

Dear Client

On the date listed below engineers will be performing maintenance in the following cloud locations. This maintenance is necessary to perform patching of the infrastructure supporting the cloud UI/API. During this maintenance, we will be upgrading infrastructure devices to the latest vendor approved and tested OS patches. The Cloud UI/API will be in Network Maintenance Mode for duration of maintenance see note below for client restrictions. Deployed client cloud servers will continue to function without interruption.

Change Reference Number: CHM121977808
Singapore (AP7): Friday July 26th 09:00 PM Japan Standard (12:00 UTC)
Expected Total Duration: 4 Hours

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 Jul 18, 20:52 UTC
SCHEDULED MAINTENANCE: SINGAPORE (AP10) CLOUD INFRASTRUCTURE MAINTENANCE

Impact: The UI/API will be in Network Maintenance Mode for duration of maintenance see note below for restrictions.

Dear Client

On the date listed below engineers will be performing maintenance in the following cloud locations. This maintenance is necessary to perform patching of the infrastructure supporting the cloud UI/API. During this maintenance, we will be upgrading infrastructure devices to the latest vendor approved and tested OS patches. The Cloud UI/API will be in Network Maintenance Mode for duration of maintenance see note below for client restrictions. Deployed client cloud servers will continue to function without interruption.

Change Reference Number: CHM121977858
Singapore (AP10): Friday July 26th 09:00 PM Japan Standard (12:00 UTC)
Expected Total Duration: 4 Hours

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 Jul 18, 20:54 UTC
Impact: The UI/API will be in Hypervisor Maintenance Mode for the duration of maintenance window. See note below for restrictions. There will be no impact to client cloud servers.

Dear Client

On the date listed below engineers will be performing maintenance in the following cloud locations. This maintenance is necessary to perform patching of the infrastructure supporting the cloud UI/API. During this maintenance we will be upgrading infrastructure devices to the latest vendor approved and tested OS patches. The Cloud UI/API will be in Hypervisor Maintenance Mode for duration of the maintenance see note below for client restrictions. Deployed client cloud servers will continue to function without interruption.

Change Reference Number: CHM121966130
Johannesburg: (AF-All Locations): Friday July 26h 08:00 PM South Africa Standard Time (18:00 PM UTC)
Expected Total Duration: 8 Hours

Note: Hypervisor 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 and #3 below.

2) Starting one hour before the maintenance event, the Admin UI and API will stop accepting any requests for actions related to Cloud Servers or Cloud Images in the affected data center only. This means users will not be able to deploy new servers or images, start/stop/reboot/edit/delete existing servers or images, or start any new import/export actions. Please note that all deployed Cloud Servers will continue to function as normal - the system will simply block actions from being made using the Admin UI or API. Changes requested prior to the one-hour limit will continue to process with status updates in the Admin UI or API until the event begins.

3) Beginning with the start of the maintenance window, the Admin UI and API will stop updating the status of Cloud Servers or Cloud Images in the affected data center. For example, if a server is shut down or rebooted from the Guest OS, the Admin UI/API will not reflect that change.

4) Except for the restrictions related to Cloud Servers and Images, all other Cloud functions will continue normally.

5) Once the maintenance is complete, the ability to take actions related to Cloud Servers and Cloud Images will be restored and the system will update the status of all deployed Cloud Servers.

This maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally.
Posted on Jul 18, 22:57 UTC
Impact: The UI/API will be in Network Maintenance Mode for duration of maintenance see note below for restrictions.

Dear Client

On the date listed below engineers will be performing maintenance in the following cloud locations. This maintenance is necessary to perform patching of the infrastructure supporting the cloud UI/API. During this maintenance, we will be upgrading infrastructure devices to the latest vendor approved and tested OS patches. The Cloud UI/API will be in Network Maintenance Mode for duration of maintenance see note below for client restrictions. Deployed client cloud servers will continue to function without interruption.

Change Reference Number: CHM121977950
Israel (IL2): Friday July 26th 09:00 PM Israel Daylight Time (18:00 UTC)
Expected Total Duration: 4 Hours

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 Jul 18, 21:13 UTC
Impact: The UI/API will be in Network Maintenance Mode for duration of maintenance see note below for restrictions.

Dear Client

On the date listed below engineers will be performing maintenance in the following cloud locations. This maintenance is necessary to perform patching of the infrastructure supporting the cloud UI/API. During this maintenance, we will be upgrading infrastructure devices to the latest vendor approved and tested OS patches. The Cloud UI/API will be in Network Maintenance Mode for duration of maintenance see note below for client restrictions. Deployed client cloud servers will continue to function without interruption.

Change Reference Number: CHM121977590
Belgium (EU9): Friday July 26th 9:00 PM Central European Standard (19:00 UTC)
Expected Total Duration: 4 Hours

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 Jul 18, 21:23 UTC
Impact: The UI/API will be in Network Maintenance Mode for duration of maintenance see note below for restrictions.

Dear Client

On the date listed below engineers will be performing maintenance in the following cloud locations. This maintenance is necessary to perform patching of the infrastructure supporting the cloud UI/API. During this maintenance, we will be upgrading infrastructure devices to the latest vendor approved and tested OS patches. The Cloud UI/API will be in Network Maintenance Mode for duration of maintenance see note below for client restrictions. Deployed client cloud servers will continue to function without interruption.

Change Reference Number: CHM121977232
Germany (EU6): Friday July 26th 9:00 PM Central European Standard (19:00 UTC)
Expected Total Duration: 4 Hours

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 Jul 18, 21:15 UTC
Impact: Client to Site VPN Service will disconnect any open Client to Site VPN sessions it may require client to reconnect.

Dear Client

On the date listed below engineers will be performing maintenance in the following locations. This maintenance is needed to complete pre-work for future move of Client to Site VPN service to new infrastructure. Engineers expect Client to Site VPN sessions to be disconnected. May require client to reconnect.

Change Reference Number: CHM121848687
US EAST (NA1): Friday July 26th 08:30 PM US Pacific Daylight Time (27/7 03:30 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 Jul 18, 20:45 UTC
We will be performing a major software upgrade to the CloudControl API infrastructure in the Canada (CA) Geographic Region on Monday July 29th local time (Tuesday July 30th UTC time) during this time period

CloudControl Change Id: CCOCHANGE-102
Time: July 29 09:00 PM Eastern Daylight / 6:00 PM Pacific Daylight (July 30th 01:00 UTC)
Expected Total Duration: 2 hours minutes downtime

This maintenance involves a series of security patches and upgrades to the CloudControl infrastructure in this region.

During the software upgrade, all Cloud Servers and Network assets you've deployed will be unaffected. However, the CloudControl API will be unavailable during the software upgrade for the duration listed above. The CloudControl UI will remain available but will be unable to process requests in the affected Geographic Region during this window.
Posted on Jul 10, 21:10 UTC
Impact: During this maintenance clients will not be able to log into the Cloud UI/API or Client to Site VPN service for up to 30 minutes. No impact to client cloud servers or networks expected.

Dear Client

In preparation for future improvements Engineers will be implementing new LDAP services for the UI/API in the location listed below. During this maintenance clients will not be able to log into the Cloud UI/API or Client to Site VPN service for up to 30 minutes. No impact to client cloud servers or networks expected. This change will improve UI/API response times, as well as allow us to implement future security improvements.

Change Reference Number: CHM121938610
Australia, New Zealand (All AU locations): Tuesday July 30th 09:00 PM Australia Eastern Standard Time (11:00 UTC)
Expected Total Duration: 1 Hours

Note this maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally.
Posted on Jul 18, 20:48 UTC
Impact: During this maintenance clients will not be able to log into the Cloud UI/API or Client to Site VPN service for up to 30 minutes. No impact to client cloud servers or networks expected.

Dear Client

In preparation for future improvements Engineers will be implementing new LDAP services for the UI/API in the location listed below. During this maintenance clients will not be able to log into the Cloud UI/API or Client to Site VPN service for up to 30 minutes. No impact to client cloud servers or networks expected. This change will improve UI/API response times, as well as allow us to implement future security improvements.

Change Reference Number: CHM121938991
Europe (All EU locations): Tuesday July 30th 09:00 PM Central European Standard (19:00 UTC)
Expected Total Duration: 1 Hours

Note this maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally.
Posted on Jul 18, 21:02 UTC
As part of our ongoing improvement initiatives, we will be kicking off our storage upgrade programme in EU7 (Amsterdam MCP 2.0) to give a better, predictable and consistent experience when it comes to cloud storage performance. As part of the initiative, we are migrating the Standard/High Performance/Economy Disk Speeds in EU7 (Amsterdam MCP 2.0) to the new “Burstable” storage model.

As part of this effort, we will be making changes to ALL disks associated with ALL existing Cloud Servers that are using the Economy, Standard, and High Performance disk speeds.

The enablement will begin during the normal software upgrade window on August 1, 2019 starting at 18:00 UTC. The change is expected to take several hours to take effect across all existing Cloud Servers.

CloudControl Change Id: OEC-11578
Time: 08:00 PM Central European Summer Time (18:00 UTC)
Expected Total Duration: Up to 18 Hours

For all NEW and EXISTING disks on all Cloud Servers using Economy, Standard, or High Performance disk speeds:

1. After the change, Disks will be allowed to burst only up the following IOPS and Throughput limits based on their disk speed:

ECONOMY: Greater of 100 IOPS or 0.5 IOPS/GB based on the size of the disk
STANDARD: Greater of 500 IOPS or 3 IOPS/GB based on the size of the disk
HIGH PERFORMANCE: Greater of 800 IOPS or 6 IOPS/GB based on the size of the disk

Throughput limit equal to the IOPS maximum x 16 KB (Kilobytes). This limit applies in addition to the above IOPS limit.

Example:: A 100 GB Disk using Standard Disk Speed will be assigned a 500 IOPS burstable maximum AND an 8,000 Kilobyte/second Throughput maximum (500 IOPS x 16 KB).

2. If the server is running when the change is implemented, the system will vMotion the server so that the changes take immediate effect. No restart is required. This is an improvement in behavior from previous locations where we have migrated to Burstable architecture.

However, if some issue prevents the system from successfully vMotioning the server, the server may require a restart before additional CloudControl actions can be made against the server.

For more information please refer to the following two articles:

Introduction to Cloud Server Local Storage ("Disks") and Disk Speeds - https://docs.mcp-services.net/x/UwIu
How do I determine if my Server Requires a Restart Using REST API? - https://docs.mcp-services.net/x/QgSZ
Posted on Jul 17, 16:54 UTC
Impact: No impact to clients is expected.

Dear Client

On the date listed below engineers will be performing maintenance in the following cloud location. This maintenance is necessary to perform patching of the infrastructure supporting the cloud UI/API. During this maintenance, we will be upgrading infrastructure devices to the latest vendor approved and tested OS patches. Engineers do not expect any impact to the UI/API or Client Cloud Servers.

Change Reference Number: CHM121966450
Australia, New Zealand (All AU Locations): Friday August 2nd 09:00 PM Australia Eastern Standard Time (11:00 UTC)
Expected Total Duration:4 Hours

Note this maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally.
Posted on Jul 18, 23:29 UTC
Impact: No impact to clients is expected.

Dear Client

On the date listed below engineers will be performing maintenance in the following cloud location. This maintenance is necessary to perform patching of the infrastructure supporting the cloud UI/API. During this maintenance, we will be upgrading infrastructure devices to the latest vendor approved and tested OS patches. Engineers do not expect any impact to the UI/API or Client Cloud Servers.

Change Reference Number: CHM121966471
Europe (All EU Locations): Friday August 2nd 09:00 PM Central European Standard (19:00 UTC)
Expected Total Duration: 4 Hours

Note this maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally.
Posted on Jul 18, 23:31 UTC
Impact: The UI/API will be in Hypervisor Maintenance Mode for the duration of maintenance window. See note below for restrictions. There will be no impact to client cloud servers.

Dear Client

On the date listed below engineers will be performing maintenance in the following cloud locations. This maintenance is necessary to perform patching of the infrastructure supporting the cloud UI/API. During this maintenance we will be upgrading infrastructure devices to the latest vendor approved and tested OS patches. The Cloud UI/API will be in Hypervisor Maintenance Mode for duration of the maintenance see note below for client restrictions. Deployed client cloud servers will continue to function without interruption.

Change Reference Number: CHM121966514
Europe (EU-All Locations): Friday August 2 09:00 PM Central European Standard (19:00 UTC)
Expected Total Duration: 8 Hours

Note: Hypervisor 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 and #3 below.

2) Starting one hour before the maintenance event, the Admin UI and API will stop accepting any requests for actions related to Cloud Servers or Cloud Images in the affected data center only. This means users will not be able to deploy new servers or images, start/stop/reboot/edit/delete existing servers or images, or start any new import/export actions. Please note that all deployed Cloud Servers will continue to function as normal - the system will simply block actions from being made using the Admin UI or API. Changes requested prior to the one-hour limit will continue to process with status updates in the Admin UI or API until the event begins.

3) Beginning with the start of the maintenance window, the Admin UI and API will stop updating the status of Cloud Servers or Cloud Images in the affected data center. For example, if a server is shut down or rebooted from the Guest OS, the Admin UI/API will not reflect that change.

4) Except for the restrictions related to Cloud Servers and Images, all other Cloud functions will continue normally.

5) Once the maintenance is complete, the ability to take actions related to Cloud Servers and Cloud Images will be restored and the system will update the status of all deployed Cloud Servers.

This maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally.
Posted on Jul 18, 23:00 UTC
Impact: During the window SRM fail-over capabilities will not be available.

Dear Client

On the date listed below engineers will be performing maintenance in the following cloud location. This maintenance is necessary to perform patching of equipment supporting Disaster Recovery SRM fail-over capabilities . During this maintenance all DR replication will continue, however SRM Fail-over capabilities will be temporarily unavailable.

Change Reference Number: CHM121966544
Johannesburg: (AF4,AF5): Thursday August 8th 07:00 PM South Africa Standard Time (17:00 PM UTC)
Expected Total Duration: 3 Hours

Note this maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally.
Posted on Jul 18, 20:46 UTC
Impact: During the window SRM fail-over capabilities will not be available.

Dear Client

On the date listed below engineers will be performing maintenance in the following cloud location. This maintenance is necessary to perform patching of equipment supporting Disaster Recovery SRM fail-over capabilities . During this maintenance all DR replication will continue, however SRM Fail-over capabilities will be temporarily unavailable.

Change Reference Number: CHM121966544
Singapore (AP9, AP10): Friday August 9th 02:00 AM Japan Standard (8/7 17:00 UTC)
Expected Total Duration: 3 Hours

Note this maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally.
Posted on Jul 18, 21:17 UTC
Impact: The UI/API will be in Hypervisor Maintenance Mode for the duration of maintenance window. See note below for restrictions. There will be no impact to client cloud servers.

Dear Client

On the date listed below engineers will be performing maintenance in the following cloud locations. This maintenance is necessary to perform patching of the infrastructure supporting the cloud UI/API. During this maintenance we will be upgrading infrastructure devices to the latest vendor approved and tested OS patches. The Cloud UI/API will be in Hypervisor Maintenance Mode for duration of the maintenance see note below for client restrictions. Deployed client cloud servers will continue to function without interruption.

Change Reference Number: CHM121966601
Australia/ New Zealand (All AU Locations): Friday August 9th 09:00 PM Australia Eastern Standard Time (11:00 UTC)
Expected Total Duration: 8 Hours

Note: Hypervisor 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 and #3 below.

2) Starting one hour before the maintenance event, the Admin UI and API will stop accepting any requests for actions related to Cloud Servers or Cloud Images in the affected data center only. This means users will not be able to deploy new servers or images, start/stop/reboot/edit/delete existing servers or images, or start any new import/export actions. Please note that all deployed Cloud Servers will continue to function as normal - the system will simply block actions from being made using the Admin UI or API. Changes requested prior to the one-hour limit will continue to process with status updates in the Admin UI or API until the event begins.

3) Beginning with the start of the maintenance window, the Admin UI and API will stop updating the status of Cloud Servers or Cloud Images in the affected data center. For example, if a server is shut down or rebooted from the Guest OS, the Admin UI/API will not reflect that change.

4) Except for the restrictions related to Cloud Servers and Images, all other Cloud functions will continue normally.

5) Once the maintenance is complete, the ability to take actions related to Cloud Servers and Cloud Images will be restored and the system will update the status of all deployed Cloud Servers.

This maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally.
Posted on Jul 18, 23:16 UTC
Impact: No impact to clients is expected.

Dear Client

On the date listed below engineers will be performing maintenance in the following cloud location. This maintenance is necessary to perform patching of the infrastructure supporting the cloud UI/API. During this maintenance, we will be upgrading infrastructure devices to the latest vendor approved and tested OS patches. Engineers do not expect any impact to the UI/API or Client Cloud Servers.

Change Reference Number: CHM121966564
Asia-Pacific (All AP Locations): Friday August 9th 09:00 PM Japan Standard (12:00 UTC)
Expected Total Duration: 4 Hours

Note this maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally.
Posted on Jul 18, 23:14 UTC
Past Incidents
Jul 23, 2019

No incidents reported today.

Jul 22, 2019
Completed - The scheduled maintenance has been completed.
Jul 22, 21:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 22, 09:00 UTC
Scheduled - The Provisioned IOPS disk speed is being enabled sometime during Monday July 22nd in the AU11 (New_Zealand MCP 2.0) location during this window

CloudControl Change Id: OEC-11591
Time: During Tuesday July 22rd business day
Expected Total Duration: Users can identify availability as described in Identify Hardware Specifications and Capabilities Available in a Data Center Location - https://docs.mcp-services.net/x/nAAu

The new disk speed allows the user to specify the specific IOPS and Throughput of a disk independent of the size of the disk. Users pay a separate hourly rate for the IOPS and amount of disk storage. For details, see:

Introduction to Cloud Server Local Storage ("Disks") and Disk Speeds - https://docs.mcp-services.net/x/UwIu
How to Manage Storage on a Cloud Server - https://docs.mcp-services.net/x/mgMk
Introduction to Usage Reporting - https://docs.mcp-services.net/x/7IBs

Other than the need to specify the desired IOPS with the supported parameters and the change in usage, the new Provisioned IOPS disk speed works like all other disk speeds.

There is no CloudControl UI or API downtime nor impact to any existing Cloud Servers and Networks due to this change. This notification is for informational purposes only.
Jul 18, 22:52 UTC
Jul 21, 2019

No incidents reported.

Jul 20, 2019

No incidents reported.

Jul 19, 2019
Completed - The scheduled maintenance has been completed.
Jul 19, 22:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 19, 18:00 UTC
Scheduled - Impact: The UI/API will be in Hypervisor Maintenance Mode for duration of maintenance see note below for restrictions.

Dear Client

On the date listed below engineers will be performing maintenance in the following cloud locations. This maintenance is necessary to performing upgrades of the infrastructure supporting the Hypervisor infrastructure. During this maintenance we will be upgrading hypervisor management devices to the latest product approved and tested version. The Cloud UI/API will be in Hypervisor Maintenance Mode for duration of maintenance. See note below for client restrictions. Deployed client cloud servers will continue to function without interruption.

Change Reference Number: CHM121623965
Johannesburg (AF5): Friday July 19th 08:00 PM South Africa Standard Time (18:00 PM UTC)
Expected Total Duration: 4 Hours

Note: Hypervisor 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 and #3 below.

2) Starting one hour before the maintenance event, the Admin UI and API will stop accepting any requests for actions related to Cloud Servers or Cloud Images in the affected data center only. This means users will not be able to deploy new servers or images, start/stop/reboot/edit/delete existing servers or images, or start any new import/export actions. Please note that all deployed Cloud Servers will continue to function as normal - the system will simply block actions from being made using the Admin UI or API. Changes requested prior to the one-hour limit will continue to process with status updates in the Admin UI or API until the event begins.

3) Beginning with the start of the maintenance window, the Admin UI and API will stop updating the status of Cloud Servers or Cloud Images in the affected data center. For example, if a server is shut down or rebooted from the Guest OS, the Admin UI/API will not reflect that change.

4) Except for the restrictions related to Cloud Servers and Images, all other Cloud functions will continue normally.

5) Once the maintenance is complete, the ability to take actions related to Cloud Servers and Cloud Images will be restored and the system will update the status of all deployed Cloud Servers.

This maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally.
Jun 14, 00:01 UTC
Completed - The scheduled maintenance has been completed.
Jul 19, 17:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 19, 12:00 UTC
Scheduled - Impact: The UI/API will be in Network Maintenance Mode for duration of maintenance see note below for restrictions.

Dear Client

On the date listed below engineers will be performing maintenance in the following cloud locations. This maintenance is necessary to perform patching of the infrastructure supporting the cloud UI/API. During this maintenance, we will be upgrading infrastructure devices to the latest vendor approved and tested OS patches. The Cloud UI/API will be in Network Maintenance Mode for duration of maintenance see note below for client restrictions. Deployed client cloud servers will continue to function without interruption.

Change Reference Number: CHM121395609
Hong Kong (AP2/AP5): Friday July 19th 09:00 PM Japan Standard (12:00 UTC)
Expected Total Duration: 5 Hours

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.
Jul 2, 21:14 UTC
Completed - The scheduled maintenance has been completed.
Jul 19, 16:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 19, 12:00 UTC
Scheduled - Impact: The UI/API will be in Hypervisor Maintenance Mode for duration of maintenance see note below for restrictions.

Dear Client

On the date listed below engineers will be performing maintenance in the following cloud locations. This maintenance is necessary to performing upgrades of the infrastructure supporting the Hypervisor infrastructure. During this maintenance we will be upgrading hypervisor management devices to the latest product approved and tested version. The Cloud UI/API will be in Hypervisor Maintenance Mode for duration of maintenance. See note below for client restrictions. Deployed client cloud servers will continue to function without interruption.

Change Reference Number: CHM121624000
Singapore (AP10): Friday July 19th 09:00 PM Japan Standard (12:00 UTC)
Expected Total Duration: 4 Hours

Note: Hypervisor 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 and #3 below.

2) Starting one hour before the maintenance event, the Admin UI and API will stop accepting any requests for actions related to Cloud Servers or Cloud Images in the affected data center only. This means users will not be able to deploy new servers or images, start/stop/reboot/edit/delete existing servers or images, or start any new import/export actions. Please note that all deployed Cloud Servers will continue to function as normal - the system will simply block actions from being made using the Admin UI or API. Changes requested prior to the one-hour limit will continue to process with status updates in the Admin UI or API until the event begins.

3) Beginning with the start of the maintenance window, the Admin UI and API will stop updating the status of Cloud Servers or Cloud Images in the affected data center. For example, if a server is shut down or rebooted from the Guest OS, the Admin UI/API will not reflect that change.

4) Except for the restrictions related to Cloud Servers and Images, all other Cloud functions will continue normally.

5) Once the maintenance is complete, the ability to take actions related to Cloud Servers and Cloud Images will be restored and the system will update the status of all deployed Cloud Servers.

This maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally.
Jun 13, 23:34 UTC
Completed - The scheduled maintenance has been completed.
Jul 19, 16:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 19, 12:00 UTC
Scheduled - Impact: The UI/API will be in Hypervisor Maintenance Mode for duration of maintenance see note below for restrictions.

Dear Client

On the date listed below engineers will be performing maintenance in the following cloud locations. This maintenance is necessary to performing upgrades of the infrastructure supporting the Hypervisor infrastructure. During this maintenance we will be upgrading hypervisor management devices to the latest product approved and tested version. The Cloud UI/API will be in Hypervisor Maintenance Mode for duration of maintenance. See note below for client restrictions. Deployed client cloud servers will continue to function without interruption.

Change Reference Number: CHM121623978
Singapore (AP9): Friday July 19th 09:00 PM Japan Standard (12:00 UTC)
Expected Total Duration: 4 Hours

Note: Hypervisor 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 and #3 below.

2) Starting one hour before the maintenance event, the Admin UI and API will stop accepting any requests for actions related to Cloud Servers or Cloud Images in the affected data center only. This means users will not be able to deploy new servers or images, start/stop/reboot/edit/delete existing servers or images, or start any new import/export actions. Please note that all deployed Cloud Servers will continue to function as normal - the system will simply block actions from being made using the Admin UI or API. Changes requested prior to the one-hour limit will continue to process with status updates in the Admin UI or API until the event begins.

3) Beginning with the start of the maintenance window, the Admin UI and API will stop updating the status of Cloud Servers or Cloud Images in the affected data center. For example, if a server is shut down or rebooted from the Guest OS, the Admin UI/API will not reflect that change.

4) Except for the restrictions related to Cloud Servers and Images, all other Cloud functions will continue normally.

5) Once the maintenance is complete, the ability to take actions related to Cloud Servers and Cloud Images will be restored and the system will update the status of all deployed Cloud Servers.

This maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally.
Jun 13, 23:31 UTC
Completed - The scheduled maintenance has been completed.
Jul 19, 13:01 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 19, 11:00 UTC
Scheduled - Impact: No impact to clients environments expected. UI/API will be put into Network Maintenance Mode for up to 10 minutes during change.

Dear Client

On the dates listed below performing emergency network maintenance. Engineers will be replacing failed network device supporting the UI/API. UI/API will be put into Network Maintenance Mode for up to 10 minutes during the window. No impact to client environments is expected.

Change Reference Number: CHM122000563
Melbourne (AU10): Friday July 19th 09:00 PM Australia Eastern Standard Time (11:00 UTC)
Expected Total Duration: 2 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
Jul 18, 20:43 UTC
Completed - The scheduled maintenance has been completed.
Jul 19, 05:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 19, 01:00 UTC
Scheduled - SCHEDULED MAINTENANCE: CANADA (CA1) CLOUD INFRASTRUCTURE MAINTENANCE

Impact: The UI/API will be in Hypervisor Maintenance Mode for duration of maintenance see note below for restrictions.

Dear Client

On the date listed below engineers will be performing maintenance in the following cloud locations. This maintenance is necessary to performing upgrades of the infrastructure supporting the Hypervisor infrastructure. During this maintenance we will be upgrading hypervisor management devices to the latest product approved and tested version. The Cloud UI/API will be in Hypervisor Maintenance Mode for duration of maintenance. See note below for client restrictions. Deployed client cloud servers will continue to function without interruption.

Change Reference Number: CHM121623873
Canada (CA1): Friday July 19th 09:00 PM Eastern Daylight Time (20/7 01:00 UTC)
Expected Total Duration: 4 Hours

Note: Hypervisor 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 and #3 below.

2) Starting one hour before the maintenance event, the Admin UI and API will stop accepting any requests for actions related to Cloud Servers or Cloud Images in the affected data center only. This means users will not be able to deploy new servers or images, start/stop/reboot/edit/delete existing servers or images, or start any new import/export actions. Please note that all deployed Cloud Servers will continue to function as normal - the system will simply block actions from being made using the Admin UI or API. Changes requested prior to the one-hour limit will continue to process with status updates in the Admin UI or API until the event begins.

3) Beginning with the start of the maintenance window, the Admin UI and API will stop updating the status of Cloud Servers or Cloud Images in the affected data center. For example, if a server is shut down or rebooted from the Guest OS, the Admin UI/API will not reflect that change.

4) Except for the restrictions related to Cloud Servers and Images, all other Cloud functions will continue normally.

5) Once the maintenance is complete, the ability to take actions related to Cloud Servers and Cloud Images will be restored and the system will update the status of all deployed Cloud Servers.

This maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally.
Jun 12, 07:41 UTC
Jul 18, 2019

No incidents reported.

Jul 17, 2019
Completed - The scheduled maintenance has been completed.
Jul 17, 08:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 17, 03:30 UTC
Scheduled - SCHEDULED MAINTENANCE: ISRAEL (IL1) CLOUD BACKUP SERVICE

Impact: No impact is expected to client.

Dear Client

On the dates and times listed below engineers will be performing scheduled maintenance in following location. This maintenance is needed to perform upgrades to network switch devices supporting Cloud Backup Service. During the maintenance engineers will upgrade switch infrastructure to vendor approved code to prevent unplanned outage. No impact to Cloud Backup Services or client cloud servers is expected.

Change Reference Number: CHM121079514
Israel (IL1): Wednesday July 17th 06:30 AM Israel Daylight Time (03:30 UTC)
Expected Total Duration: 5 Hours

Note this maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally.
Jul 11, 09:05 UTC
Jul 16, 2019
Completed - The scheduled maintenance has been completed.
Jul 16, 11:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 16, 10:00 UTC
Update - Dear Client
After further testing it was determined there will be impact to Cloud UI/API and Client to Site VPN service during this change. Notification has been updated with new information.

Sorry for any inconvenience this may cause.
Jul 9, 17:06 UTC
Scheduled - Impact: During this maintenance clients will not be able to log into the Cloud UI/API or Client to Site VPN service for up to 30 minutes. No impact to client cloud servers or networks expected.

Dear Client

In preparation for future improvements Engineers will be implementing new LDAP services for the UI/API in the location listed below. During this maintenance clients will not be able to log into the Cloud UI/API or Client to Site VPN service. No impact to client cloud servers or networks expected.

Change Reference Number: CHM121849221
Canada: (CA1, CA2): Tuesday July 16th 06:00 AM Eastern Daylight Time (10:00 UTC)
Expected Total Duration: 1 Hours

Note this maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally.
Jul 2, 21:17 UTC
Jul 15, 2019
Completed - The scheduled maintenance has been completed.
Jul 15, 20:45 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 15, 20:00 UTC
Scheduled - We will be performing a minor software upgrade to the CloudControl API in all Geographic Regions on Monday July 15th during the normal software upgrade window in each region:

CloudControl Software Change Id: CCCHANGE-254
Time: See Software Upgrade Maintenance Schedule at https://docs.mcp-services.net/x/AQMu for the specific windows in each Geographic Region
Expected Total Duration: 45 minutes downtime

This minor API software upgrade addresses an issue affecting a small number of server deployment that was introduced in the Tuesday July 9th release. However, the impact is such that we are doing an upgrade outside the usual Tuesday/Thursday schedule. We apologize for any inconvenience.

During the software upgrade, all Cloud Servers and Network assets you've deployed will be unaffected. However, the CloudControl API will be unavailable during the software upgrade for the duration listed above. The CloudControl UI will remain available but will be unable to process requests in the affected Geographic Regions during their windows.
Jul 10, 20:51 UTC
Completed - The scheduled maintenance has been completed.
Jul 15, 19:45 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 15, 19:01 UTC
Scheduled - We will be performing a minor software upgrade to the CloudControl API in all Geographic Regions on Monday July 15th during the normal software upgrade window in each region:

CloudControl Software Change Id: CCCHANGE-254
Time: See Software Upgrade Maintenance Schedule at https://docs.mcp-services.net/x/AQMu for the specific windows in each Geographic Region
Expected Total Duration: 45 minutes downtime

This minor API software upgrade addresses an issue affecting a small number of server deployment that was introduced in the Tuesday July 9th release. However, the impact is such that we are doing an upgrade outside the usual Tuesday/Thursday schedule. We apologize for any inconvenience.

During the software upgrade, all Cloud Servers and Network assets you've deployed will be unaffected. However, the CloudControl API will be unavailable during the software upgrade for the duration listed above. The CloudControl UI will remain available but will be unable to process requests in the affected Geographic Regions during their windows.
Jul 10, 20:50 UTC
Completed - The scheduled maintenance has been completed.
Jul 15, 18:45 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 15, 18:01 UTC
Scheduled - We will be performing a minor software upgrade to the CloudControl API in all Geographic Regions on Monday July 15th during the normal software upgrade window in each region:

CloudControl Software Change Id: CCCHANGE-254
Time: See Software Upgrade Maintenance Schedule at https://docs.mcp-services.net/x/AQMu for the specific windows in each Geographic Region
Expected Total Duration: 45 minutes downtime

This minor API software upgrade addresses an issue affecting a small number of server deployment that was introduced in the Tuesday July 9th release. However, the impact is such that we are doing an upgrade outside the usual Tuesday/Thursday schedule. We apologize for any inconvenience.

During the software upgrade, all Cloud Servers and Network assets you've deployed will be unaffected. However, the CloudControl API will be unavailable during the software upgrade for the duration listed above. The CloudControl UI will remain available but will be unable to process requests in the affected Geographic Regions during their windows.
Jul 10, 20:49 UTC
Completed - The scheduled maintenance has been completed.
Jul 15, 12:45 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 15, 12:00 UTC
Scheduled - We will be performing a minor software upgrade to the CloudControl API in all Geographic Regions on Monday July 15th during the normal software upgrade window in each region:

CloudControl Software Change Id: CCCHANGE-254
Time: See Software Upgrade Maintenance Schedule at https://docs.mcp-services.net/x/AQMu for the specific windows in each Geographic Region
Expected Total Duration: 45 minutes downtime

This minor API software upgrade addresses an issue affecting a small number of server deployment that was introduced in the Tuesday July 9th release. However, the impact is such that we are doing an upgrade outside the usual Tuesday/Thursday schedule. We apologize for any inconvenience.

During the software upgrade, all Cloud Servers and Network assets you've deployed will be unaffected. However, the CloudControl API will be unavailable during the software upgrade for the duration listed above. The CloudControl UI will remain available but will be unable to process requests in the affected Geographic Regions during their windows.
Jul 10, 20:48 UTC
Completed - The scheduled maintenance has been completed.
Jul 15, 11:45 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 15, 11:00 UTC
Scheduled - We will be performing a minor software upgrade to the CloudControl API in all Geographic Regions on Monday July 15th during the normal software upgrade window in each region:

CloudControl Software Change Id: CCCHANGE-254
Time: See Software Upgrade Maintenance Schedule at https://docs.mcp-services.net/x/AQMu for the specific windows in each Geographic Region
Expected Total Duration: 45 minutes downtime

This minor API software upgrade addresses an issue affecting a small number of server deployment that was introduced in the Tuesday July 9th release. However, the impact is such that we are doing an upgrade outside the usual Tuesday/Thursday schedule. We apologize for any inconvenience.

During the software upgrade, all Cloud Servers and Network assets you've deployed will be unaffected. However, the CloudControl API will be unavailable during the software upgrade for the duration listed above. The CloudControl UI will remain available but will be unable to process requests in the affected Geographic Regions during their windows.
Jul 10, 20:48 UTC
Completed - The scheduled maintenance has been completed.
Jul 15, 10:45 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 15, 10:00 UTC
Scheduled - We will be performing a minor software upgrade to the CloudControl API in all Geographic Regions on Monday July 15th during the normal software upgrade window in each region:

CloudControl Software Change Id: CCCHANGE-254
Time: See Software Upgrade Maintenance Schedule at https://docs.mcp-services.net/x/AQMu for the specific windows in each Geographic Region
Expected Total Duration: 45 minutes downtime

This minor API software upgrade addresses an issue affecting a small number of server deployment that was introduced in the Tuesday July 9th release. However, the impact is such that we are doing an upgrade outside the usual Tuesday/Thursday schedule. We apologize for any inconvenience.

During the software upgrade, all Cloud Servers and Network assets you've deployed will be unaffected. However, the CloudControl API will be unavailable during the software upgrade for the duration listed above. The CloudControl UI will remain available but will be unable to process requests in the affected Geographic Regions during their windows.
Jul 10, 20:47 UTC
Completed - The scheduled maintenance has been completed.
Jul 15, 09:45 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 15, 09:00 UTC
Scheduled - We will be performing a minor software upgrade to the CloudControl API in all Geographic Regions on Monday July 15th during the normal software upgrade window in each region:

CloudControl Software Change Id: CCCHANGE-254
Time: See Software Upgrade Maintenance Schedule at https://docs.mcp-services.net/x/AQMu for the specific windows in each Geographic Region
Expected Total Duration: 45 minutes downtime

This minor API software upgrade addresses an issue affecting a small number of server deployment that was introduced in the Tuesday July 9th release. However, the impact is such that we are doing an upgrade outside the usual Tuesday/Thursday schedule. We apologize for any inconvenience.

During the software upgrade, all Cloud Servers and Network assets you've deployed will be unaffected. However, the CloudControl API will be unavailable during the software upgrade for the duration listed above. The CloudControl UI will remain available but will be unable to process requests in the affected Geographic Regions during their windows.
Jul 10, 20:46 UTC
Jul 14, 2019
Resolved - Issue resolved. Service has been restored.
Jul 14, 02:53 UTC
Investigating - Technical teams are engaged and investigating the issue
Jul 14, 02:09 UTC
Resolved - Dear Client,

Cloud UI service has been restored in AU region at 5:25 PM UTC.
Jul 14, 01:36 UTC
Investigating - Technical teams have been engaged and investigation in progress
Jul 13, 15:48 UTC
Jul 13, 2019
Resolved - Services have been restored
Jul 13, 16:18 UTC
Investigating - The network functionality via cloud in AMS01/EU7 will not be available. Teams are engaged in proceeding the next course of action.
Jul 13, 15:30 UTC
Completed - The scheduled maintenance has been completed.
Jul 13, 12:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 13, 04:00 UTC
Scheduled - Impact: The UI/API will be in Hypervisor Maintenance Mode for the duration of maintenance window. See note below for restrictions. There will be no impact to client cloud servers.

Dear Client

On the date listed below engineers will be performing maintenance in the following cloud locations. This maintenance is necessary to perform patching of the infrastructure supporting the cloud UI/API. During this maintenance we will be upgrading infrastructure devices to the latest vendor approved and tested OS patches. The Cloud UI/API will be in Hypervisor Maintenance Mode for duration of the maintenance see note below for client restrictions. Deployed client cloud servers will continue to function without interruption.

Change Reference Number: CHM121578755
North America (NA-All Locations): Friday July 12th 09:00 PM US Pacific Daylight Time (13/7 04:00 UTC)
Expected Total Duration: 8 Hours

Note: Hypervisor 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 and #3 below.
2) Starting one hour before the maintenance event, the Admin UI and API will stop accepting any requests for actions related to Cloud Servers or Cloud Images in the affected data center only. This means users will not be able to deploy new servers or images, start/stop/reboot/edit/delete existing servers or images, or start any new import/export actions. Please note that all deployed Cloud Servers will continue to function as normal - the system will simply block actions from being made using the Admin UI or API. Changes requested prior to the one-hour limit will continue to process with status updates in the Admin UI or API until the event begins.
3) Beginning with the start of the maintenance window, the Admin UI and API will stop updating the status of Cloud Servers or Cloud Images in the affected data center. For example, if a server is shut down or rebooted from the Guest OS, the Admin UI/API will not reflect that change.
4) Except for the restrictions related to Cloud Servers and Images, all other Cloud functions will continue normally.
5) Once the maintenance is complete, the ability to take actions related to Cloud Servers and Cloud Images will be restored and the system will update the status of all deployed Cloud Servers.

This maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally.
Jun 24, 20:14 UTC
Completed - The scheduled maintenance has been completed.
Jul 13, 09:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 13, 04:00 UTC
Scheduled - Impact: Managed Hosting clients using the NAS services with CIFS shares will see a brief outage during failover of NAS Controller. Clients using NFS / SAN shares are not expected to see impact.

Dear Client

On the date listed below Operations will be performing maintenance in the locations below. This maintenance is to perform upgrade of NAS controllers to latest vendor recommended release. During the failover of the NAS controllers Clients using CIFS Shares will see brief loss of service typically less than 5 seconds. All other clients are not expected to see any impact.

Change Reference Number: CHM121758342
US EAST (ASH02): Friday July 12th 09:00 PM US Pacific Daylight Time (13/7 04:00 UTC)
Expected Total Duration: 5 Hours

Note this maintenance is specific only to the affected data center location and other Geographic Regions will continue to function normally.
Jul 10, 01:01 UTC
Completed - The scheduled maintenance has been completed.
Jul 13, 00:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 12, 16:37 UTC
Scheduled - Impact: The UI/API will be in Network Maintenance Mode for duration of maintenance see note below for restrictions.

Dear Client

On the date listed below engineers will be performing maintenance in the following cloud locations. This maintenance is necessary to perform patching of the infrastructure supporting the cloud UI/API. During this maintenance, we will be upgrading infrastructure devices to the latest vendor approved and tested OS patches. The Cloud UI/API will be in Network Maintenance Mode for duration of maintenance see note below for client restrictions. Deployed client cloud servers will continue to function without interruption.

Change Reference Number: CHM121396350
Melbourne (AU10): Friday July 12th 06:00 AM Australia Eastern Standard Time (20:00 UTC)
Expected Total Duration: 4 Hours

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.
Jul 12, 16:23 UTC
Completed - The scheduled maintenance has been completed.
Jul 13, 00:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 12, 18:00 UTC
Scheduled - Impact: No client impact expected, however medium risk of disruptions to Cloud and Cloud Services for SAP.

Dear Client

On the dates and times listed below engineers will be performing capacity maintenance. We will be performing power maintenance to allow for capacity increases. Engineers will be working on devices in the following locations supporting both Cloud and Cloud Services for SAP. No impact to services is expected, however this is medium risk maintenance with possibility of disruption of service.

Change Reference Number: CHM121676171
Johannesburg: (AF1,AF3,AF5): Friday July 12th 08:00 PM South Africa Standard Time (18:00 PM UTC)
Expected Total Duration: 6 Hours

Note this maintenance is specific only to the affected data center location and other Geographic Regions will continue to function normally
Jun 25, 23:42 UTC
Jul 12, 2019
Completed - The scheduled maintenance has been completed.
Jul 12, 23:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 12, 19:00 UTC
Update - Dear Client,
Due to an unexpected hardware failure this morning the follow maintenance CHM121792642 impact has to be modified for us to complete below change and address the failure. The Cloud/UI will now be put into Network Maintenance mode for the duration of the change window see note below for details. No impact to client cloud servers or networks is expected.

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.
Jul 12, 17:03 UTC
Scheduled - Impact: No client impact is expected.

Dear Client

On the date listed below engineers will be performing maintenance in the following cloud and manage hosting locations. Engineers have identified a potential issue with secondary router in this location. Per vendor recommendation we will be upgrading device to new IOS. This device is currently serving secondary role. There is no expectation of impact to our clients.

Change Reference Number: CHM121792642
Frankfurt (EU6,FRA01): Friday July 12th 09:00 PM Central European Standard (19:00 UTC)
Expected Total Duration: 4 Hours

Note this maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally.
Jun 30, 23:52 UTC
Completed - The scheduled maintenance has been completed.
Jul 12, 23:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 12, 19:00 UTC
Scheduled - Impact: Managed Hosting clients using the NAS services with CIFS shares will see a brief outage during failover of NAS Controller. Clients using NFS shares are not expected to see impact.

Dear Client

On the date listed below Operations will be performing maintenance in the locations below. This maintenance is to perform upgrade of NAS controllers to latest vendor recommended release. During the failover of the NAS controllers Clients using CIFS Shares will see brief loss of service typically less than 5 seconds. All other clients are not expected to see any impact.


Change Reference Number: CHM121727745
Amsterdam (AMS01): Friday July 12th 09:00 PM Central European Standard (19:00 UTC)
Expected Total Duration: 4 Hours

Note this maintenance is specific only to the affected data center location and other Geographic Regions will continue to function normally.
Jun 25, 23:45 UTC
Completed - The scheduled maintenance has been completed.
Jul 12, 22:01 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 12, 18:00 UTC
Scheduled - Impact: The UI/API will be in Hypervisor Maintenance Mode for duration of maintenance see note below for restrictions.

Dear Client

On the date listed below engineers will be performing maintenance in the following cloud locations. This maintenance is necessary to performing upgrades of the infrastructure supporting the Hypervisor infrastructure. During this maintenance we will be upgrading hypervisor management devices to the latest product approved and tested version. The Cloud UI/API will be in Hypervisor Maintenance Mode for duration of maintenance. See note below for client restrictions. Deployed client cloud servers will continue to function without interruption.

Change Reference Number: CHM121623862
Johannesburg (AF1): Friday July 12th 08:00 PM South Africa Standard Time (18:00 PM UTC)
Expected Total Duration: 4 Hours

Note: Hypervisor 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 and #3 below.

2) Starting one hour before the maintenance event, the Admin UI and API will stop accepting any requests for actions related to Cloud Servers or Cloud Images in the affected data center only. This means users will not be able to deploy new servers or images, start/stop/reboot/edit/delete existing servers or images, or start any new import/export actions. Please note that all deployed Cloud Servers will continue to function as normal - the system will simply block actions from being made using the Admin UI or API. Changes requested prior to the one-hour limit will continue to process with status updates in the Admin UI or API until the event begins.

3) Beginning with the start of the maintenance window, the Admin UI and API will stop updating the status of Cloud Servers or Cloud Images in the affected data center. For example, if a server is shut down or rebooted from the Guest OS, the Admin UI/API will not reflect that change.

4) Except for the restrictions related to Cloud Servers and Images, all other Cloud functions will continue normally.

5) Once the maintenance is complete, the ability to take actions related to Cloud Servers and Cloud Images will be restored and the system will update the status of all deployed Cloud Servers.

This maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally.
Jun 13, 23:29 UTC
Completed - The scheduled maintenance has been completed.
Jul 12, 22:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 12, 18:00 UTC
Scheduled - Impact: The UI/API will be in Hypervisor Maintenance Mode for duration of maintenance see note below for restrictions.

Dear Client

On the date listed below engineers will be performing maintenance in the following cloud locations. This maintenance is necessary to performing upgrades of the infrastructure supporting the Hypervisor infrastructure. During this maintenance we will be upgrading hypervisor management devices to the latest product approved and tested version. The Cloud UI/API will be in Hypervisor Maintenance Mode for duration of maintenance. See note below for client restrictions. Deployed client cloud servers will continue to function without interruption.

Change Reference Number: CHM121539856
Israel (IL2): Friday July 12th 09:00 PM Israel Daylight Time (18:00 UTC)
Expected Total Duration: 4 Hours

Note: Hypervisor 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 and #3 below.
2) Starting one hour before the maintenance event, the Admin UI and API will stop accepting any requests for actions related to Cloud Servers or Cloud Images in the affected data center only. This means users will not be able to deploy new servers or images, start/stop/reboot/edit/delete existing servers or images, or start any new import/export actions. Please note that all deployed Cloud Servers will continue to function as normal - the system will simply block actions from being made using the Admin UI or API. Changes requested prior to the one-hour limit will continue to process with status updates in the Admin UI or API until the event begins.
3) Beginning with the start of the maintenance window, the Admin UI and API will stop updating the status of Cloud Servers or Cloud Images in the affected data center. For example, if a server is shut down or rebooted from the Guest OS, the Admin UI/API will not reflect that change.
4) Except for the restrictions related to Cloud Servers and Images, all other Cloud functions will continue normally.
5) Once the maintenance is complete, the ability to take actions related to Cloud Servers and Cloud Images will be restored and the system will update the status of all deployed Cloud Servers.

This maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally.
Jun 13, 23:14 UTC
Completed - The scheduled maintenance has been completed.
Jul 12, 22:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 12, 18:00 UTC
Scheduled - Impact: The UI/API will be in Hypervisor Maintenance Mode for duration of maintenance see note below for restrictions.

Dear Client

On the date listed below engineers will be performing maintenance in the following cloud locations. This maintenance is necessary to performing upgrades of the infrastructure supporting the Hypervisor infrastructure. During this maintenance we will be upgrading hypervisor management devices to the latest product approved and tested version. The Cloud UI/API will be in Hypervisor Maintenance Mode for duration of maintenance. See note below for client restrictions. Deployed client cloud servers will continue to function without interruption.

Change Reference Number: CHM121538619
Johannesburg: (AF3): Friday July 12th 08:00 PM South Africa Standard Time (18:00 PM UTC)
Expected Total Duration: 4 Hours

Note: Hypervisor 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 and #3 below.

2) Starting one hour before the maintenance event, the Admin UI and API will stop accepting any requests for actions related to Cloud Servers or Cloud Images in the affected data center only. This means users will not be able to deploy new servers or images, start/stop/reboot/edit/delete existing servers or images, or start any new import/export actions. Please note that all deployed Cloud Servers will continue to function as normal - the system will simply block actions from being made using the Admin UI or API. Changes requested prior to the one-hour limit will continue to process with status updates in the Admin UI or API until the event begins.

3) Beginning with the start of the maintenance window, the Admin UI and API will stop updating the status of Cloud Servers or Cloud Images in the affected data center. For example, if a server is shut down or rebooted from the Guest OS, the Admin UI/API will not reflect that change.

4) Except for the restrictions related to Cloud Servers and Images, all other Cloud functions will continue normally.

5) Once the maintenance is complete, the ability to take actions related to Cloud Servers and Cloud Images will be restored and the system will update the status of all deployed Cloud Servers.

This maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally.
May 31, 23:25 UTC
Completed - The scheduled maintenance has been completed.
Jul 12, 22:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 12, 18:00 UTC
Scheduled - Impact: The UI/API will be in Hypervisor Maintenance Mode for duration of maintenance see note below for restrictions.

Dear Client

On the date listed below engineers will be performing maintenance in the following cloud locations. This maintenance is necessary to performing upgrades of the infrastructure supporting the Hypervisor infrastructure. During this maintenance we will be upgrading hypervisor management devices to the latest product approved and tested version. The Cloud UI/API will be in Hypervisor Maintenance Mode for duration of maintenance. See note below for client restrictions. Deployed client cloud servers will continue to function without interruption.

Change Reference Number: CHM121538488
Israel (IL1): Friday July 12th 09:00 PM Israel Daylight Time (18:00 UTC)
Expected Total Duration: 4 Hours

Note: Hypervisor 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 and #3 below.
2) Starting one hour before the maintenance event, the Admin UI and API will stop accepting any requests for actions related to Cloud Servers or Cloud Images in the affected data center only. This means users will not be able to deploy new servers or images, start/stop/reboot/edit/delete existing servers or images, or start any new import/export actions. Please note that all deployed Cloud Servers will continue to function as normal - the system will simply block actions from being made using the Admin UI or API. Changes requested prior to the one-hour limit will continue to process with status updates in the Admin UI or API until the event begins.
3) Beginning with the start of the maintenance window, the Admin UI and API will stop updating the status of Cloud Servers or Cloud Images in the affected data center. For example, if a server is shut down or rebooted from the Guest OS, the Admin UI/API will not reflect that change.
4) Except for the restrictions related to Cloud Servers and Images, all other Cloud functions will continue normally.
5) Once the maintenance is complete, the ability to take actions related to Cloud Servers and Cloud Images will be restored and the system will update the status of all deployed Cloud Servers.

This maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally.
May 31, 23:22 UTC
Resolved - Service has been restored. Issue is resolved.
Jul 12, 19:12 UTC
Update - Teams are engaged and investigating.
Jul 12, 18:42 UTC
Investigating - Site is put in Network Maintenance Mode, Engineer’s are engaged and investigating...
Jul 12, 18:05 UTC
Completed - The scheduled maintenance has been completed.
Jul 12, 18:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 12, 17:30 UTC
Scheduled - Impact: No impact to clients expected.

Dear Client

On the dates listed below engineers will be adding additional ISP connection to follow location. Client traffic will remain on primary link no fail-overs expected . Engineers do not expect any impact to our clients.

Change Reference Number: CHM121936994
London (EU2,EU8, LHR03): Friday July 12th 07:30PM Central European Standard (17:30 UTC)
Expected Total Duration: 1 Hours

Note this maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally.
Jul 11, 16:26 UTC
Completed - The scheduled maintenance has been completed.
Jul 12, 16:01 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 12, 12:00 UTC
Scheduled - Impact: The UI/API will be in Hypervisor Maintenance Mode for duration of maintenance see note below for restrictions.

Dear Client

On the date listed below engineers will be performing maintenance in the following cloud locations. This maintenance is necessary to performing upgrades of the infrastructure supporting the Hypervisor infrastructure. During this maintenance we will be upgrading hypervisor management devices to the latest product approved and tested version. The Cloud UI/API will be in Hypervisor Maintenance Mode for duration of maintenance. See note below for client restrictions. Deployed client cloud servers will continue to function without interruption.

Change Reference Number: CHM121677214
Malaysia (AP14): Friday July 12th 09:00 PM Japan Standard (12:00 UTC)
Expected Total Duration: 4 Hours

Note: Hypervisor 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 and #3 below.

2) Starting one hour before the maintenance event, the Admin UI and API will stop accepting any requests for actions related to Cloud Servers or Cloud Images in the affected data center only. This means users will not be able to deploy new servers or images, start/stop/reboot/edit/delete existing servers or images, or start any new import/export actions. Please note that all deployed Cloud Servers will continue to function as normal - the system will simply block actions from being made using the Admin UI or API. Changes requested prior to the one-hour limit will continue to process with status updates in the Admin UI or API until the event begins.

3) Beginning with the start of the maintenance window, the Admin UI and API will stop updating the status of Cloud Servers or Cloud Images in the affected data center. For example, if a server is shut down or rebooted from the Guest OS, the Admin UI/API will not reflect that change.

4) Except for the restrictions related to Cloud Servers and Images, all other Cloud functions will continue normally.

5) Once the maintenance is complete, the ability to take actions related to Cloud Servers and Cloud Images will be restored and the system will update the status of all deployed Cloud Servers.

This maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally.
Jun 14, 00:09 UTC
Completed - The scheduled maintenance has been completed.
Jul 12, 16:01 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 12, 12:00 UTC
Scheduled - Impact: The UI/API will be in Hypervisor Maintenance Mode for duration of maintenance see note below for restrictions.

Dear Client

On the date listed below engineers will be performing maintenance in the following cloud locations. This maintenance is necessary to performing upgrades of the infrastructure supporting the Hypervisor infrastructure. During this maintenance we will be upgrading hypervisor management devices to the latest product approved and tested version. The Cloud UI/API will be in Hypervisor Maintenance Mode for duration of maintenance. See note below for client restrictions. Deployed client cloud servers will continue to function without interruption.

Change Reference Number: CHM121623790
Malaysia (AP13): Friday July 12th 09:00 PM Japan Standard (12:00 UTC)
Expected Total Duration: 4 Hours

Note: Hypervisor 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 and #3 below.

2) Starting one hour before the maintenance event, the Admin UI and API will stop accepting any requests for actions related to Cloud Servers or Cloud Images in the affected data center only. This means users will not be able to deploy new servers or images, start/stop/reboot/edit/delete existing servers or images, or start any new import/export actions. Please note that all deployed Cloud Servers will continue to function as normal - the system will simply block actions from being made using the Admin UI or API. Changes requested prior to the one-hour limit will continue to process with status updates in the Admin UI or API until the event begins.

3) Beginning with the start of the maintenance window, the Admin UI and API will stop updating the status of Cloud Servers or Cloud Images in the affected data center. For example, if a server is shut down or rebooted from the Guest OS, the Admin UI/API will not reflect that change.

4) Except for the restrictions related to Cloud Servers and Images, all other Cloud functions will continue normally.

5) Once the maintenance is complete, the ability to take actions related to Cloud Servers and Cloud Images will be restored and the system will update the status of all deployed Cloud Servers.

This maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally.
Jun 14, 00:07 UTC
Completed - The scheduled maintenance has been completed.
Jul 12, 16:01 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 12, 12:00 UTC
Scheduled - Impact: The UI/API will be in Hypervisor Maintenance Mode for duration of maintenance see note below for restrictions.

Dear Client

On the date listed below engineers will be performing maintenance in the following cloud locations. This maintenance is necessary to performing upgrades of the infrastructure supporting the Hypervisor infrastructure. During this maintenance we will be upgrading hypervisor management devices to the latest product approved and tested version. The Cloud UI/API will be in Hypervisor Maintenance Mode for duration of maintenance. See note below for client restrictions. Deployed client cloud servers will continue to function without interruption.

Change Reference Number: CHM121623850
Hong Kong (AP2): Friday July 12th 09:00 PM Japan Standard (12:00 UTC)
Expected Total Duration: 4 Hours

Note: Hypervisor 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 and #3 below.

2) Starting one hour before the maintenance event, the Admin UI and API will stop accepting any requests for actions related to Cloud Servers or Cloud Images in the affected data center only. This means users will not be able to deploy new servers or images, start/stop/reboot/edit/delete existing servers or images, or start any new import/export actions. Please note that all deployed Cloud Servers will continue to function as normal - the system will simply block actions from being made using the Admin UI or API. Changes requested prior to the one-hour limit will continue to process with status updates in the Admin UI or API until the event begins.

3) Beginning with the start of the maintenance window, the Admin UI and API will stop updating the status of Cloud Servers or Cloud Images in the affected data center. For example, if a server is shut down or rebooted from the Guest OS, the Admin UI/API will not reflect that change.

4) Except for the restrictions related to Cloud Servers and Images, all other Cloud functions will continue normally.

5) Once the maintenance is complete, the ability to take actions related to Cloud Servers and Cloud Images will be restored and the system will update the status of all deployed Cloud Servers.

This maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally.
Jun 13, 23:27 UTC
Completed - The scheduled maintenance has been completed.
Jul 12, 14:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 12, 11:00 UTC
Scheduled - Impact: The UI/API will be in Network Maintenance Mode for duration of maintenance see note below for restrictions.

Dear Client

On the date listed below engineers will be performing maintenance in the following cloud locations. This maintenance is necessary to perform patching of the infrastructure supporting the cloud UI/API. During this maintenance, we will be upgrading infrastructure devices to the latest vendor approved and tested OS patches. The Cloud UI/API will be in Network Maintenance Mode for duration of maintenance see note below for client restrictions. Deployed client cloud servers will continue to function without interruption.

Change Reference Number: CHM121396350
Melbourne (AU10): Friday July 12th 09:00 PM Australia Eastern Standard Time (11:00 UTC)
Expected Total Duration: 3 Hours

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.
Jul 2, 21:28 UTC
Completed - The scheduled maintenance has been completed.
Jul 12, 13:01 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 12, 10:00 UTC
Scheduled - Impact: No impact to clients is expected

Dear Client

On the date listed below engineers will be performing scheduled maintenance in the location listed below. This maintenance is necessary to perform upgrades to the storage infrastructure supporting the Managed Hosting San services. During this maintenance we will be upgrading storage switch devices to latest vendor recommended IOS. Although this type of maintenance has been performed in the past without impact, there is a low risk of latency and service disruption to Managed Hosting SAN Services.

Change Reference Number: CHM121712549
Sydney (SYD01): Friday July 12th 09:00 PM Australia Eastern Daylight Time (10:00 UTC)
Expected Total Duration: 3 Hours

Note this maintenance is specific only to the affected data center location and other Geographic Regions will continue to function normally.
Jun 21, 20:15 UTC
Jul 11, 2019
Completed - The scheduled maintenance has been completed.
Jul 11, 21:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 11, 09:00 UTC
Update - We will be undergoing scheduled maintenance during this time.
Jul 3, 17:38 UTC
Scheduled - The ability to replicate Cloud Snapshots between AU9 (Australia - Sydney MCP2) and AU10 (Australia - Melbourne MCP2) will be made available on Thursday, July 11th

CloudControl Change Id: OEC-11542
Time: Sometime after Thursday July 11th business day
Expected Total Duration: Users can identify availability as described in Identify Hardware Specifications and Capabilities Available in a Data Center Location - https://docs.mcp-services.net/x/nAAu

This new feature allows the user to replicate all Cloud System Snapshots to another location in the same Geographic Region, and to use those replicated snapshots to create Cloud Servers in the replicated data center location. The feature is available to all Advanced Snapshot plan users. There is an additional hourly rate for use of the feature. For details, see:

Introduction to Cloud Server Snapshots - https://docs.mcp-services.net/x/DoBk
How to Manage Snapshot Replication on a Cloud Server - https://docs.mcp-services.net/x/HAKZ
How to Create a Snapshot Preview Server from a Replicated Snapshot - https://docs.mcp-services.net/x/OQKZ
Introduction to Usage Reporting - https://docs.mcp-services.net/x/7IBs

There is no CloudControl UI or API downtime nor impact to any existing Cloud Servers and Networks due to this change. This notification is for informational purposes only.
Jul 3, 17:32 UTC
Completed - The scheduled maintenance has been completed.
Jul 11, 21:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 11, 09:00 UTC
Scheduled - The ability to replicate Cloud Snapshots between AU9 (Australia - Sydney MCP2) and AU11 (New_Zealand) will be made available on Thursday, July 11th

CloudControl Change Id: OEC-11543
Time: Sometime after Thursday July 11th business day
Expected Total Duration: Users can identify availability as described in Identify Hardware Specifications and Capabilities Available in a Data Center Location - https://docs.mcp-services.net/x/nAAu

This new feature allows the user to replicate all Cloud System Snapshots to another location in the same Geographic Region, and to use those replicated snapshots to create Cloud Servers in the replicated data center location. The feature is available to all Advanced Snapshot plan users. There is an additional hourly rate for use of the feature. For details, see:

Introduction to Cloud Server Snapshots - https://docs.mcp-services.net/x/DoBk
How to Manage Snapshot Replication on a Cloud Server - https://docs.mcp-services.net/x/HAKZ
How to Create a Snapshot Preview Server from a Replicated Snapshot - https://docs.mcp-services.net/x/OQKZ
Introduction to Usage Reporting - https://docs.mcp-services.net/x/7IBs

There is no CloudControl UI or API downtime nor impact to any existing Cloud Servers and Networks due to this change. This notification is for informational purposes only.
Jul 3, 17:28 UTC
Completed - The scheduled maintenance has been completed.
Jul 11, 06:01 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 10, 18:01 UTC
Scheduled - On June 24 at 18:00 UTC, we performed a maintenance event to migrate to new Burstable Standard/High Performance/Economy Disk Speeds in AF3 (Johannesburg MCP 2.0) as described in https://cloud-status.dimensiondata.com/incidents/zwfsxnql8h1b

As described below, a small number of servers were successful. We will be addressing servers that were not successfully updated on July 10th at 18:00 UTC:

CloudControl Change Id: OEC-11550
Time: 08:00 PM South Africa Standard Time (18:00 UTC)
Expected Total Duration: Up to 12 Hours

The June 24th change was designed to implement changes to all existing disks to allow them to burst only up the following IOPS and Throughput limits based on their disk speed:

ECONOMY: Greater of 100 IOPS or 0.5 IOPS/GB based on the size of the disk
STANDARD: Greater of 500 IOPS or 3 IOPS/GB based on the size of the disk
HIGH PERFORMANCE: Greater of 800 IOPS or 6 IOPS/GB based on the size of the disk
ALL THREE SPEEDS: Throughput limit equal to the IOPS maximum x 16 KB (Kilobytes). This limit applies in addition to the above IOPS limit.

A review has indicated a small number of servers were not properly implemented with the change, leading to inconsistent performance.

In this event, the system will re-attempt the change ONLY on servers that are not conforming to the limits above. All other existing servers will be unaffected. If an affected server is running when the change is implemented, the system will vMotion the server so that the changes take immediate effect. No restart is required.

For more information please refer to the following two articles:

Introduction to Cloud Server Local Storage ("Disks") and Disk Speeds - https://docs.mcp-services.net/x/UwIu
How do I determine if my Server Requires a Restart Using REST API? - https://docs.mcp-services.net/x/QgSZ
Jul 3, 19:30 UTC
Jul 10, 2019
Resolved - Network connectivity issue has been resolved at TLV01 .
Jul 10, 07:30 UTC
Investigating - Degradation of network services observed at TLV01.
Jul 10, 06:23 UTC
Resolved - Service was restored without any intervention by any Technical teams.
Jul 10, 04:22 UTC
Monitoring - Intermittent connectivity not experienced at this time. Teams to further monitor.
Jul 10, 04:10 UTC
Investigating - Network connectivity issue in TLV01. Engineers are engaged and investigating
Jul 10, 03:35 UTC
Jul 9, 2019
Completed - The scheduled maintenance has been completed.
Jul 9, 21:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 9, 09:00 UTC
Scheduled - We will be removing some older OS Images that are at the end of their support cycle.

CloudControl Change Id: IMG-177
Time: OS Images will be removed sometime during July 9, 2019 in each location
Expected Total Duration: None - the images will simply be removed from the UI and API

The 2 images that are being retired are:

Win2008 R2 Ent with MS SQL 2008 R2 Ent
Win2008 R2 Ent with MS SQL 2008 R2 Std

Retired means that these OS Images will no longer receive security patches or be supported by Microsoft, and so they will no longer be available to deploy from our Images and Applications Dashboard described in:

Navigating the Images and Applications Dashboard - https://docs.mcp-services.net/x/iwwu

This change does NOT impact existing Client Images. If you wish to continue using these images, please create your own Client Image prior to the decommission as described in:

How to Clone a Cloud Server to Create a Client Image - https://docs.mcp-services.net/x/pwMk

The CloudControl UI, API, and all existing Cloud Servers are unaffected by this change. This announcement is for informational purposes prior to OS Image removal.

Any clients continuing to use existing servers or Images with a retired OS need to understand that they are no longer supported by the Vendor or on the Cloud. In all cases, Cloud support for retired images will be rendered on a "best effort" basis only.
Jun 27, 23:40 UTC
Completed - The scheduled maintenance has been completed.
Jul 9, 20:45 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 9, 20:00 UTC
Scheduled - We will be performing a minor software upgrade to the CloudControl API in all Geographic Regions on Tuesday July 9th during the normal software upgrade window in each region:

CloudControl Software Change Id: CCCHANGE-250
Time: See Software Upgrade Maintenance Schedule at https://docs.mcp-services.net/x/AQMu for the specific windows in each Geographic Region
Expected Total Duration: 45 minutes downtime

This minor API software upgrade includes enhancements that will mostly not be visible until the UI release in late August. However, there are two changes worth noting in the meantime:

ADVANCED VIRTUALIZATION SETTING ENFORCEMENT

The previous March release added support for tracking Advanced Virtualization Settings on Images. This release adds support for tracking Advanced Virtualization Settings on Cloud Servers.

There is one immediate change associated with the API release. The system will now prevent deployment of Cloud Servers from Images with specific Advanced Virtualization Settings. You can view the settings of an image on the Image Details screen as described in Navigating the Images and Applications Dashboard - https://docs.mcp-services.net/x/iwwu

Specifically, deployment of servers from Images with any of the following settings is prohibited in most data center locations:

Nested Hardware Virtualization = TRUE
CPU Latency Sensitivity = HIGH
Numa Autosize = TRUE
Enable Host Info to VM Tools = TRUE

The only exception to this prohibition is server deployment into specific hypervisor clusters designed for SAP HANA support. As of this release, these clusters exist only in specific Private Cloud locations. The August UI release will expose the setting enabling support in the Data Center capabilities screen. In the meantime, if you are using a Private Cloud location and are unsure of SAP HANA support, please open a support case.

Please note there is a very small number of Client Images with such settings. However, if a Customer Image has these settings, the system will prevent deployment until the Image has been modified to remove the relevant setting. Modification of such settings must be done via API until the August UI release.

For more details, see

Introduction to OS (Operating System) and Client Images
https://docs.mcp-services.net/x/UQSZ

How to Modify Advanced Virtualization Settings on a Client Image using REST API
https://docs.mcp-services.net/x/DwSy


API SUPPORT FOR RE-IP ADDRESSING AS PART OF DRS FOR CLOUD

This release provides API support for a new “re-ip address” feature in the DRS for Cloud offering. When DRS replicates Source Server disk content to the Target Server location, the guest OS settings for IP addresses of the NICs are inherited from the source. This behavior is often undesirable. The Re-IP address function allows users to impose specific IP address settings as part of the Preview function. Although the function is API-only until the UI release in August, it is relatively simple to apply in the current MCP 1.0 to MCP 2.0 migration use case.

For more details, see:

Introduction to DRS for Cloud - NIC IP Configuration after Preview of a Consistency Group
https://docs.mcp-services.net/x/qgE8#IntroductiontoDRSforCloud-NICIPConfigurationafterPreviewofaConsistencyGroup

How to Set Re-IP Address Rules for a Target Server in a DRS Server Pair
https://docs.mcp-services.net/x/9AOy

During the software upgrade, all Cloud Servers and Network assets you've deployed will be unaffected. However, the CloudControl API will be unavailable during the software upgrade for the duration listed above. The CloudControl UI will remain available but will be unable to process requests in the affected Geographic Regions during their windows.
Jul 3, 00:19 UTC
Completed - The scheduled maintenance has been completed.
Jul 9, 19:45 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 9, 19:00 UTC
Scheduled - We will be performing a minor software upgrade to the CloudControl API in all Geographic Regions on Tuesday July 9th during the normal software upgrade window in each region:

CloudControl Software Change Id: CCCHANGE-250
Time: See Software Upgrade Maintenance Schedule at https://docs.mcp-services.net/x/AQMu for the specific windows in each Geographic Region
Expected Total Duration: 45 minutes downtime

This minor API software upgrade includes enhancements that will mostly not be visible until the UI release in late August. However, there are two changes worth noting in the meantime:

ADVANCED VIRTUALIZATION SETTING ENFORCEMENT

The previous March release added support for tracking Advanced Virtualization Settings on Images. This release adds support for tracking Advanced Virtualization Settings on Cloud Servers.

There is one immediate change associated with the API release. The system will now prevent deployment of Cloud Servers from Images with specific Advanced Virtualization Settings. You can view the settings of an image on the Image Details screen as described in Navigating the Images and Applications Dashboard - https://docs.mcp-services.net/x/iwwu

Specifically, deployment of servers from Images with any of the following settings is prohibited in most data center locations:

Nested Hardware Virtualization = TRUE
CPU Latency Sensitivity = HIGH
Numa Autosize = TRUE
Enable Host Info to VM Tools = TRUE

The only exception to this prohibition is server deployment into specific hypervisor clusters designed for SAP HANA support. As of this release, these clusters exist only in specific Private Cloud locations. The August UI release will expose the setting enabling support in the Data Center capabilities screen. In the meantime, if you are using a Private Cloud location and are unsure of SAP HANA support, please open a support case.

Please note there is a very small number of Client Images with such settings. However, if a Customer Image has these settings, the system will prevent deployment until the Image has been modified to remove the relevant setting. Modification of such settings must be done via API until the August UI release.

For more details, see

Introduction to OS (Operating System) and Client Images
https://docs.mcp-services.net/x/UQSZ

How to Modify Advanced Virtualization Settings on a Client Image using REST API
https://docs.mcp-services.net/x/DwSy


API SUPPORT FOR RE-IP ADDRESSING AS PART OF DRS FOR CLOUD

This release provides API support for a new “re-ip address” feature in the DRS for Cloud offering. When DRS replicates Source Server disk content to the Target Server location, the guest OS settings for IP addresses of the NICs are inherited from the source. This behavior is often undesirable. The Re-IP address function allows users to impose specific IP address settings as part of the Preview function. Although the function is API-only until the UI release in August, it is relatively simple to apply in the current MCP 1.0 to MCP 2.0 migration use case.

For more details, see:

Introduction to DRS for Cloud - NIC IP Configuration after Preview of a Consistency Group
https://docs.mcp-services.net/x/qgE8#IntroductiontoDRSforCloud-NICIPConfigurationafterPreviewofaConsistencyGroup

How to Set Re-IP Address Rules for a Target Server in a DRS Server Pair
https://docs.mcp-services.net/x/9AOy

During the software upgrade, all Cloud Servers and Network assets you've deployed will be unaffected. However, the CloudControl API will be unavailable during the software upgrade for the duration listed above. The CloudControl UI will remain available but will be unable to process requests in the affected Geographic Regions during their windows.
Jul 3, 00:18 UTC
Completed - The scheduled maintenance has been completed.
Jul 9, 18:45 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 9, 18:00 UTC
Scheduled - We will be performing a minor software upgrade to the CloudControl API in all Geographic Regions on Tuesday July 9th during the normal software upgrade window in each region:

CloudControl Software Change Id: CCCHANGE-250
Time: See Software Upgrade Maintenance Schedule at https://docs.mcp-services.net/x/AQMu for the specific windows in each Geographic Region
Expected Total Duration: 45 minutes downtime

This minor API software upgrade includes enhancements that will mostly not be visible until the UI release in late August. However, there are two changes worth noting in the meantime:

ADVANCED VIRTUALIZATION SETTING ENFORCEMENT

The previous March release added support for tracking Advanced Virtualization Settings on Images. This release adds support for tracking Advanced Virtualization Settings on Cloud Servers.

There is one immediate change associated with the API release. The system will now prevent deployment of Cloud Servers from Images with specific Advanced Virtualization Settings. You can view the settings of an image on the Image Details screen as described in Navigating the Images and Applications Dashboard - https://docs.mcp-services.net/x/iwwu

Specifically, deployment of servers from Images with any of the following settings is prohibited in most data center locations:

Nested Hardware Virtualization = TRUE
CPU Latency Sensitivity = HIGH
Numa Autosize = TRUE
Enable Host Info to VM Tools = TRUE

The only exception to this prohibition is server deployment into specific hypervisor clusters designed for SAP HANA support. As of this release, these clusters exist only in specific Private Cloud locations. The August UI release will expose the setting enabling support in the Data Center capabilities screen. In the meantime, if you are using a Private Cloud location and are unsure of SAP HANA support, please open a support case.

Please note there is a very small number of Client Images with such settings. However, if a Customer Image has these settings, the system will prevent deployment until the Image has been modified to remove the relevant setting. Modification of such settings must be done via API until the August UI release.

For more details, see

Introduction to OS (Operating System) and Client Images
https://docs.mcp-services.net/x/UQSZ

How to Modify Advanced Virtualization Settings on a Client Image using REST API
https://docs.mcp-services.net/x/DwSy


API SUPPORT FOR RE-IP ADDRESSING AS PART OF DRS FOR CLOUD

This release provides API support for a new “re-ip address” feature in the DRS for Cloud offering. When DRS replicates Source Server disk content to the Target Server location, the guest OS settings for IP addresses of the NICs are inherited from the source. This behavior is often undesirable. The Re-IP address function allows users to impose specific IP address settings as part of the Preview function. Although the function is API-only until the UI release in August, it is relatively simple to apply in the current MCP 1.0 to MCP 2.0 migration use case.

For more details, see:

Introduction to DRS for Cloud - NIC IP Configuration after Preview of a Consistency Group
https://docs.mcp-services.net/x/qgE8#IntroductiontoDRSforCloud-NICIPConfigurationafterPreviewofaConsistencyGroup

How to Set Re-IP Address Rules for a Target Server in a DRS Server Pair
https://docs.mcp-services.net/x/9AOy

During the software upgrade, all Cloud Servers and Network assets you've deployed will be unaffected. However, the CloudControl API will be unavailable during the software upgrade for the duration listed above. The CloudControl UI will remain available but will be unable to process requests in the affected Geographic Regions during their windows.
Jul 3, 00:17 UTC
Completed - The scheduled maintenance has been completed.
Jul 9, 12:45 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 9, 12:00 UTC
Scheduled - We will be performing a minor software upgrade to the CloudControl API in all Geographic Regions on Tuesday July 9th during the normal software upgrade window in each region:

CloudControl Software Change Id: CCCHANGE-250
Time: See Software Upgrade Maintenance Schedule at https://docs.mcp-services.net/x/AQMu for the specific windows in each Geographic Region
Expected Total Duration: 45 minutes downtime

This minor API software upgrade includes enhancements that will mostly not be visible until the UI release in late August. However, there are two changes worth noting in the meantime:

ADVANCED VIRTUALIZATION SETTING ENFORCEMENT

The previous March release added support for tracking Advanced Virtualization Settings on Images. This release adds support for tracking Advanced Virtualization Settings on Cloud Servers.

There is one immediate change associated with the API release. The system will now prevent deployment of Cloud Servers from Images with specific Advanced Virtualization Settings. You can view the settings of an image on the Image Details screen as described in Navigating the Images and Applications Dashboard - https://docs.mcp-services.net/x/iwwu

Specifically, deployment of servers from Images with any of the following settings is prohibited in most data center locations:

Nested Hardware Virtualization = TRUE
CPU Latency Sensitivity = HIGH
Numa Autosize = TRUE
Enable Host Info to VM Tools = TRUE

The only exception to this prohibition is server deployment into specific hypervisor clusters designed for SAP HANA support. As of this release, these clusters exist only in specific Private Cloud locations. The August UI release will expose the setting enabling support in the Data Center capabilities screen. In the meantime, if you are using a Private Cloud location and are unsure of SAP HANA support, please open a support case.

Please note there is a very small number of Client Images with such settings. However, if a Customer Image has these settings, the system will prevent deployment until the Image has been modified to remove the relevant setting. Modification of such settings must be done via API until the August UI release.

For more details, see

Introduction to OS (Operating System) and Client Images
https://docs.mcp-services.net/x/UQSZ

How to Modify Advanced Virtualization Settings on a Client Image using REST API
https://docs.mcp-services.net/x/DwSy


API SUPPORT FOR RE-IP ADDRESSING AS PART OF DRS FOR CLOUD

This release provides API support for a new “re-ip address” feature in the DRS for Cloud offering. When DRS replicates Source Server disk content to the Target Server location, the guest OS settings for IP addresses of the NICs are inherited from the source. This behavior is often undesirable. The Re-IP address function allows users to impose specific IP address settings as part of the Preview function. Although the function is API-only until the UI release in August, it is relatively simple to apply in the current MCP 1.0 to MCP 2.0 migration use case.

For more details, see:

Introduction to DRS for Cloud - NIC IP Configuration after Preview of a Consistency Group
https://docs.mcp-services.net/x/qgE8#IntroductiontoDRSforCloud-NICIPConfigurationafterPreviewofaConsistencyGroup

How to Set Re-IP Address Rules for a Target Server in a DRS Server Pair
https://docs.mcp-services.net/x/9AOy

During the software upgrade, all Cloud Servers and Network assets you've deployed will be unaffected. However, the CloudControl API will be unavailable during the software upgrade for the duration listed above. The CloudControl UI will remain available but will be unable to process requests in the affected Geographic Regions during their windows.
Jul 3, 00:16 UTC
Completed - The scheduled maintenance has been completed.
Jul 9, 11:45 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 9, 11:00 UTC
Scheduled - We will be performing a minor software upgrade to the CloudControl API in all Geographic Regions on Tuesday July 9th during the normal software upgrade window in each region:

CloudControl Software Change Id: CCCHANGE-250
Time: See Software Upgrade Maintenance Schedule at https://docs.mcp-services.net/x/AQMu for the specific windows in each Geographic Region
Expected Total Duration: 45 minutes downtime

This minor API software upgrade includes enhancements that will mostly not be visible until the UI release in late August. However, there are two changes worth noting in the meantime:

ADVANCED VIRTUALIZATION SETTING ENFORCEMENT

The previous March release added support for tracking Advanced Virtualization Settings on Images. This release adds support for tracking Advanced Virtualization Settings on Cloud Servers.

There is one immediate change associated with the API release. The system will now prevent deployment of Cloud Servers from Images with specific Advanced Virtualization Settings. You can view the settings of an image on the Image Details screen as described in Navigating the Images and Applications Dashboard - https://docs.mcp-services.net/x/iwwu

Specifically, deployment of servers from Images with any of the following settings is prohibited in most data center locations:

Nested Hardware Virtualization = TRUE
CPU Latency Sensitivity = HIGH
Numa Autosize = TRUE
Enable Host Info to VM Tools = TRUE

The only exception to this prohibition is server deployment into specific hypervisor clusters designed for SAP HANA support. As of this release, these clusters exist only in specific Private Cloud locations. The August UI release will expose the setting enabling support in the Data Center capabilities screen. In the meantime, if you are using a Private Cloud location and are unsure of SAP HANA support, please open a support case.

Please note there is a very small number of Client Images with such settings. However, if a Customer Image has these settings, the system will prevent deployment until the Image has been modified to remove the relevant setting. Modification of such settings must be done via API until the August UI release.

For more details, see

Introduction to OS (Operating System) and Client Images
https://docs.mcp-services.net/x/UQSZ

How to Modify Advanced Virtualization Settings on a Client Image using REST API
https://docs.mcp-services.net/x/DwSy


API SUPPORT FOR RE-IP ADDRESSING AS PART OF DRS FOR CLOUD

This release provides API support for a new “re-ip address” feature in the DRS for Cloud offering. When DRS replicates Source Server disk content to the Target Server location, the guest OS settings for IP addresses of the NICs are inherited from the source. This behavior is often undesirable. The Re-IP address function allows users to impose specific IP address settings as part of the Preview function. Although the function is API-only until the UI release in August, it is relatively simple to apply in the current MCP 1.0 to MCP 2.0 migration use case.

For more details, see:

Introduction to DRS for Cloud - NIC IP Configuration after Preview of a Consistency Group
https://docs.mcp-services.net/x/qgE8#IntroductiontoDRSforCloud-NICIPConfigurationafterPreviewofaConsistencyGroup

How to Set Re-IP Address Rules for a Target Server in a DRS Server Pair
https://docs.mcp-services.net/x/9AOy

During the software upgrade, all Cloud Servers and Network assets you've deployed will be unaffected. However, the CloudControl API will be unavailable during the software upgrade for the duration listed above. The CloudControl UI will remain available but will be unable to process requests in the affected Geographic Regions during their windows.
Jul 3, 00:16 UTC
Completed - The scheduled maintenance has been completed.
Jul 9, 10:45 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 9, 10:00 UTC
Scheduled - We will be performing a minor software upgrade to the CloudControl API in all Geographic Regions on Tuesday July 9th during the normal software upgrade window in each region:

CloudControl Software Change Id: CCCHANGE-250
Time: See Software Upgrade Maintenance Schedule at https://docs.mcp-services.net/x/AQMu for the specific windows in each Geographic Region
Expected Total Duration: 45 minutes downtime

This minor API software upgrade includes enhancements that will mostly not be visible until the UI release in late August. However, there are two changes worth noting in the meantime:

ADVANCED VIRTUALIZATION SETTING ENFORCEMENT

The previous March release added support for tracking Advanced Virtualization Settings on Images. This release adds support for tracking Advanced Virtualization Settings on Cloud Servers.

There is one immediate change associated with the API release. The system will now prevent deployment of Cloud Servers from Images with specific Advanced Virtualization Settings. You can view the settings of an image on the Image Details screen as described in Navigating the Images and Applications Dashboard - https://docs.mcp-services.net/x/iwwu

Specifically, deployment of servers from Images with any of the following settings is prohibited in most data center locations:

Nested Hardware Virtualization = TRUE
CPU Latency Sensitivity = HIGH
Numa Autosize = TRUE
Enable Host Info to VM Tools = TRUE

The only exception to this prohibition is server deployment into specific hypervisor clusters designed for SAP HANA support. As of this release, these clusters exist only in specific Private Cloud locations. The August UI release will expose the setting enabling support in the Data Center capabilities screen. In the meantime, if you are using a Private Cloud location and are unsure of SAP HANA support, please open a support case.

Please note there is a very small number of Client Images with such settings. However, if a Customer Image has these settings, the system will prevent deployment until the Image has been modified to remove the relevant setting. Modification of such settings must be done via API until the August UI release.

For more details, see

Introduction to OS (Operating System) and Client Images
https://docs.mcp-services.net/x/UQSZ

How to Modify Advanced Virtualization Settings on a Client Image using REST API
https://docs.mcp-services.net/x/DwSy


API SUPPORT FOR RE-IP ADDRESSING AS PART OF DRS FOR CLOUD

This release provides API support for a new “re-ip address” feature in the DRS for Cloud offering. When DRS replicates Source Server disk content to the Target Server location, the guest OS settings for IP addresses of the NICs are inherited from the source. This behavior is often undesirable. The Re-IP address function allows users to impose specific IP address settings as part of the Preview function. Although the function is API-only until the UI release in August, it is relatively simple to apply in the current MCP 1.0 to MCP 2.0 migration use case.

For more details, see:

Introduction to DRS for Cloud - NIC IP Configuration after Preview of a Consistency Group
https://docs.mcp-services.net/x/qgE8#IntroductiontoDRSforCloud-NICIPConfigurationafterPreviewofaConsistencyGroup

How to Set Re-IP Address Rules for a Target Server in a DRS Server Pair
https://docs.mcp-services.net/x/9AOy

During the software upgrade, all Cloud Servers and Network assets you've deployed will be unaffected. However, the CloudControl API will be unavailable during the software upgrade for the duration listed above. The CloudControl UI will remain available but will be unable to process requests in the affected Geographic Regions during their windows.
Jul 3, 00:14 UTC
Completed - The scheduled maintenance has been completed.
Jul 9, 09:45 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 9, 09:00 UTC
Scheduled - We will be performing a minor software upgrade to the CloudControl API in all Geographic Regions on Tuesday July 9th during the normal software upgrade window in each region:

CloudControl Software Change Id: CCCHANGE-250
Time: See Software Upgrade Maintenance Schedule at https://docs.mcp-services.net/x/AQMu for the specific windows in each Geographic Region
Expected Total Duration: 45 minutes downtime

This minor API software upgrade includes enhancements that will mostly not be visible until the UI release in late August. However, there are two changes worth noting in the meantime:

ADVANCED VIRTUALIZATION SETTING ENFORCEMENT

The previous March release added support for tracking Advanced Virtualization Settings on Images. This release adds support for tracking Advanced Virtualization Settings on Cloud Servers.

There is one immediate change associated with the API release. The system will now prevent deployment of Cloud Servers from Images with specific Advanced Virtualization Settings. You can view the settings of an image on the Image Details screen as described in Navigating the Images and Applications Dashboard - https://docs.mcp-services.net/x/iwwu

Specifically, deployment of servers from Images with any of the following settings is prohibited in most data center locations:

Nested Hardware Virtualization = TRUE
CPU Latency Sensitivity = HIGH
Numa Autosize = TRUE
Enable Host Info to VM Tools = TRUE

The only exception to this prohibition is server deployment into specific hypervisor clusters designed for SAP HANA support. As of this release, these clusters exist only in specific Private Cloud locations. The August UI release will expose the setting enabling support in the Data Center capabilities screen. In the meantime, if you are using a Private Cloud location and are unsure of SAP HANA support, please open a support case.

Please note there is a very small number of Client Images with such settings. However, if a Customer Image has these settings, the system will prevent deployment until the Image has been modified to remove the relevant setting. Modification of such settings must be done via API until the August UI release.

For more details, see

Introduction to OS (Operating System) and Client Images
https://docs.mcp-services.net/x/UQSZ

How to Modify Advanced Virtualization Settings on a Client Image using REST API
https://docs.mcp-services.net/x/DwSy


API SUPPORT FOR RE-IP ADDRESSING AS PART OF DRS FOR CLOUD

This release provides API support for a new “re-ip address” feature in the DRS for Cloud offering. When DRS replicates Source Server disk content to the Target Server location, the guest OS settings for IP addresses of the NICs are inherited from the source. This behavior is often undesirable. The Re-IP address function allows users to impose specific IP address settings as part of the Preview function. Although the function is API-only until the UI release in August, it is relatively simple to apply in the current MCP 1.0 to MCP 2.0 migration use case.

For more details, see:

Introduction to DRS for Cloud - NIC IP Configuration after Preview of a Consistency Group
https://docs.mcp-services.net/x/qgE8#IntroductiontoDRSforCloud-NICIPConfigurationafterPreviewofaConsistencyGroup

How to Set Re-IP Address Rules for a Target Server in a DRS Server Pair
https://docs.mcp-services.net/x/9AOy

During the software upgrade, all Cloud Servers and Network assets you've deployed will be unaffected. However, the CloudControl API will be unavailable during the software upgrade for the duration listed above. The CloudControl UI will remain available but will be unable to process requests in the affected Geographic Regions during their windows.
Jul 3, 00:14 UTC