- Updates and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Operation Overview
- Configuring the Route to Peering Connection
- Creating and Deleting Peering Connection
- Viewing Relevant Routing Policies
- Viewing Monitoring Data of Network Traffic Over a Cross-region Peering Connection
- Configuring the Bandwidth Cap for a Cross-region Peering Connection
- Rejecting a Peering Connection
- Deleting a Peering Connection
- Viewing the Peer Account ID
- Enabling Cross-region Connectivity for Basic Networks
- API Documentation
- Best Practices
- FAQ
- Service Agreement
- Glossary
- Updates and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Operation Overview
- Configuring the Route to Peering Connection
- Creating and Deleting Peering Connection
- Viewing Relevant Routing Policies
- Viewing Monitoring Data of Network Traffic Over a Cross-region Peering Connection
- Configuring the Bandwidth Cap for a Cross-region Peering Connection
- Rejecting a Peering Connection
- Deleting a Peering Connection
- Viewing the Peer Account ID
- Enabling Cross-region Connectivity for Basic Networks
- API Documentation
- Best Practices
- FAQ
- Service Agreement
- Glossary
Non-transitive connectivity of peering connections
A peering connection enables connectivity between two VPCs, but the connectivity cannot be transited.
For example, as shown in the following figure, peering connections are created between VPC 1 and VPC 2, and between VPC 1 and VPC 3. However, due to the non-transitivity of peering connections, traffic cannot flow between VPC 2 and VPC 3.
Note:
Even if a peering connection is created, both ends of the connection cannot communicate with each other if routes for sending and returning packets are not configured at both ends.
Intra-region and cross-region peering connections
VPCs support both intra-region and cross-region peering connections. Due to differences in physical distance and underlying implementation architecture, there are some differences between the two types of connections, as shown in the following table:
| Comparison item | Intra-region peering connection | Cross-region peering connection |
|---|---|---|
| Underlying architecture | Local private network within a single region based on Tencent Cloud | Cross-region internal MPLS network based on Tencent Cloud |
| Bandwidth | Maximum bandwidth for interconnection with public cloud: 5 Gbps Maximum bandwidth for interconnection with BM network: 1 Gbps |
Maximum bandwidth: 1 Gbps, with the following options available for the bandwidth cap (MB/sec): 10, 20, 50, 100, 200, 500, and 1000 For peering connections between Beijing, Shanghai, Guangzhou, Korea, and Hong Kong (China), you can apply for higher bandwidth. If you require data connectivity between Mainland China and other regions, consult your business manager. |
| Billing | Free of charge | Daily billing based on the regions where the two ends of the peering connection are located and the actual network bandwidth used. For more information, see Price overview. |
| Availability | Intra-region service quality level: gold; guaranteed availability: ≥ 99.50% | Linkage availability: Platinum: 99.95% Gold: 99.50% Silver: 99.00% For more information, see SLA. |
| Cross-account connection | Supported | Supported |
| Access permission | The CVMs at either end of a peering connection can access all the resources at the peer end, including CVMs, databases, and CLBs. | The CVMs at either end of a peering connection can access all the resources at the peer end, including CVMs, databases, and CLBs. |
| Function limits | The VPC IP ranges to which the two ends of a peering connection belong cannot overlap. Peering connections are independent of each other. |
The VPC IP ranges to which the two ends of a peering connection belong cannot overlap. If multiple peer VPCs are connected to the same VPC, the IP ranges to which these peer VPCs belong cannot overlap. |
| Application scenario | Connect applications in different VPCs within the same region | Typical application scenario: cross-region disaster recovery VPCs in different regions can communicate with each other over cross-region peering connections, which helps rapidly deploy a 2-region-3-DC solution for disaster recovery and meet the requirement for financial-level network disaster recovery with high bandwidth and reliability. |
Yes
No
Was this page helpful?