- What's New
- Function Overview
- Service Overview
- Billing
- Getting Started
-
User Guide
-
Cloud Connection Operation Guide
- Permissions Management
- Cloud Connections
- Cross-Border Permits
- Network Instances
-
Bandwidth Packages
- Buying a Bandwidth Package
- Modifying a Bandwidth Package
- Binding a Bandwidth Package to a Cloud Connection
- Unbinding a Bandwidth Package from a Cloud Connection
- Changing a Pay-per-Use Bandwidth Package to a Yearly/Monthly Bandwidth Package
- Unsubscribing from a Yearly/Monthly Bandwidth Package
- Deleting a Pay-per-Use Bandwidth Package
- Managing Bandwidth Package Tags
- Inter-Region bandwidths
- Cross-Account Authorization
- Routes
- Monitoring and Auditing
- Quotas
- Central Network Operation Guide
-
Cloud Connection Operation Guide
-
Best Practices
- Connecting VPCs in the Same Region But in Different Accounts
- Connecting VPCs in Different Regions and Accounts
- Connecting On-Premises Data Centers and VPCs
- Connecting VPCs in Different Geographic Regions
- Connecting VPCs in Different Accounts
- Using a Cloud Connection and SNAT to Enable Private Networks to Access the Internet
- Using a Cloud Connection and DNAT to Enable the Internet to Access Private Networks
- Using a Cloud Connection and DNAT to Improve the Web Delivery Across Regions
- Using a Cloud Connection and a VPC Peering Connection to Connect VPCs Across Regions
-
API Reference
- Before You Start
- API Overview
- Calling APIs
-
API
-
Cloud Connections
- Creating a Cloud Connection
- Querying the Cloud Connection List
- Querying a Cloud Connection
- Updating a Cloud Connection
- Deleting a Cloud Connection
- Adding a Tag to a Cloud Connection
- Deleting a Tag from a Cloud Connection
- Querying the Tags Added to a Cloud Connection
- Querying Cloud Connections by Tag
- Network Instances
-
Bandwidth Packages
- Creating a Bandwidth Package
- Querying the Bandwidth Package List
- Querying a Bandwidth Package
- Updating a Bandwidth Package
- Deleting a Bandwidth Package
- Adding a Tag to a Bandwidth Package
- Deleting a Tag from a Bandwidth Package
- Querying the Tags of a Bandwidth Package
- Querying Bandwidth Packages by Tag
- Binding a Bandwidth Package to a Cloud Connection
- Unbinding a Bandwidth Package from a Cloud Connection
- Inter-Region Bandwidths
- Cloud Connection Routes
- Authorizations
-
Central Networks
- Creating a Central Network
- Querying the Central Network List
- Querying a Central Network
- Updating a Central Network
- Deleting a Central Network
- Adding a Tag to a Central Network
- Deleting a Tag from a Central Network
- Querying the Tags Added to a Central Network
- Querying Central Networks by Tag
- Adding a Central Network Policy
- Querying the List of Central Network Policies
- Applying a Central Network Policy
- Deleting a Central Network Policy
- Querying the Changes Between the Current Policy and an Applied Policy
-
Central Network Attachments
- Adding a Global DC Gateway to a Central Network
- Querying the List of Global DC Gateways on a Central Network
- Querying a Global DC Gateway on a Central Network
- Updating a Global DC Gateway on a Central Network
- Adding a Route Table of an Enterprise Router as an Attachment on a Central Network
- Querying the List of Enterprise Router Route Tables on a Central Network
- Querying an Enterprise Router Route Table on a Central Network
- Updating an Enterprise Router Route Table on a Central Network
- Querying the List of Central Network Attachments
- Removing an Attachment from a Central Network
- Central Network Connections
- Site Network Management
- Site-to-site Connection Management
- Cloud Connection Quotas
- Central Network Quotas
- Central Network Capabilities
- Site Network Quotas
- Site Network Capabilities
- Specifications
-
Global Connection Bandwidths
- Querying the Global Connection Bandwidth List
- Creating a Global Connection Bandwidth
- Querying a Global Connection Bandwidth
- Updating a Global Connection Bandwidth
- Deleting a Global Connection Bandwidth
- Binding a Global Connection Bandwidth to an Instance
- Unbinding a Global Connection Bandwidth from an Instance
- Querying the List of Global Connection Bandwidths That Meet the Binding Conditions
- Querying the Tenant Configuration of a Global Connection Bandwidth
- Querying the Line Specification List
- Querying the Site List
- Querying the Line Grade List
-
Global Connection Bandwidth Tag Management
- Querying a Global Connection Bandwidth Tag in an Account
- Adding a Tag to a Global Connection Bandwidth
- Deleting a Tag from a Global Connection Bandwidth
- Adding Tags to a Global Connection Bandwidth
- Deleting Tags from a Global Connection Bandwidth
- Querying the Number of Global Connection Bandwidth Tags in an Account
- Querying the List of Global Connection Bandwidths in an Account
- Querying All Global Connection Bandwidth Tags in an Account
-
Cloud Connections
- Permissions and Supported Actions
- Appendix
- Historical APIs
- SDK Reference
-
FAQs
-
Popular Questions
- How Do I Configure Cloud Connect?
- What Can I Do If Cross-Region Network Communications Fail?
- What Tools Can I Use to Test Network Connectivity After All Configurations Are Complete?
- What Can I Do If There Is a Route Conflict When I Load a Network Instance to a Cloud Connection?
- How Can I Modify the Bandwidth of a Purchased Bandwidth Package?
- Do I Need to Create Another Cloud Connection If Network Instances in One Region Need to Communicate with Network Instances in Two Other Regions That Have Already Been Loaded to a Cloud Connection?
- Why Do I Need Cloud Connect If the Network Latency Is the Same as on the Internet?
-
General Consulting and Service Use
- What Can I Do with Cloud Connect?
- How Do I Configure Cloud Connect?
- What Are the Differences Between Cloud Connect and VPC Peering?
- What Tools Can I Use to Test Network Connectivity After All Configurations Are Complete?
- What Network Instance Types Does Cloud Connect Support?
- How Many Bandwidth Packages Can I Bind to a Cloud Connection?
- Are the Uplink and Downlink Rates of the Configured Inter-Region Bandwidth the Same?
- Are There Any Limits on the Traffic for Cross-Region Network Communications?
- What Are the Metrics for Traffic Monitoring?
- What Are the Restrictions of Using Cloud Connect?
- Where Can I Add Routes for a Cloud Connection on the Management Console?
- Do I Need to Bind an EIP to Each ECS in the VPCs Connected over a Cloud Connection?
- How Can I Modify the Bandwidth of a Purchased Bandwidth Package?
- Will the Modified Inter-Region Bandwidth Take Effect Immediately?
- How Can I Modify Inter-Region Bandwidth?
- Do I Need to Create Another Cloud Connection If Network Instances in One Region Need to Communicate with Network Instances in Two Other Regions That Have Already Been Loaded to a Cloud Connection?
- Are Network Circuits Physically Isolated?
- Is Cloud Connect an Out-Of-The-Box Service?
- How Can Cloud Connect Offer High Availability?
-
Console Operations
- How Do I Configure Cloud Connect?
- What Can I Do If There Is a Route Conflict When I Load a Network Instance to a Cloud Connection?
- How Many Bandwidth Packages Can I Bind to a Cloud Connection?
- What Are the Restrictions of Using Cloud Connect?
- How Can I Apply for a Cross-Border Permit?
- Where Can I Add Routes for a Cloud Connection on the Management Console?
- How Can I Modify the Bandwidth of a Purchased Bandwidth Package?
- How Can I Modify Inter-Region Bandwidth?
- What Tool Can I Used to Test the Bandwidth Rate of a Cloud Connection?
- Will the Modified Inter-Region Bandwidth Take Effect Immediately?
- Bandwidth Packages
-
Bandwidth, Latency and Packet Loss
- What Can I Do If Cross-Region Network Communications Fail?
- Will the Modified Inter-Region Bandwidth Take Effect Immediately?
- How Can I Troubleshoot Network Connectivity for a Hybrid Cloud Built Using Cloud Connect and Direct Connect?
- Do I Need a Bandwidth Package for Testing Network Connectivity?
- Why Do I Need Cloud Connect If the Network Latency Is the Same as on the Internet?
- Are the Uplink and Downlink Rates of the Configured Inter-Region Bandwidth the Same?
- Are There Any Limits on the Traffic for Cross-Region Network Communications?
- How Can I Modify an Inter-Region Bandwidth?
- Are Network Circuits Physically Isolated?
- How Can Cloud Connect Offer High Availability?
-
Cross-Border Permit
- Why Do I Need a Cross-Border Permit?
- Who Approves Cross-Border Permits?
- How Can I Apply for a Cross-Border Permit?
- When Would I Need to Apply for a Cross-Border Permit?
- How Long Will a Cross-Border Permit Be Approved?
- Why Is Additional Real-Name Authentication Required After I Have Completed Huawei Cloud Real-Name Authentication?
- Can I Modify the Content of the Cloud Connect Cross-Border Circuit Service Agreement?
- Can I Download the Materials for My Cross-Border Permit Application on the Console After I Delete Them from My PC?
- Does Huawei Cloud Need to Sign and Stamp the Seal on the Materials for Cross-Border Permit Application?
- Networking and Cloud Connect Scenarios
-
Cross-Account Authorization
- Does the Other User Need to Buy a Bandwidth Package If I Want to Load This Other User's VPCs to My Cloud Connection?
- Does the Other User Need to Create a Cloud Connection If I Want to Load This Other User's VPCs to My Cloud Connection?
- How Do I Load VPCs Across Accounts?
- Can a VPC Be Loaded to More than One Cloud Connection?
- Permissions
- Monitoring
- Quotas
-
Popular Questions
- General Reference
Copied.
Why Do I Need Cloud Connect If the Network Latency Is the Same as on the Internet?
Consider the following when you are using Cloud Connect:
Network Performance Measuring Metrics
- Packet loss rate: the proportion of packets lost during network transmission
This metric measures the network's packet forwarding capabilities. The difference between the number of packets from the sender and the number of packets to the receiver is the number of packets lost during network transmission. The percentage of the packets that are lost is the packet loss rate.
- Jitter: fluctuation in the latency of the packets flowing through the network
Physical devices, such routers, that forward data packets on the network have buffers. When an amount of data that exceeds the transmission capacity of the cable is transmitted, physical devices will buffer excess packets. Packets that are not buffered or buffered for a short time arrive faster than those buffered for longer. This variation is called network jitter.
- Latency: the average round-trip time for transmitting packets between two network nodes
For a store-and-forward device, the delay starts when the last bit of the last data frame enters the device and ends when the first bit of the data frame appears on the outbound interface. The time difference is the delay of the storage and forwarding device.
Generally, there are the following types of delay:- Propagation delay: the time taken to transmit a packet in the transmission medium. Propagation delay is directly proportional to the physical distance between the two ends and the packet size. The longer the physical distance and the larger the packet, the longer the transmission delay.
- Device delay: the time taken by a physical device, such as a router, to forward a data packet. The device delay is related to the forwarding performance of the switching device.
- Packet conversion delay: the time taken for encoding and decoding data packets at both ends.
- Jitter buffer delay: Generally, with IP communications for a voice service, a buffer is configured to eliminate the network jitter to prevent the voice quality from being discontinuous. The buffer also causes a certain delay.
Transmission Distance
Cloud Connect uses a DCI backbone network for communications, and the latency depends on the transmission distance and transmission loss.
- A longer distance results in more loss and higher latency.
- A shorter distance results in less loss and lower latency.
To ensure connection reliability, inter-region services are usually carried by multiple connections. The length of each connection varies slightly. Therefore, Cloud Connect does not guarantee the latency.
Advantages of Cloud Connect Compared with the Internet
Two scenarios are presented here to compare the network performance of Cloud Connect and the Internet.
ECS Specification |
2 vCPUs and 4 GB memory |
---|---|
Bandwidth |
4 Mbit/s |
Regions of the VPCs that need to communicate with each other |
CN North-Beijing4 (AZ1) and CN-Hong Kong (AZ1) |
CN East-Shanghai1 (AZ1) and CN-Hong Kong (AZ1) |
|
Test Time |
From 2020/09/09 18:30 to 2020/09/10 09:30 (15 hours in total) |
How This Works |
Internet: Bind EIPs to the servers in the VPCs. Cloud Connect: Load the VPCs in CN North-Beijing1, CN East-Shanghai1, and CN-Hong Kong to one cloud connection. |
Quality of network between CN North-Beijing4 and CN-Hong Kong


Item |
Packet Loss |
Average Latency |
Jitter |
---|---|---|---|
Cloud Connect |
0% |
38.9 ms |
1.57 ms |
Internet |
0.04% |
42.882 ms |
2.105 ms |
Quality of network connection between CN East-Shanghai1 and CN-Hong Kong


Item |
Packet Loss |
Average Latency |
Jitter |
---|---|---|---|
Cloud Connect |
0% |
32.14 ms |
0.514 ms |
Internet |
1.73% |
33.24 ms |
2.838 ms |
You can see from the test results that the performance of Cloud Connect is better than that of the Internet in terms of network latency. Cloud Connect outperforms the Internet in terms of packet loss and jitter.
In summary, Cloud Connect can provide more accurate data transmission and more stable network communications.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot