Billing Overview
Last updated: 2025-11-18 19:46:30
This document describes the billing and pricing of Cloud Connect Network (CCN).
Billing
The service fee of Tencent CCN consists of three parts, namely the network connection instance fee, cross-region data transfer fee, and inbound traffic processing fee.
Note:
The connected network instance fee and inbound traffic processing fee have been billed since July 03, 2023. For details, see the Announcement.
Billable item | Billing mode | Payment method | Billing unit | Use case |
Connected network instance fee | Pay-as-you-go | Pay after use | USD/instance/hour | The connection fee for the network instances associated with CCN, see Connected Network Instance Fee |
Cross-region data transfer fee | Pay-as-you-go by bandwidth | Pay after use | USD/GB, based on the actual monthly usage, calculated according to the 95th percentile bandwidth peak and the proportion of effective usage days. | Suitable for services with periodic peak bandwidth. For specific pricing, see Pay-as-You-Go by Bandwidth. The pay-as-you-go by bandwidth billing mode is in grayscale. To use it, submit a ticket. |
| Pay-as-you-go by traffic | Pay after use | USD/GB, billed based on cross-region outbound traffic | Suitable for services with fluctuating traffic that prefer to pay based on actual usage. For specific pricing, see Pay-As-You-Go by Traffic. The pay-as-you-go by traffic billing mode is in grayscale. To use it, submit a ticket. |
Inbound traffic processing fee | Pay-as-you-go | Pay after use | USD/GB | |
Connected Network Instance Fee
A connected network instance refers to a VPC, Direct Connect, or VPN gateway instance associated with a CCN instance.
Billing mode
Pay-as-you-go on an hourly basis. The minimum billing unit is one hour.
Calculation
Hourly connected network instance fee = Unit price per connected instance (USD/instance) x Total number of connected network instances in the billing cycle.
Note:
The VPC where Tencent Cloud Lighthouse is located is not included.
Only out-of-plan usage is charged.
Each account has a free quota of two network connection instances until 00:00:00, April 1, 2026.
If you remove a network connection instance under the free quota, the quota will be released in one hour.
When an account has more than two network connection instances, the system randomly selects two instances every hour for fee deduction.
In cross-account scenarios, you can select the account responsible for bearing the network connection instance fee. If the account designated to bear the fee is the same as the account where the network instance resides, this instance directly incurs the network connection instance fee and is excluded from the free tier.
Billable item | Billing mode | Usage | Price (USD) | |
Connected network instance (USD/instance/hour) | Pay-as-you-go | ≤ 2 instances | Free of charge before April 1, 2026 00:00:00 (UTC+8) | |
| | > 2 instances (beyond the first two) | The Chinese mainland | 0.05 |
| | | Regions outside the Chinese mainland | 0.06 |
Billing Examples
Case Scenario | Applicable Billing Rule | Network Connection Instance Fee per Hour |
Assume that your CCN contains the following instances: 1 VPC instance that hosts Tencent Cloud Lighthouse (Lighthouse) in the Chinese mainland 2 standard VPC instances in the Chinese mainland 3 VPC gateway instances in Hong Kong (China) | The VPC instance that hosts Lighthouse is free of charge. You also have a free quota of 2 random instances. | Potential final charges: The fee for 1 standard VPC instance in the Chinese mainland The fee for 2 VPC gateway instances in Hong Kong (China) Total cost = Number of connected instances in the Chinese mainland x Unit price in the Chinese mainland + Number of connected instances in other regions x Unit price in other regions = 1 x USD 0.05 + 2 x USD 0.06 = USD 0.17 |
Cross-Region Data Transfer Fee
CCN charges fees for cross-region data transfer and supports two billing modes (pay-as-you-go by bandwidth and pay-as-you-go by traffic) and three service levels (Platinum, Gold, and Silver).
You can select the optimal solution that balances cost and quality based on your business needs. For example, for business data backup, we recommend that you choose pay-as-you-go by traffic - Silver. For real-time audio/video or game acceleration, we recommend that you choose pay-as-you-go by bandwidth - Gold.
The following describes the three service levels of CCN cross-region bandwidth:
Service level | Service availability | Price ratio | Use case |
Platinum | 99.995% | 1.5 | Applicable to services that require extremely high communication quality, such as transaction and payment services. |
Gold | 99.95% | 1 | Applicable to services that require relatively high communication quality, such as gaming and video services. |
Silver | 99.50% | 0.75 | Applicable to services not sensitive to communication quality, such as offline data backup. |
Note:
For the same region (whether within the same account or across different accounts), bandwidth usage of 5 Gbps and below is free of charge. However, usage beyond the free tier of network connection instance fees and inbound traffic processing fees will still incur fees. If you require bandwidth exceeding 5 Gbps within the same region, submit a ticket for consultation.
The service level for intra-region interconnection is Gold and cannot be modified.
Three service levels (Platinum, Gold, and Silver) are provided for cross-region interconnection. You can select a service level when creating a CCN instance. Cross-account and cross-region costs are billed to the account of the CCN instance owner.
Under normal network conditions, the Platinum, Gold, and Silver service levels exhibit identical latency and packet loss performance. The primary distinction lies in the priority of protection under circumstances such as failures.
Pay-As-You-Go by Bandwidth
In this mode, you use resources first and pay for them later. Fees are calculated based on the 95th percentile of your monthly bandwidth usage and the proportion of active days. This mode is suitable for services with significant bandwidth fluctuations.
For example, if you have 10 Mbps of bandwidth between Beijing and Shanghai regions but also a bandwidth burst of 30 Mbps. We recommend you select pay-as-you-go by monthly 95th percentile because you may only need to pay for 10 Mbps of bandwidth after the top 5% is removed.
Note:
The pay-as-you-go by bandwidth billing mode is in grayscale. To use it, submit a ticket.
In the pay-as-you-go by bandwidth billing mode, bandwidth is available for use after you create a CCN instance. You do not need to purchase bandwidth separately. The default bandwidth limit is 1 Gbps and can be adjusted as needed. For more information about bandwidth management, see Configure bandwidth.
In the pay-as-you-go by bandwidth billing mode, you are charged based on the 95th percentile of your monthly bandwidth usage.
Billing cycle
Monthly pay-as-you-go: Fees are generated each month. You will be charged for the current month on the first day of the following month between 8 AM and 10 AM.
Fee calculation
Total monthly cost of CCN = Sum of the interconnection costs of all regions
Monthly interconnection cost between two regions = 95th percentile of the monthly peak bandwidth of the interconnection between two regions × Proportion of valid days × Tiered unit price
95th percentile of monthly peak bandwidth: Bandwidth data is collected every 5 minutes. The peak bandwidth (higher one between inbound and outbound bandwidths) between two regions within each 5 minutes is taken as a sample point. All sample points of a month are sorted in descending order and the top 5% are removed. The highest value of the remaining sample points is used as the 95th percentile of the monthly peak bandwidth. For example, you used CCN in June to build cross-region connection between regions A and B for 14 valid days. Because one sample point is generated every five minutes, 288 (60 min × 24/5 min) sample points are generated every day, and 4,032 (14 days × 288 sample points/day) sample points are generated in 14 days. The bandwidth values of the 4,032 sample points are sorted in descending order, the top 5% (4,032 sample points × 0.05 = 201.6 sample points) are removed, and the bandwidth value of the 202nd sample point is used as the 95th percentile of the monthly peak bandwidth.
Proportion of valid days: Proportion of valid days = Number of valid days in the current month/Number of days in the current month. A valid day refers to when at least one sample point has a bandwidth greater than 10 Kbps on that day.
Tiered unit price: Unit price of the tier into which the 95th percentile of the monthly peak bandwidth falls.
Pricing
Note:
The billable tier is the tier where the bandwidth peak falls.
For the price of connection between regions outside the Chinese mainland, please contact your sales rep.
CCN is a pay-as-you-go service based on actual usage. To avoid unexpected costs, we recommend setting a bandwidth cap between regions.
Service level | Local region | Peer region | Bandwidth unit price (USD/Mbps/month) | ||
| | | (0 Mbps-100 Mbps] | (100 Mbps-1,000 Mbps] | (> 1,000 Mbps) |
Platinum | Chinese mainland | Chinese mainland | 55 | 21 | 13 |
| | Gold | 37 | 13 | 9 |
| | Silver | 28 | 10 | 7 |
Billing examples
Assume that your CCN instance (service level: Gold) was connected to network instances in Guangzhou, Beijing, and Shanghai in June 2024, with 14 active days in the month. The bandwidth usage is shown in the following figure:
Fee for data transfer between Guangzhou and Beijing = 95th percentile of monthly bandwidth usage x Proportion of active days x Tiered unit price = 120 Mbps x (14/30) x 13 USD/Mbps/month = USD 728
Fee for data transfer between Beijing and Shanghai = 95th percentile of monthly bandwidth usage x Proportion of active days x Tiered unit price = 30 Mbps x (14/30) x 37 USD/Mbps/month = USD 518
The total amount payable = Sum of data transfer fees across all regions under the account = USD 728 + USD 518 = USD 1,246
Pay-As-You-Go by Traffic
In this mode, you use resources first and pay for them later. Fees are calculated based on cross-region outbound traffic. This mode is suitable for services that have unstable traffic volumes and require payment by actual usage.
Note:
The pay-as-you-go by traffic billing mode is in grayscale. To use it, submit a ticket.
In the pay-as-you-go by traffic billing mode, bandwidth is available for use after you create a CCN instance. You do not need to purchase bandwidth separately. The default bandwidth limit is 1 Gbps and can be adjusted as needed. For more information about bandwidth management, see Configuring Bandwidth.
Billing Cycle
Pay-as-you-go by traffic: Payment is made after resource usage based on the actual consumption, with hourly settlement. Usage under one hour is billed as a full hour.
Billing Formula
Total data transfer fee = Sum of cross-region outbound traffic fees across all regions
Cross-region outbound traffic fee = Cross-region outbound traffic x Unit price
Pricing
Note:
You are charged based on cross-region outbound traffic.
Pay-as-you-go by traffic supports only data transfer between non-cross-border regions. If you have cross-border requirements, use the pay-as-you-go by bandwidth billing mode.
Service Level Platinum Pricing Table (USD/GB) | Inbound Region | |||||
Outbound Region | Chinese mainland | Asia Pacific | Europe | North America | South America | Middle East |
Chinese mainland | 0.1014 | - | - | - | - | - |
Asia Pacific | - | 0.1109 | 0.1109 | 0.1109 | 0.1200 | 0.3750 |
Europe | - | 0.0750 | 0.0300 | 0.0750 | 0.0750 | 0.0750 |
North America | - | 0.0750 | 0.0750 | 0.0277 | 0.0750 | 0.3000 |
South America | - | 0.2070 | 0.2070 | 0.2070 | 0.2070 | 0.4800 |
Middle East | - | 0.3750 | 0.3000 | 0.3000 | 0.4800 | 0.4800 |
Service Level Gold Pricing Table (USD/GB) | Inbound Region | |||||
Outbound Region | Chinese mainland | Asia Pacific | Europe | North America | South America | Middle East |
Chinese mainland | 0.0676 | - | - | - | - | - |
Asia Pacific | - | 0.0739 | 0.0739 | 0.0739 | 0.0800 | 0.2500 |
Europe | - | 0.0500 | 0.0200 | 0.0500 | 0.0500 | 0.2000 |
North America | - | 0.0500 | 0.0500 | 0.0185 | 0.0500 | 0.2000 |
South America | - | 0.1380 | 0.1380 | 0.1380 | 0.1380 | 0.3200 |
Middle East | - | 0.2500 | 0.2000 | 0.2000 | 0.3200 | 0.3200 |
Service Level Silver Pricing Table (USD/GB) | Inbound Region | |||||
Outbound Region | Chinese mainland | Asia Pacific | Europe | North America | South America | Middle East |
Chinese mainland | 0.0507 | - | - | - | - | - |
Asia Pacific | - | 0.0555 | 0.0555 | 0.0555 | 0.0600 | 0.1870 |
Europe | - | 0.0375 | 0.0150 | 0.0375 | 0.0375 | 0.1500 |
North America | - | 0.0375 | 0.0375 | 0.0138 | 0.0375 | 0.1500 |
South America | - | 0.1035 | 0.1035 | 0.1035 | 0.1035 | 0.2400 |
Middle East | - | 0.1870 | 0.1500 | 0.1500 | 0.2400 | 0.2400 |
Billing examples
Assume that your CCN instance (service level: Gold) was connected to network instances in Guangzhou, Beijing, and Shanghai. The cross-region outbound traffic is shown in the following figure:
Note:
You are charged based on cross-region outbound traffic.
For the Gold service level, the list price for data transfer between regions in the Chinese mainland is 0.0676 USD/GB.
Outbound traffic fee for data transfer from Guangzhou to Beijing = 1,500 GB x 0.0676 USD/GB = USD 101.4
Outbound traffic fee for data transfer from Beijing to Guangzhou = 500 GB x 0.0676 USD/GB = USD 33.8
Outbound traffic fee for data transfer from Shanghai to Beijing = 3,000 GB x 0.0676 USD/GB = USD 202.8
Outbound traffic fee for data transfer from Beijing to Shanghai = 1,000 GB x 0.0676 USD/GB = USD 67.6
The total amount payable = Sum of cross-region outbound traffic fees across all regions under the account = USD 101.4 + USD 33.8 + USD 202.8 + USD 67.6 = USD 405.6
Inbound Traffic Processing Fee
Inbound traffic refers to the traffic coming from connected network instances (VPC/Direct Connect/VPN gateway instances) to a CCN instance. For specific traffic details, see Viewing Monitoring Data. CCN processes inbound traffic data and charges corresponding fees.
Note:
Traffic sent from the Cloud Connect Network to its associated network connection instances (including VPC instances, Direct Connect (DC) gateway instances, and VPN gateway instances), namely the outbound traffic, is not subject to traffic processing charges.
You are charged for inbound cross-region traffic and inbound traffic between non-VPC entities within the same region.
Intra-regional cross-VPC inbound traffic is free, except for the following two scenarios:
CLB bound to real servers across VPCs.
Intra-city access via custom routing.
In cross-account scenarios, you can select the account responsible for bearing the inbound traffic processing fee. If the account designated to bear the fee is the same as the account where the network instance resides, the traffic processing fee incurred by this instance will be directly billed and excluded from the free tier.
Billing mode
Pay-as-you-go on an hourly basis. The minimum billable unit is one hour.
Calculation
Inbound traffic processing fee = Inbound traffic x Unit price.
The specific prices are as follows:
Note:
A free quota of 100 TB of inbound traffic is provided per month from now till 00:00:00, April 1, 2026.
Billable item | Billing mode | Usage | Price (USD) |
Inbound traffic (USD/GB) | Pay-as-you-go | ≤ 100 TB | Free of charge till April 01, 2026 00:00:00 (UTC+8) |
| | > 100 TB (traffic beyond the free quota) | 0.02 |
Billing examples
Assume that your CCN instance was connected to 2 network instances in Guangzhou and 1 network instance in Beijing in June 2024. The inbound traffic is shown in the following figure:
Inbound traffic processing fee = (Total cross-region inbound traffic – Cross-region traffic free tier) x Unit price of inbound traffic = (Inbound traffic from Beijing to Guangzhou Zone 1 + Inbound traffic from Guangzhou Zone 2 to Beijing – Cross-region traffic free tier) = (120 TB + 15 TB – 100 TB) x 0.02 USD/GB = USD 716.8
Note:
Since the traffic from Guangzhou Zone 1 to Guangzhou Zone 2 is within the same region, the inbound traffic fee is 0.
1 TB = 1024 GB
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback