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: Clients will not have Console Access to Cloud Servers during maintenance window.

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

Change Reference Number: CHM121096606
Israel (IL1/IL2): Sunday May 26th 04:00 AM Israel Daylight Time (01: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 Apr 22, 17:54 UTC
The DRS for Cloud feature is being enabled sometime during Tuesday, May 28th to support migrations from the London MCP 1.0 (EU2) to the London MCP 2.0 (EU8) location.

CloudControl Change Id: OEC-11445
Time: During Tuesday May 28th 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 rate 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 May 22, 15:08 UTC
The DRS for Cloud feature is being enabled sometime during Tuesday, May 28th to support migrations from the Amsterdam MCP 1.0 (EU1) to the Amsterdam MCP 2.0 (EU7) location.

CloudControl Change Id: OEC-11444
Time: During Tuesday May 28th 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 rate 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 May 22, 15:03 UTC
The DRS for Cloud feature is being enabled sometime during Tuesday, May 28th to support migrations from the Johannesburg MCP 1.0 (AF1) to the Johannesburg MCP 2.0 (AF3) location.

CloudControl Change Id: OEC-11443
Time: During Tuesday May 28th 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 rate 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 May 22, 14:58 UTC
The DRS for Cloud feature is being enabled sometime during Tuesday, May 28th to support migrations from the New Zealand MCP 1.0 (AU8) to the New Zealand MCP 2.0 (AU11) location.

CloudControl Change Id: OEC-11442
Time: During Tuesday May 28th 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. Additional bi-directional replication for disaster recovery use cases between MCP 2.0 locations is expected to be released in July. There is an additional hourly rate 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 May 22, 14:49 UTC
The DRS for Cloud feature is being enabled sometime during Tuesday, May 28th to support migrations from the Melbourne MCP 1.0 (AU2) to the Melbourne MCP 2.0 (AU10) location.

CloudControl Change Id: OEC-11441
Time: During Tuesday May 28th 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. Additional bi-directional replication for disaster recovery use cases between MCP 2.0 locations is expected to be released in July. There is an additional hourly rate 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 May 22, 14:45 UTC
The DRS for Cloud feature is being enabled sometime during Tuesday, May 28th to support migrations from the Hong Kong MCP 1.0 (AP2) to the Hong Kong MCP 2.0 (AP5) location.

CloudControl Change Id: OEC-11440
Time: During Tuesday May 28th 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.

This initial rollout in the Asia-Pacific Geographic Region is being deployed to support users who wish to migrate their Cloud Servers from the Hong Kong MCP 1.0 location to the MCP 2.0 location. 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. Additional bi-directional replication for disaster recovery use cases between MCP 2.0 locations is expected to be released in July. There is an additional hourly rate 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 May 22, 14:38 UTC
The DRS for Cloud feature is being enabled sometime during Tuesday, May 28th to support migrations from the Tokyo MCP 1.0 (AP1) and Tokyo MCP 2.0 (AP4) locations to Singapore (AP3).

CloudControl Change Id: OEC-11437 through OEC-11439
Time: During Tuesday May 28th 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 rollouts of this feature in the Asia-Pacific Geographic Region is being deployed to support users who wish to migrate their Cloud Servers from the two Tokyo locations to the Singapore location. As such, the replication being enabled in this rollout is unidirectional: users can replicate only from the Tokyo location to the MCP 2.0 location. Additional bi-directional replication for disaster recovery use cases between MCP 2.0 locations is expected to be released in July. There is an additional hourly rate 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 May 22, 14:23 UTC
As part of our ongoing improvement initiatives, we will be kicking off our storage upgrade programme in NA9 (Ashburn) 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 NA9 (Ashburn) 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 May 29, 2019 starting at 17:00 UTC. The change is expected to take several hours to take effect across all existing Cloud Servers.

CloudControl Change Id: OEC-11398
Time 05:00 AM Eastern Daylight / 2:00 AM Pacific Daylight (9:00 UTC)
Expected Total Duration: Up to 12 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 May 3, 18:54 UTC
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 configuration. 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: CHM121278233
Melbourne (AU10): Friday May 31st 09:00 PM Australia Eastern Standard Time (11: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
Posted on May 9, 00:27 UTC
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 configuration. 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: CHM121278233
Melbourne (AU10): Friday May 31st 09:00 PM Australia Eastern Standard Time (11: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
Posted on May 7, 17:19 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: CHM121395609
Hong Kong (AP2/AP5): Friday May 31st 09:00 PM Japan Standard (12: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.
Posted on May 17, 00:34 UTC
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 Cloud Services. During this maintenance we will be upgrading storage 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 Client Cloud Servers. The Admin UI/API and Community will remain available.

Change Reference Number: CHM121200423
Johannesburg: (AF3,AF5): Friday May 31st 08:00 PM South Africa Standard Time (18:00 PM UTC)
Expected Total Duration: 12 Hours

Note this maintenance is specific only to the affected data center location and other Geographic Regions will continue to function normally.
Posted on May 21, 21:05 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: CHM121211657
Israel (IL1, IL2): Friday May 31st 09:00 PM Israel Daylight Time (18: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 May 7, 22:25 UTC
Impact: No impact to our clients is expected

Dear Client

On the date listed below engineers will be performing maintenance in the following locations. This maintenance is needed to perform repairs of network component supporting or cloud and manage hosting environment. During the maintenance engineers, will be performing replacement of problematic switch device. This device is currently secondary device no impact to client or services is expected.

Change Reference Number: CHM121403297
London (EU2,EU8,LHR03): Friday May 31st 09:00 PM Central European Standard (19:00 UTC)
Expected Total Duration: 3 Hour

Note this maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally.
Posted on May 23, 22:17 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: CHM121395966
US West: (NA3/NA12): Friday May 31st 09:00 PM US Pacific Daylight Time (1/6 04: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.
Posted on May 17, 00:33 UTC
We will be performing a major impact software upgrade to the CloudControl API in the North America Geographic Region on Tuesday June 4th local time (Wednesday June 5 UTC) during a non-standard software upgrade window due to the duration of the event:

CloudControl Software Change Id: CCOCHANGE-99
Date: Tuesday June 4, 2019 (Wednesday June 5 UTC)
Time: 9:00 PM US Eastern Daylight / 06:00 PM Pacific Daylight (Wednesday June 5 01:00 UTC)
Expected Total Duration: 10 hours

This major impact software upgrade involves migrating the CloudControl API and FTPS infrastructure supporting the North America (NA) Geographic Region from the NA1 (US-East MCP 1.0) infrastructure to the NA9 (US - East 3 - MCP 2.0) infrastructure.

The impacts of this change are as follows:

1) At the start of the maintenance window, the CloudControl API will be put into maintenance. All Cloud Servers and Networks you've deployed will be unaffected. However, the CloudControl API will be unavailable during the software upgrade for the duration listed above.

2) The CloudControl UI will remain available but will be unable to process requests in the North America Geographic Region during the window. Requests for other Geographic Regions will NOT be affected - only requests for the North America Geographic Region will be affected.

3) When the maintenance is over, the CloudControl API and FTPS servers will be answering on new IP addresses in the NA9 location. DNS records will be updated in conjunction with the change but if users have hard-coded the CloudControl API IP addresses, implemented firewall rules controlling access to the API address, or maintain their own DNS mappings that will not pick up the Public DNS change, they will need to update those IP references to support the new IP address after the migration. The specific IP changes that will be made are:

https://api-na.dimensiondata.com moving from 168.143.80.201 to 168.128.0.135
ftp://ftps-au.cloud-vpn.net/ moving from 168.143.80.234 to 168.128.0.130

4) In conjunction with the migration, the CloudControl API is ceasing support for a subset of legacy, insecure cipher suites. We are also deprecating other cipher suites for which we will cease support on September 4, 2019. For details, see the following article:

CloudControl API Encryption Standards and Migration Changes - https://docs.mcp-services.net/x/CAGZ

Please contact us if you have questions about this migration.
Posted on May 13, 18:08 UTC
SCHEDULED MAINTENANCE: MELBOURNE (AU10) 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: CHM121396350
Melbourne (AU10): Friday June 7th 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.
Posted on May 22, 12:14 UTC
SCHEDULED MAINTENANCE: LONDON (EU8) 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: CHM121396350
London (EU8): Friday June 7th 09:00 PM Central European Standard (19: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.
Posted on May 22, 12:17 UTC
Impact: No impact to clients expected.

Dear Client
On the dates listed below the Internet Service Provider for the following location will be performing emergency network maintenance. The ISP will be performing software upgrades to upstream routers supplying internet access to the below cloud locations. This circuit is currently our secondary link engineers do not expect any impact to our clients.

Change Reference Number: CHM121472262
London (EU2,EU8,LHR03): Sunday June 16th 07:00 AM Central European Standard Time (05:00 UTC)
Expected Total Duration: 12 Hours

Note this maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally.
Posted on May 23, 22:10 UTC
Past Incidents
May 25, 2019
Resolved - Issue has been resolved. Email services have been restored. If related issues persist, please contact the NOC for further assistance.
May 25, 19:36 UTC
Update - Our teams continue to work towards service restoration. Updates will be provided once available.
May 25, 19:21 UTC
Update - Our teams are currently engaged and will provide updates as they become available.
May 25, 18:55 UTC
Update - Our teams continue to work towards service restoration. Updates will be provided once available.
May 25, 18:27 UTC
Update - Our teams are currently engaged and will provide updates as they become available.
May 25, 17:58 UTC
Investigating - All CIS Users are not able to access outlook or e-mail services. Our teams are currently engaged, and will provide updates in short time.
May 25, 17:10 UTC
Completed - The scheduled maintenance has been completed.
May 25, 02:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 24, 18: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 Cloud Services. During this maintenance we will be upgrading storage 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 Client Cloud Servers. The Admin UI/API and Community will remain available.

Change Reference Number: CHM121373168
Johannesburg: (AF4): Friday May 24th 08:00 PM South Africa Standard Time (18:00 PM UTC)
Expected Total Duration: 8 Hours

Note this maintenance is specific only to the affected data center location and other Geographic Regions will continue to function normally.
May 15, 16:41 UTC
May 24, 2019
Completed - The scheduled maintenance has been completed.
May 24, 20:00 UTC
Update - Urgent Update: Due to unexpected issues primary core router is not coming online after vendor maintenance. Engineers will be doing a reload of the primary core router at 5:20 AM AEST to correct issue. During reload IPSEC CPNC Clients without the HA option will see their VPN tunnels go down for duration of reload up to 10 minutes. All other client traffic should not be impacted. Apologies for any inconvenience this may cause.
May 24, 18:57 UTC
Update - Due to unexpected issues this change is being extend by 2 hours. No change in risk or impact is expected.
May 24, 17:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 24, 11:00 UTC
Scheduled - Impact: No impact to clients expected. There is a medium risk of brief periods of network latency.

Dear Client

On the date listed below the Internet Service Provider for the following location will be performing emergency network maintenance. The ISP will be performing upstream cable. Engineers will be failing traffic over to a redundant connection, prior to the maintenance. This type of maintenance has been performed in the past without impact to traffic, however there is a medium risk of brief latency and or packet loss during the maintenance window.

Change Reference Number: CHM121471078
Sydney (AU1,AU6,AU9,SYD01): Friday May 24th 09:00 PM Australia Eastern Standard Time (11:00 UTC)
Expected Total Duration: 7 Hours

Note this maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally.
May 23, 22:33 UTC
Completed - The scheduled maintenance has been completed.
May 24, 19:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 24, 11:00 UTC
Scheduled - SCHEDULED MAINTENANCE: SYDNEY (AU1,AU6,AU9) INFRASTRUCTURE MAINTENANCE

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 Cloud Services. During this maintenance, we will be upgrading storage devices to the latest vendor approved and tested OS release. Although this type of maintenance has been performed in the past without impact, there is a low risk of latency and service disruption to Client Cloud Servers.


Change Reference Number: CHM121209939
Sydney (AU1,AU6,AU9): Friday May 24th 09:00 PM Australia Eastern Standard Time (11:00 UTC)
Expected Total Duration: 8 Hours

Note this maintenance is specific only to the affected data center location and other Geographic Regions will continue to function normally.
May 22, 12:11 UTC
Completed - The scheduled maintenance has been completed.
May 24, 15:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 24, 11: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 configuration. 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: CHM121276767
Sydney (AU9): Friday May 24th 09:00 PM Australia Eastern Standard Time (11: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 7, 17:12 UTC
May 23, 2019
Completed - The scheduled maintenance has been completed.
May 23, 20:46 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 23, 20:00 UTC
Scheduled - We will be performing a minor software upgrade to the CloudControl API in all Geographic Regions on Thursday May 23rd during the normal software upgrade window in each region:

CloudControl Software Change Id: CCCHANGE-246
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

This minor software upgrade includes improvements related to the DRS for Cloud feature that will be made widely available for MCP 1.0 to 2.0 migrations in a separate announcement.

During the software upgrade, all Cloud Servers and Networks 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.
May 17, 19:05 UTC
Completed - The scheduled maintenance has been completed.
May 23, 19:45 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 23, 19:00 UTC
Scheduled - We will be performing a minor software upgrade to the CloudControl API in all Geographic Regions on Thursday May 23rd during the normal software upgrade window in each region:

CloudControl Software Change Id: CCCHANGE-246
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

This minor software upgrade includes improvements related to the DRS for Cloud feature that will be made widely available for MCP 1.0 to 2.0 migrations in a separate announcement.

During the software upgrade, all Cloud Servers and Networks 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.
May 17, 19:05 UTC
Completed - The scheduled maintenance has been completed.
May 23, 18:45 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 23, 18:01 UTC
Scheduled - We will be performing a minor software upgrade to the CloudControl API in all Geographic Regions on Thursday May 23rd during the normal software upgrade window in each region:

CloudControl Software Change Id: CCCHANGE-246
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

This minor software upgrade includes improvements related to the DRS for Cloud feature that will be made widely available for MCP 1.0 to 2.0 migrations in a separate announcement.

During the software upgrade, all Cloud Servers and Networks 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.
May 17, 19:04 UTC
Completed - The scheduled maintenance has been completed.
May 23, 12:45 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 23, 12:00 UTC
Scheduled - We will be performing a minor software upgrade to the CloudControl API in all Geographic Regions on Thursday May 23rd during the normal software upgrade window in each region:

CloudControl Software Change Id: CCCHANGE-246
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

This minor software upgrade includes improvements related to the DRS for Cloud feature that will be made widely available for MCP 1.0 to 2.0 migrations in a separate announcement.

During the software upgrade, all Cloud Servers and Networks 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.
May 17, 19:03 UTC
Completed - The scheduled maintenance has been completed.
May 23, 11:45 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 23, 11:00 UTC
Scheduled - We will be performing a minor software upgrade to the CloudControl API in all Geographic Regions on Thursday May 23rd during the normal software upgrade window in each region:

CloudControl Software Change Id: CCCHANGE-246
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

This minor software upgrade includes improvements related to the DRS for Cloud feature that will be made widely available for MCP 1.0 to 2.0 migrations in a separate announcement.

During the software upgrade, all Cloud Servers and Networks 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.
May 17, 19:02 UTC
Completed - The scheduled maintenance has been completed.
May 23, 10:45 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 23, 10:00 UTC
Scheduled - We will be performing a minor software upgrade to the CloudControl API in all Geographic Regions on Thursday May 23rd during the normal software upgrade window in each region:

CloudControl Software Change Id: CCCHANGE-246
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

This minor software upgrade includes improvements related to the DRS for Cloud feature that will be made widely available for MCP 1.0 to 2.0 migrations in a separate announcement.

During the software upgrade, all Cloud Servers and Networks 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.
May 17, 19:01 UTC
Completed - The scheduled maintenance has been completed.
May 23, 09:45 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 23, 09:00 UTC
Scheduled - We will be performing a minor software upgrade to the CloudControl API in all Geographic Regions on Thursday May 23rd during the normal software upgrade window in each region:

CloudControl Software Change Id: CCCHANGE-246
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

This minor software upgrade includes improvements related to the DRS for Cloud feature that will be made widely available for MCP 1.0 to 2.0 migrations in a separate announcement.

During the software upgrade, all Cloud Servers and Networks 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.
May 17, 19:01 UTC
May 22, 2019
Completed - The scheduled maintenance has been completed.
May 22, 16:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 22, 12:00 UTC
Scheduled - Impact: No impact to our clients is expected

Dear Client

On the date listed below engineers will be performing maintenance in the following locations. This maintenance is needed to perform replacement of network component supporting cloud servers. During the maintenance engineers, will be performing vendor recommended replacement of failed network device. This device is currently secondary device no impact to client is expected.

Change Reference Number: CHM121357689
Tokyo (AP1,AP4): Wednesday May 22nd 09:00 PM Japan Standard (12:00 UTC)
Expected Total Duration: 4 Hour

Note this maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally.
May 20, 20:38 UTC
May 21, 2019
Completed - The scheduled maintenance has been completed.
May 21, 22:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 21, 21:00 UTC
Scheduled - We will be performing a minor software upgrade to the CloudControl UI in all Geographic Regions on Tuesday May 21st during the normal software upgrade window in each region:

CloudControl Software Change Id: CCCHANGE-245
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: 10 minutes during a 60 minute window

This minor software upgrade includes the following enhancements:

FIREWALL STATISTICS INCLUDING OVERLAP STATE AND HIT COUNTER

Users can now view near-real time statistics and information about usage of their firewalls in the UI. For details, see:

Introduction to Firewall Rules for Cloud Network Domains in MCP 2.0 - https://docs.mcp-services.net/x/OQIu
How to View and Manage Firewall Rules and Statistics on a Network Domain - https://docs.mcp-services.net/x/vwMk


VISIBILITY OF “RESTART REQUIRED” SERVERS

When making disk changes on a running server involving Burstable disk speeds or the Provisioned IOPS disk speed, a failure to successfully implement the associated Throughput change may require a restart of the server. The need to take this action is now visible in the UI. For details, see:

Introduction to Cloud Server Local Storage ("Disks") and Disk Speeds - https://docs.mcp-services.net/x/UwIu#IntroductiontoCloudServerLocalStorage("Disks")andDiskSpeeds-AddingandModifyingDisks
How to Add Additional Local Storage (Disk) to a Cloud Server - https://docs.mcp-services.net/x/hwMk
How to Manage a Local Storage Disk on a Cloud Server - https://docs.mcp-services.net/x/mgMk


VISIBILITY OF ADVANCED VIRTUALIZATION SETTINGS ON IMAGES

The system will now display any Advanced Virtualization Settings present on both OS and Customer Images. This functionality has limited applicability outside SAP environments but will be further enhanced in the next release. For details, see:

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


SECURITY GROUPS USAGE REPORT

A detailed report identifying how Security Groups Hours usage was calculated for a given period is now available. For details, see:

How to Create a Security Group Usage Report - https://docs.mcp-services.net/x/ywGy


COMING SOON: DRS FOR CLOUD

This release includes changes to the DRS for Cloud functionality designed to support availability as a “stand alone” feature that can be used both for real-time replication for DR purposes and for migrations between MCP 1.0 and 2.0 locations. The initial availability will focus on MCP 1.0 to 2.0 migrations and is expected in the coming weeks. Rollouts between MCP 2.0 locations will follow during the summer. More details and links to the documentation will be available with the availability announcement.


During the software upgrade, all Cloud Servers and Networks you've deployed will be unaffected. However, the CloudControl UI will be unavailable during the software upgrade for the duration listed above. The API will remain available and is able to process requests in the affected Geographic Regions during their windows.
May 15, 20:28 UTC
Completed - The scheduled maintenance has been completed.
May 21, 20:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 21, 19:00 UTC
Scheduled - We will be performing a minor software upgrade to the CloudControl UI in all Geographic Regions on Tuesday May 21st during the normal software upgrade window in each region:

CloudControl Software Change Id: CCCHANGE-245
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: 10 minutes during a 60 minute window

This minor software upgrade includes the following enhancements:

FIREWALL STATISTICS INCLUDING OVERLAP STATE AND HIT COUNTER

Users can now view near-real time statistics and information about usage of their firewalls in the UI. For details, see:

Introduction to Firewall Rules for Cloud Network Domains in MCP 2.0 - https://docs.mcp-services.net/x/OQIu
How to View and Manage Firewall Rules and Statistics on a Network Domain - https://docs.mcp-services.net/x/vwMk


VISIBILITY OF “RESTART REQUIRED” SERVERS

When making disk changes on a running server involving Burstable disk speeds or the Provisioned IOPS disk speed, a failure to successfully implement the associated Throughput change may require a restart of the server. The need to take this action is now visible in the UI. For details, see:

Introduction to Cloud Server Local Storage ("Disks") and Disk Speeds - https://docs.mcp-services.net/x/UwIu#IntroductiontoCloudServerLocalStorage("Disks")andDiskSpeeds-AddingandModifyingDisks
How to Add Additional Local Storage (Disk) to a Cloud Server - https://docs.mcp-services.net/x/hwMk
How to Manage a Local Storage Disk on a Cloud Server - https://docs.mcp-services.net/x/mgMk


VISIBILITY OF ADVANCED VIRTUALIZATION SETTINGS ON IMAGES

The system will now display any Advanced Virtualization Settings present on both OS and Customer Images. This functionality has limited applicability outside SAP environments but will be further enhanced in the next release. For details, see:

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


SECURITY GROUPS USAGE REPORT

A detailed report identifying how Security Groups Hours usage was calculated for a given period is now available. For details, see:

How to Create a Security Group Usage Report - https://docs.mcp-services.net/x/ywGy


COMING SOON: DRS FOR CLOUD

This release includes changes to the DRS for Cloud functionality designed to support availability as a “stand alone” feature that can be used both for real-time replication for DR purposes and for migrations between MCP 1.0 and 2.0 locations. The initial availability will focus on MCP 1.0 to 2.0 migrations and is expected in the coming weeks. Rollouts between MCP 2.0 locations will follow during the summer. More details and links to the documentation will be available with the availability announcement.


During the software upgrade, all Cloud Servers and Networks you've deployed will be unaffected. However, the CloudControl UI will be unavailable during the software upgrade for the duration listed above. The API will remain available and is able to process requests in the affected Geographic Regions during their windows.
May 15, 20:27 UTC
Completed - The scheduled maintenance has been completed.
May 21, 19:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 21, 18:00 UTC
Scheduled - We will be performing a minor software upgrade to the CloudControl UI in all Geographic Regions on Tuesday May 21st during the normal software upgrade window in each region:

CloudControl Software Change Id: CCCHANGE-245
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: 10 minutes during a 60 minute window

This minor software upgrade includes the following enhancements:

FIREWALL STATISTICS INCLUDING OVERLAP STATE AND HIT COUNTER

Users can now view near-real time statistics and information about usage of their firewalls in the UI. For details, see:

Introduction to Firewall Rules for Cloud Network Domains in MCP 2.0 - https://docs.mcp-services.net/x/OQIu
How to View and Manage Firewall Rules and Statistics on a Network Domain - https://docs.mcp-services.net/x/vwMk


VISIBILITY OF “RESTART REQUIRED” SERVERS

When making disk changes on a running server involving Burstable disk speeds or the Provisioned IOPS disk speed, a failure to successfully implement the associated Throughput change may require a restart of the server. The need to take this action is now visible in the UI. For details, see:

Introduction to Cloud Server Local Storage ("Disks") and Disk Speeds - https://docs.mcp-services.net/x/UwIu#IntroductiontoCloudServerLocalStorage("Disks")andDiskSpeeds-AddingandModifyingDisks
How to Add Additional Local Storage (Disk) to a Cloud Server - https://docs.mcp-services.net/x/hwMk
How to Manage a Local Storage Disk on a Cloud Server - https://docs.mcp-services.net/x/mgMk


VISIBILITY OF ADVANCED VIRTUALIZATION SETTINGS ON IMAGES

The system will now display any Advanced Virtualization Settings present on both OS and Customer Images. This functionality has limited applicability outside SAP environments but will be further enhanced in the next release. For details, see:

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


SECURITY GROUPS USAGE REPORT

A detailed report identifying how Security Groups Hours usage was calculated for a given period is now available. For details, see:

How to Create a Security Group Usage Report - https://docs.mcp-services.net/x/ywGy


COMING SOON: DRS FOR CLOUD

This release includes changes to the DRS for Cloud functionality designed to support availability as a “stand alone” feature that can be used both for real-time replication for DR purposes and for migrations between MCP 1.0 and 2.0 locations. The initial availability will focus on MCP 1.0 to 2.0 migrations and is expected in the coming weeks. Rollouts between MCP 2.0 locations will follow during the summer. More details and links to the documentation will be available with the availability announcement.


During the software upgrade, all Cloud Servers and Networks you've deployed will be unaffected. However, the CloudControl UI will be unavailable during the software upgrade for the duration listed above. The API will remain available and is able to process requests in the affected Geographic Regions during their windows.
May 15, 20:26 UTC
Completed - The scheduled maintenance has been completed.
May 21, 13:01 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 21, 12:00 UTC
Scheduled - We will be performing a minor software upgrade to the CloudControl UI in all Geographic Regions on Tuesday May 21st during the normal software upgrade window in each region:

CloudControl Software Change Id: CCCHANGE-245
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: 10 minutes during a 60 minute window

This minor software upgrade includes the following enhancements:

FIREWALL STATISTICS INCLUDING OVERLAP STATE AND HIT COUNTER

Users can now view near-real time statistics and information about usage of their firewalls in the UI. For details, see:

Introduction to Firewall Rules for Cloud Network Domains in MCP 2.0 - https://docs.mcp-services.net/x/OQIu
How to View and Manage Firewall Rules and Statistics on a Network Domain - https://docs.mcp-services.net/x/vwMk


VISIBILITY OF “RESTART REQUIRED” SERVERS

When making disk changes on a running server involving Burstable disk speeds or the Provisioned IOPS disk speed, a failure to successfully implement the associated Throughput change may require a restart of the server. The need to take this action is now visible in the UI. For details, see:

Introduction to Cloud Server Local Storage ("Disks") and Disk Speeds - https://docs.mcp-services.net/x/UwIu#IntroductiontoCloudServerLocalStorage("Disks")andDiskSpeeds-AddingandModifyingDisks
How to Add Additional Local Storage (Disk) to a Cloud Server - https://docs.mcp-services.net/x/hwMk
How to Manage a Local Storage Disk on a Cloud Server - https://docs.mcp-services.net/x/mgMk


VISIBILITY OF ADVANCED VIRTUALIZATION SETTINGS ON IMAGES

The system will now display any Advanced Virtualization Settings present on both OS and Customer Images. This functionality has limited applicability outside SAP environments but will be further enhanced in the next release. For details, see:

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


SECURITY GROUPS USAGE REPORT

A detailed report identifying how Security Groups Hours usage was calculated for a given period is now available. For details, see:

How to Create a Security Group Usage Report - https://docs.mcp-services.net/x/ywGy


COMING SOON: DRS FOR CLOUD

This release includes changes to the DRS for Cloud functionality designed to support availability as a “stand alone” feature that can be used both for real-time replication for DR purposes and for migrations between MCP 1.0 and 2.0 locations. The initial availability will focus on MCP 1.0 to 2.0 migrations and is expected in the coming weeks. Rollouts between MCP 2.0 locations will follow during the summer. More details and links to the documentation will be available with the availability announcement.


During the software upgrade, all Cloud Servers and Networks you've deployed will be unaffected. However, the CloudControl UI will be unavailable during the software upgrade for the duration listed above. The API will remain available and is able to process requests in the affected Geographic Regions during their windows.
May 15, 20:26 UTC
Completed - The scheduled maintenance has been completed.
May 21, 12:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 21, 11:00 UTC
Scheduled - We will be performing a minor software upgrade to the CloudControl UI in all Geographic Regions on Tuesday May 21st during the normal software upgrade window in each region:

CloudControl Software Change Id: CCCHANGE-245
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: 10 minutes during a 60 minute window

This minor software upgrade includes the following enhancements:

FIREWALL STATISTICS INCLUDING OVERLAP STATE AND HIT COUNTER

Users can now view near-real time statistics and information about usage of their firewalls in the UI. For details, see:

Introduction to Firewall Rules for Cloud Network Domains in MCP 2.0 - https://docs.mcp-services.net/x/OQIu
How to View and Manage Firewall Rules and Statistics on a Network Domain - https://docs.mcp-services.net/x/vwMk


VISIBILITY OF “RESTART REQUIRED” SERVERS

When making disk changes on a running server involving Burstable disk speeds or the Provisioned IOPS disk speed, a failure to successfully implement the associated Throughput change may require a restart of the server. The need to take this action is now visible in the UI. For details, see:

Introduction to Cloud Server Local Storage ("Disks") and Disk Speeds - https://docs.mcp-services.net/x/UwIu#IntroductiontoCloudServerLocalStorage("Disks")andDiskSpeeds-AddingandModifyingDisks
How to Add Additional Local Storage (Disk) to a Cloud Server - https://docs.mcp-services.net/x/hwMk
How to Manage a Local Storage Disk on a Cloud Server - https://docs.mcp-services.net/x/mgMk


VISIBILITY OF ADVANCED VIRTUALIZATION SETTINGS ON IMAGES

The system will now display any Advanced Virtualization Settings present on both OS and Customer Images. This functionality has limited applicability outside SAP environments but will be further enhanced in the next release. For details, see:

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


SECURITY GROUPS USAGE REPORT

A detailed report identifying how Security Groups Hours usage was calculated for a given period is now available. For details, see:

How to Create a Security Group Usage Report - https://docs.mcp-services.net/x/ywGy


COMING SOON: DRS FOR CLOUD

This release includes changes to the DRS for Cloud functionality designed to support availability as a “stand alone” feature that can be used both for real-time replication for DR purposes and for migrations between MCP 1.0 and 2.0 locations. The initial availability will focus on MCP 1.0 to 2.0 migrations and is expected in the coming weeks. Rollouts between MCP 2.0 locations will follow during the summer. More details and links to the documentation will be available with the availability announcement.


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

CloudControl Software Change Id: CCCHANGE-245
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: 10 minutes during a 60 minute window

This minor software upgrade includes the following enhancements:

FIREWALL STATISTICS INCLUDING OVERLAP STATE AND HIT COUNTER

Users can now view near-real time statistics and information about usage of their firewalls in the UI. For details, see:

Introduction to Firewall Rules for Cloud Network Domains in MCP 2.0 - https://docs.mcp-services.net/x/OQIu
How to View and Manage Firewall Rules and Statistics on a Network Domain - https://docs.mcp-services.net/x/vwMk


VISIBILITY OF “RESTART REQUIRED” SERVERS

When making disk changes on a running server involving Burstable disk speeds or the Provisioned IOPS disk speed, a failure to successfully implement the associated Throughput change may require a restart of the server. The need to take this action is now visible in the UI. For details, see:

Introduction to Cloud Server Local Storage ("Disks") and Disk Speeds - https://docs.mcp-services.net/x/UwIu#IntroductiontoCloudServerLocalStorage("Disks")andDiskSpeeds-AddingandModifyingDisks
How to Add Additional Local Storage (Disk) to a Cloud Server - https://docs.mcp-services.net/x/hwMk
How to Manage a Local Storage Disk on a Cloud Server - https://docs.mcp-services.net/x/mgMk


VISIBILITY OF ADVANCED VIRTUALIZATION SETTINGS ON IMAGES

The system will now display any Advanced Virtualization Settings present on both OS and Customer Images. This functionality has limited applicability outside SAP environments but will be further enhanced in the next release. For details, see:

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


SECURITY GROUPS USAGE REPORT

A detailed report identifying how Security Groups Hours usage was calculated for a given period is now available. For details, see:

How to Create a Security Group Usage Report - https://docs.mcp-services.net/x/ywGy


COMING SOON: DRS FOR CLOUD

This release includes changes to the DRS for Cloud functionality designed to support availability as a “stand alone” feature that can be used both for real-time replication for DR purposes and for migrations between MCP 1.0 and 2.0 locations. The initial availability will focus on MCP 1.0 to 2.0 migrations and is expected in the coming weeks. Rollouts between MCP 2.0 locations will follow during the summer. More details and links to the documentation will be available with the availability announcement.


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

CloudControl Software Change Id: CCCHANGE-245
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: 10 minutes during a 60 minute window

This minor software upgrade includes the following enhancements:

FIREWALL STATISTICS INCLUDING OVERLAP STATE AND HIT COUNTER

Users can now view near-real time statistics and information about usage of their firewalls in the UI. For details, see:

Introduction to Firewall Rules for Cloud Network Domains in MCP 2.0 - https://docs.mcp-services.net/x/OQIu
How to View and Manage Firewall Rules and Statistics on a Network Domain - https://docs.mcp-services.net/x/vwMk


VISIBILITY OF “RESTART REQUIRED” SERVERS

When making disk changes on a running server involving Burstable disk speeds or the Provisioned IOPS disk speed, a failure to successfully implement the associated Throughput change may require a restart of the server. The need to take this action is now visible in the UI. For details, see:

Introduction to Cloud Server Local Storage ("Disks") and Disk Speeds - https://docs.mcp-services.net/x/UwIu#IntroductiontoCloudServerLocalStorage("Disks")andDiskSpeeds-AddingandModifyingDisks
How to Add Additional Local Storage (Disk) to a Cloud Server - https://docs.mcp-services.net/x/hwMk
How to Manage a Local Storage Disk on a Cloud Server - https://docs.mcp-services.net/x/mgMk


VISIBILITY OF ADVANCED VIRTUALIZATION SETTINGS ON IMAGES

The system will now display any Advanced Virtualization Settings present on both OS and Customer Images. This functionality has limited applicability outside SAP environments but will be further enhanced in the next release. For details, see:

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


SECURITY GROUPS USAGE REPORT

A detailed report identifying how Security Groups Hours usage was calculated for a given period is now available. For details, see:

How to Create a Security Group Usage Report - https://docs.mcp-services.net/x/ywGy


COMING SOON: DRS FOR CLOUD

This release includes changes to the DRS for Cloud functionality designed to support availability as a “stand alone” feature that can be used both for real-time replication for DR purposes and for migrations between MCP 1.0 and 2.0 locations. The initial availability will focus on MCP 1.0 to 2.0 migrations and is expected in the coming weeks. Rollouts between MCP 2.0 locations will follow during the summer. More details and links to the documentation will be available with the availability announcement.


During the software upgrade, all Cloud Servers and Networks you've deployed will be unaffected. However, the CloudControl UI will be unavailable during the software upgrade for the duration listed above. The API will remain available and is able to process requests in the affected Geographic Regions during their windows.
May 15, 20:23 UTC
May 20, 2019
Completed - The scheduled maintenance has been completed.
May 20, 21:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 20, 09:00 UTC
Scheduled - The ability to replicate Cloud Snapshots between EU6 (Frankfurt - MCP2) and EU7 (Amsterdam - MCP2) will be made available on Monday, May 20

CloudControl Change Id: OEC-11418
Time: During Monday May 20th 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.
May 17, 13:57 UTC
Resolved - The change has been successfully completed. Closing status page.
May 20, 20:49 UTC
Investigating - Impact: The UI/API will be in Hypervisor Maintenance Mode for duration of maintenance see note below for restrictions. No impact to deployed client cloud servers.

Dear Client

Engineers have identified an issue in the US EAST NA9 Cloud Location. In order to correct issue engineers will need to perform reload of devices supporting the Hypervisor Infrastructure. There will be no impact to deployed client cloud servers during this maintenance however the Cloud UI/API will be in Hypervisor Maintenance Mode for duration of maintenance. See note below for client restrictions.

Change Reference Number: CHM121451514
US EAST (NA9): IMMEDIATELY
Expected Total Duration: 2 Hour

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 20, 18:50 UTC
May 19, 2019

No incidents reported.

May 18, 2019
Completed - The scheduled maintenance has been completed.
May 18, 10:01 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 18, 02: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: CHM121325363
Canada: (CA1, CA2): Friday May 17th 09:00 PM Eastern Standard Time (18/5 02: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.
May 7, 22:26 UTC
May 17, 2019
Completed - The scheduled maintenance has been completed.
May 17, 22:01 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 17, 18:00 UTC
Scheduled - Impact: No impact to our clients is expected

Dear Client

On the date listed below engineers will be performing maintenance in the following locations. This maintenance is needed to perform repairs of network component supporting managed hosting environment. During the maintenance engineers, will be performing cable and port testing. This device is currently secondary device no impact to client is expected.

Change Reference Number: CHM121403297
Johannesburg: (JNB01): Friday May 17th 08:00 PM South Africa Standard Time (18:00 PM UTC)
Expected Total Duration: 4 Hour

Note this maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally.
May 16, 22:32 UTC
Completed - The scheduled maintenance has been completed.
May 17, 22:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 17, 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 configuration. 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: CHM121185368
Israel (IL2): Friday May 17th 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 7, 17:09 UTC
Completed - The scheduled maintenance has been completed.
May 17, 21:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 17, 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 configuration. 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: CHM121324778
Johannesburg: (AF4): Friday May 17th 08:00 PM South Africa Standard Time (18:00 PM UTC)
Expected Total Duration: 3 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 9, 00:19 UTC
Completed - The scheduled maintenance has been completed.
May 17, 19:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 17, 11: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 Cloud Services. During this maintenance we will be upgrading storage devices to the latest vendor approved and tested OS release. Although this type of maintenance has been performed in the past without impact, there is a low risk of latency and service disruption to Client Cloud Servers.


Change Reference Number: CHM121209939
Sydney (AU1,AU6,AU9): Friday May 17th 09:00 PM Australia Eastern Standard Time (11:00 UTC)
Expected Total Duration: 8 Hours

Note this maintenance is specific only to the affected data center location and other Geographic Regions will continue to function normally.
May 11, 00:39 UTC
Completed - The scheduled maintenance has been completed.
May 17, 15:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 17, 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 configuration. 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: CHM121332658
Singapore (AP9): Friday May 17th 09:00 PM Japan Standard (12:00 UTC)
Expected Total Duration: 3 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 7, 20:53 UTC
May 16, 2019
Resolved - System restoration is complete. Clients confirmed operational functionality.
May 16, 21:25 UTC
Update - We continue to work work on this instance. Further updates will be provided in short time.
May 16, 19:07 UTC
Update - Our teams continue engagement and will provide updates once available.
May 16, 18:39 UTC
Update - We continue to work work on this instance. Further updates will be provided in short time.
May 16, 18:01 UTC
Update - Our teams are still working toward service restoration. Updates will be provided once available.
May 16, 17:38 UTC
Update - Our teams continue engagement and will provide updates once available.
May 16, 17:14 UTC
Update - Engineers are currently engaged and are in the process of installing the device. Further updates will be made once available.
May 16, 16:45 UTC
Update - RMA has arrived on site Engineers are working under Emergency Change CHM121414460 to install the device
May 16, 15:31 UTC
Update - We are continuing to investigate this issue.
May 16, 15:24 UTC
Update - We are continuing to investigate this issue.
May 16, 15:23 UTC
Update - RMA Has been initiated. Will publish additional updates once available.
May 15, 19:00 UTC
Update - We continue to work work on this instance. Further updates will be provided in short time.
May 15, 18:53 UTC
Update - Our teams continue engagement and will provide updates once available.
May 15, 18:31 UTC
Update - We are continuing to investigate this issue.
May 15, 18:09 UTC
Investigating - We are currently experiencing issues in the AU region and are currently working with appropriate teams to resolve this issue. You may experience a degradation in service or service unavailability due to this unexpected event. We are taking every possible action to resolve this situation in a timely manner.
May 15, 17:51 UTC
Completed - The scheduled maintenance has been completed.
May 16, 01:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 15, 17:00 UTC
Scheduled - As part of our ongoing improvement initiatives, we will be kicking off our storage upgrade programme in EU6 (Frankfurt)) 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 EU6 (Frankfurt) 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 outside the normal software upgrade window on May 15, 2019 starting at 17:00 UTC. The change is expected to take several hours to take effect across all existing Cloud Servers.

CloudControl Change Id: OEC-11397
Time: 07:00 AM Central European Summer Time (17:00 UTC)
Expected Total Duration: Up to 8 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
May 3, 18:43 UTC
May 15, 2019
Completed - The scheduled maintenance has been completed.
May 15, 06:31 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 14, 18:30 UTC
Scheduled - The ability to to use the Security Groups feature has been made available for use in the Public Singapore (AP3) location, effective immediately.

CloudControl Change Id: OEC-11406
Time: Available Now
Expected Total Duration: N/A

This new feature allows the user to deploy Security Groups to isolate servers residing on the same VLAN. The feature is available to all users of AP3. There is an additional hourly rate for use of the feature. For details, see:

Introduction to Security Groups - https://docs.mcp-services.net/x/NgMu
Identify Hardware Specifications and Capabilities Available in a Data Center Location - https://docs.mcp-services.net/x/nAAu
How to View and Manage VLAN Security Groups on a Network Domain - https://docs.mcp-services.net/x/OAMu
How to Add or Remove a Cloud Server NIC to / from a VLAN Security Group - https://docs.mcp-services.net/x/pAMu
How to Delete a VLAN Security Group - https://docs.mcp-services.net/x/qAMu
How to View, Create, and Manage Server Security Groups on a Network Domain - https://docs.mcp-services.net/x/AwdH
How to Add or Remove a Cloud Server to / from a Server Security Group - https://docs.mcp-services.net/x/HQdH
How to Delete a Server Security Group - https://docs.mcp-services.net/x/IgdH
Introduction to Usage Reporting - https://docs.mcp-services.net/x/7IBs

There is no CloudControl UI or API downtime nor any impact to any existing Cloud Servers and Networks due to this change. This notification is for informational purposes
May 14, 18:28 UTC
May 14, 2019
Completed - The scheduled maintenance has been completed.
May 14, 21:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 14, 18:00 UTC
Scheduled - Impact: No impact to clients expected.

Dear Client

On the dates listed below the Internet Service Provider for the following location will be performing emergency network maintenance. The ISP will be performing software upgrades to upstream routers supplying internet access to the below cloud locations. This circuit is currently our secondary link engineers do not expect any impact to our clients.

Change Reference Number: CHM121344677
Singapore (AP10, SIN04): Wednesday May 15 03:00 AM Japan Standard (14/5 18: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
May 9, 23:20 UTC
Resolved - This issue has been resolved...
May 14, 18:27 UTC
Update - We are continuing to investigate this issue.
May 14, 17:24 UTC
Investigating - We are currently experiencing intermittent issue with replication for Snapshots and are currently working with the vendor to resolve this issue. You may experience issue when trying to replicate a snapshot to another location due to this unexpected event. We are taking every possible action to resolve this situation in a timely manner. DMVPN Tunnel81 impacting SNAPSHOT Replication intermittently.

We sincerely appreciate your patience.
May 14, 17:08 UTC
Completed - The scheduled maintenance has been completed.
May 14, 16:01 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 14, 15:00 UTC
Scheduled - Impact: No impact to clients expected.

Dear Client

The Managed Cloud Platform provides RedHat repository content to customer VMs via the RedHat Update Infrastructure (RHUI). The current version of this product has been discontinued by RedHat and a new version has been put in place.

The new version of RHUI will be activated on May 14. After this date, customers can perform a simple "yum update" command to reconfigure their servers to use the new RHUI infrastructure. NOTE: the update will be installed as part of an overall update process but can optionally be done as a stand-alone update by issuing the following command (as root): # yum update mcp-client-rhel*

The MCP client packages are specific to each major version of RHEL; therefore, using an asterisk ("*") will allow the above command to run on any RHEL version.

Once the command is issued to start the migration, the process will run fully unattended with no interaction required by the user. All migration activity is logged in /var/log/rhui-client-install.

Current documentation can be found here. https://docs.mcp-services.net/x/UAIu
New documentation will be made available here after the change. https://docs.mcp-services.net/x/ygSZ

Change Reference Number: CHM121232839
All Locations: Tuesday May 14th 08:00 AM US Pacific Daylight Time (15:00 UTC)
Expected Total Duration: 1 Hours
May 3, 21:26 UTC
Completed - The scheduled maintenance has been completed.
May 14, 09:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 14, 05:30 UTC
Scheduled - Impact: No impact to clients expected. There is a medium risk of brief periods of network latency.

Dear Client

On the date listed below the Internet Service Provider for the following location will be performing emergency network maintenance. The ISP will be performing software upgrades to upstream routers supplying internet access to the below cloud location. Engineers will be failing traffic over to a redundant connection, prior to the maintenance. This type of maintenance has been performed in the past without impact to traffic, however there is a medium risk of brief latency and or packet loss during the maintenance window.

Change Reference Number: CHM121190116
US East: (NA5,NA9,ASH02): Monday May 13th 10:30 PM US Pacific Daylight Time (14/5 05:30 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.
Apr 25, 00:05 UTC
May 13, 2019

No incidents reported.

May 12, 2019

No incidents reported.

May 11, 2019
Completed - The scheduled maintenance has been completed.
May 11, 13:01 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 11, 05: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 Dimension Data Cloud Services. During this maintenance we will be upgrading storage devices to the latest vendor approved and tested OS release. Although this type of maintenance has been performed in the past without impact, there is a low risk of latency and service disruption to Client Cloud Servers. The Admin UI/API and Community will remain available.

Change Reference Number: CHM121202163
US West (NA12): Friday May 10th 09:00 PM US Pacific Standard Time (11/5 05:00 UTC)
Expected Total Duration: 8 Hours

Note this maintenance is specific only to the affected data center location and other Geographic Regions will continue to function normally.
May 7, 17:16 UTC
Completed - The scheduled maintenance has been completed.
May 11, 06:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 11, 04:00 UTC
Scheduled - Impact: No impact expected, low risk of latency or brief service disruption of traffic between MCP locations.

Dear Client

On the date listed below engineers will be performing emergency maintenance in all cloud locations. This maintenance is necessary to prevent unplanned outages of traffic between cloud locations. Engineers will perform configuration changes to network devices controlling traffic between MCP locations. Engineers do not expect any interruption of service, however there is a low risk of latency and or brief service disruption for traffic destined for other MCP locations.

Change Reference Number: CHM121355576
North America (NA-All Locations): Friday May 10th 09:00 PM US Pacific Daylight Time (11/5 04:00 UTC)
Expected Total Duration: 2 Hours

This maintenance is specific only to the affected data center locations and other Geographic Regions will continue to function normally.
May 9, 21:46 UTC
Completed - The scheduled maintenance has been completed.
May 11, 02:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 10, 19: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 Dimension Data Cloud Services. During this maintenance we will be upgrading storage devices to the latest vendor approved and tested OS release. Although this type of maintenance has been performed in the past without impact, there is a medium risk of latency and service disruption to Client Cloud Servers. The Admin UI/API and Community will remain available.

Change Reference Number: CHM121201689
Amsterdam (EU7): Friday May 10th 09:00 PM Central European Standard (19:00 UTC)
Expected Total Duration: 7 Hours

Note this maintenance is specific only to the affected data center location and other Geographic Regions will continue to function normally.
Apr 25, 20:59 UTC