Notice to Users – Suppression of MCP 1.0 locations without Cloud Assets in the Updated UI from 22 June 2017
Scheduled Maintenance Report for NTT Ltd. Cloud
The scheduled maintenance has been completed.
Posted Jul 22, 2017 - 00:00 UTC
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Jun 22, 2017 - 00:03 UTC
In progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Jun 22, 2017 - 00:01 UTC
Dear Cloud User,

Starting 22 June 2017, the majority of users will no longer be able to see unused MCP 1.0 locations on the Updated UI. The API will also not list unused MCP 1.0 locations. Unused MCP 1.0 locations are where a client (CloudControl “Organization”) does not have any cloud assets deployed.
This change will ensure that existing clients’ expansion to previously unused locations and all consumption of new clients occur on MCP 2.0 platforms. Clients’ future growth in currently used MCP 1.0 locations are not impacted. Clients with dedicated MCP 1.0 platforms are also not impacted, even when new CloudControl Organizations are created.
MCP 2.0 platforms are superior to MCP 1.0 in all regards, providing clients with more functionality and performance at the same or lower cost as MCP 1.0. Cloud Servers in MCP 1.0 locations can communicate securely with Cloud Servers in MCP 2.0 locations by means of the CPNC service.
Existing clients who use MCP 1.0 platforms and plan future expansion to currently unused cloud locations should contact their account team for advice on their best options around coexistence with or migration to MCP 2.0.

Please contact us if you have any questions.

Dimension Data Cloud Network Operations Center (NOC)
Dimension Data
Posted May 11, 2017 - 17:16 UTC
This scheduled maintenance affected: NA - US East (Managed Hosting ASH01, Managed Hosting ASH02, NTT Cloud NA1, NTT Cloud NA5, NTT Cloud NA9, Cloud Monitoring, CPNC), EU - Amsterdam (Managed Hosting AMS01, NTT Cloud EU7, Cloud Monitoring, CPNC), NA - US West (Managed Hosting SJC03, Managed Hosting - SNU01, NTT Cloud - NA3, NTT Cloud - NA12, Cloud Monitoring, CPNC), IL - Israel (NTT Cloud IL, CaaS IL1, CaaS IL2, CPNC), CA - Canada (Managed Hosting YYZ01, NTT Cloud CA1, NTT Cloud CA2, Cloud Monitoring, CPNC), AU - New Zealand (Managed Hosting HLZ01, NTT Cloud AU8, NTT Cloud AU11, Cloud Monitoring, CPNC), AP - Tokyo (Managed Hosting HND01, NTT Cloud AP1, NTT Cloud - AP4, Cloud Monitoring), EU - Germany (Managed Hosting FRA01, NTT Cloud EU6, Cloud Monitoring, CPNC), AP - Singapore (Managed Hosting SIN01, NTT Cloud AP3, Cloud Monitoring, CSfS AP9, CSfS AP10), AP - Hong Kong (NTT Cloud AP2, NTT Cloud AP5, Cloud Monitoring), AU - Sydney (NTT Cloud AU1, NTT Cloud AU6, NTT Cloud AU9, Cloud Monitoring, CPNC), EU - Belgium (CaaS EU9, CPNC), AU - Melbourne (NTT Cloud AU2, NTT Cloud AU10, Cloud Monitoring, CPNC), NTT Cloud AU, NTT Cloud AP, NTT Cloud CA, NTT Cloud EU, NTT Cloud NA, AF - Johannesburg (NTT Cloud - AF3, Cloud Monitoring, CSfS AF4, CSfS AF5, CPNC), and EU - United Kingdom (NTT Cloud EU8, Cloud Monitoring, CPNC).