- Documentation
Bandwidth Package
Overview
Limits
Limits
Quota limits
Bandwidth limits
Bandwidth Package adopts a distributed high-availability cluster architecture, distributing all traffic evenly across multiple traffic forwarding servers in the cluster. Therefore, the maximum bandwidth you set for the Bandwidth Package will be evenly allocated to these servers.
Maximum traffic for a single connection = Maximum bandwidth of Bandwidth Package ÷ Server count in the cluster.
For example, if you set the maximum bandwidth of Bandwidth Package to 5000 Mbps and the Bandwidth Package cluster contains 4 traffic forwarding servers, then the maximum traffic for a single connection is 5000 Mbps ÷ 4 = 1250 Mbps.
Rate limiting rules for Bandwidth Package:
- Inbound bandwidth: The inbound bandwidth rate is limited to the purchased maximum bandwidth.
- Outbound bandwidth: The outbound bandwidth rate is limited to the purchased maximum bandwidth.
For example, if the maximum bandwidth of your purchased Bandwidth Package is 5000 Mbps, then the maximum inbound and outbound bandwidths are both 5000 Mbps.
tip
- Bandwidth Packages can only reach the set maximum bandwidth when multiple connections are used. You cannot reach the set maximum with less connections.
- When the total bandwidth of a Bandwidth Package instance exceeds 5000 Mbps, the platform automatically activates distributed rate limiting.
- During use, the maximum bandwidth of a Bandwidth Package instance may exceed your set value. With technology upgrades, the limit becomes more precise. Therefore, we recommend setting a maximum bandwidth slightly higher than your business requirements.
Limits on adding cloud resources to Bandwidth Package
Last updated: 2026.06.12 14:16:42