# Usage Limitations

## **Product Quota Limitations**

| Quota Name                                                   | Default Quota | Description                                                  |
| ------------------------------------------------------------ | ------------- | ------------------------------------------------------------ |
| UGN instances per primary account                            | 5             | All subaccounts share the primary account's quota.           |
| Associated network instances per UGN instance                | 25            | The total number of network instances that can be associated with a single UGN instance, regardless of type. |
| Regions per UGN instance                                     | 20            | ßThe total number of distinct regions represented by the network instances associated with a single UGN instance. |
| Regions that can be added to a UGN instance in a single operation | 5             | When associating network instances from multiple regions, up to five regions can be added in a single operation. To add more regions, perform multiple association operations. |
| Inbound route policies per UGN instance                      | 50            | The maximum number of route policies that can take effect in the inbound direction. |
| Outbound route policies per UGN instance                     | 50            | The maximum number of route policies that can take effect in the outbound direction. |
| Effective route policies per region within a UGN instance    | 100           | The maximum number of route policies that can take effect for network instances in the same region. |

If you need to increase the quota, please click Help and Support in the upper right corner of the console - Create Ticket to initiate a quota increase application. 

## **Product Allocation Restrictions**

1. Bandwidth Package Quota Adjustment: By default, users are allowed to increase or decrease the size of the bandwidth package and delete the bandwidth package on the console.
2. Currently, users are not allowed to switch the service level and smart route of the bandwidth package on the console.
3. Users are currently allowed to switch between fixed-bandwidth billing and Max5 peak-value billing on the console. The switching frequency is once a month, and it takes effect at 0:00 of the next month by default. **Flow-based billing does not support switching.**


If you need to adjust other parameters, please submit a ticket or contact your account manager.



## **Other Usage Limitations**

There are the following ownership relationships among various resource objects:

- One UGN instance belongs to one project.
   1. When deleting a UGN instance, all its subordinate resources must be deleted.

- One network instance can only be added to one UGN instance:
   1. When there is a connection relationship among network instances, they cannot be added to a UGN instance.
   2. One UGN instance can be associated with the network instances of multiple projects under the same main account. If it is a sub-account, it can only be associated with the network instances that the sub-account has the permission to access.
   3. Only after signing a cross-border contract can the network instances with cross-border relationships be added to a UGN instance.
   4. After the cross-border contract expires or becomes invalid, the network instances that have already been added to the UGN instance do not need to be removed, and new network instances can still be added at this time.

- When any two cross-region network instances need to communicate, there must be a bandwidth package between the regions:
   1. There must be and can only be one bandwidth package between any two regions where network instances exist. One region can have bandwidth packages with multiple other regions.
   2. One bandwidth package belongs to only one UGN instance.
   3. A custom bandwidth package can only be created when network instances exist in both regions at the two ends of a line.
   4. A cross-border bandwidth package (including the default bandwidth package and the custom bandwidth package) can only be created after signing a cross-border contract.
   5. Only after a custom bandwidth package is deleted can all the network instances in the regions it involves be removed from the UGN instance.
- When network instances are first added from two different regions within a UGN instance, a default bandwidth package will currently be automatically created for that line:
   1. The default bandwidth package has a speed limit of 5 kb. Except that it is not charged, it is the same as a custom bandwidth package.
   2. After a custom bandwidth package is purchased for a line, the default bandwidth package will be deleted.
   3. When a custom bandwidth package is deleted, a default bandwidth package will be automatically created again.