Usage Limitations

Product Quota Limitations

Routing Limitations

Since Cloud Network can enable multiple network instances to communicate with each other, to ensure smooth communication between instances, there can be no subnet overlap between the VPC instances joined to the Cloud Network. If the subnets of two VPCs overlap or conflict, they cannot join the Cloud Network.

Product Matching Limitations

1. Bandwidth package quota adjustment: By default, the console allows users to adjust the bandwidth package size, and allows to delete the bandwidth package.
2. Currently, the console does not support users to switch the service level and intelligent path of the bandwidth package.
3. The currently supported billing methods are fixed bandwidth billing and Max5 peak billing. The console allows users to switch between billing methods once a month, which defaults to 0 o’clock of the next month.

To adjust other parameters, please submit a ticket or contact your customer manager;

Other Usage Limitations

There are the following relationships and quota limitations between different resource objects:

1. A Cloud Network instance belongs to a project;

   1. When deleting the Cloud Network, all subordinate resources should be deleted;
   2. The number of UGN instance quotas that can be created under a single account refers to the quota limitation under the main account;

2. A Cloud Network instance can associate up to 20 network instances:

   1. When a network instance has a connection, it cannot be added to the Cloud Network instance;
   2. A network instance can only join one Cloud Network instance;
   3. A Cloud Network instance can include network instances of different projects that the current sub-account has permission to;
   4. Only after signing a cross-border contract can a network instance with a cross-border relationship be added to the Cloud Network instance;
   5. After the cross-border contract expires/becomes invalid, the network instance that has joined the Cloud Network instance does not need to quit, and new network instances can still be added at this time;
   6. When binding/unbinding the same network instance in bulk, an error is returned;

3. A Cloud Network instance can associate network instances of multiple projects under the same main account:

4. Whenever two cross-domain network instances need to communicate, there must be a bandwidth package between these regions:

   1. Between any two regions with network instances, there must and can only be one bandwidth package, and one region can have bandwidth packages with multiple regions at the same time;
   2. A bandwidth package can only be bound to one Cloud Network instance at the same time;
   3. When two different regions join the network instance for the first time in the Cloud Network instance, a default bandwidth package will be automatically created for this line;
   4. The default bandwidth package limits the speed to 5kb, which is consistent with the custom bandwidth package except for the free charge;
   5. After purchasing a custom bandwidth package for a line, the default bandwidth package will be deleted;
   6. When deleting a custom bandwidth package, a default bandwidth package will be automatically recreated;
   7. Only when there are network instances at both ends of a line can a custom bandwidth package be created;
   8. Only after a custom bandwidth package is deleted can all network instances involved in its region quit the Cloud Network instance;
   9. Only after signing a cross-border contract can a cross-border bandwidth package be created (including default bandwidth packages and custom bandwidth packages).