Traffic is the accumulated value of data traffic generated when you use and access COS, including public network upstream traffic, public network downstream traffic, private network upstream traffic, private network downstream traffic, and CDN origin-pull traffic. COS charges you by the accumulated traffic usage.
Note:
For more information on storage classes, see Overview.
The billing unit of the traffic billing item and traffic packages is GB, and the traffic unit conversion ratio is 1,024.For example, 1 TB of public network downstream traffic equals 1,024 GB. A public network downstream traffic package of 1 TB can deduct fees of 1,024 GB of public network downstream traffic.This conversion rule will take effect from April 1, 2025.
Traffic Fee Billing Items
Billable Item
Applicable Storage Class
Description
Applicable Billing Mode
Public network downstream traffic
All Storage Class
Traffic generated by data download from COS to the local system or client over the public network (internet).
Pay-as-you-go: Public network downstream traffic (GB) * unit price per GB
Public network upstream traffic
Traffic generated by data upload from the local system or client to COS over the public network (internet).
Free of charge
Private network upstream traffic
Traffic generated by data transfer from the client to COS over the Tencent Cloud private network.Note: Tencent Cloud products within the same region access each other over the private network by default, with no traffic fees incurred. For more information on how to identify private network access, see Overview > Private Network Access.
Free of charge
Private network downstream traffic
Traffic generated by data transfer from COS to the client over the Tencent Cloud private network.Note: Tencent Cloud products within the same region access each other over the private network by default, with no traffic fees incurred. For more information on how to identify private network access, see Overview > Private Network Access.
Free of charge
CDN origin-pull traffic
When users utilize COS as the origin for CDN/EdgeOne, the back-to-origin traffic generated from transferring data from COS to Tencent Cloud CDN/EdgeOne edge nodes.
Pay-as-you-go: CDN origin-pull traffic (GB) * unit price per GB
Cross-region replication traffic
Traffic generated by replicating objects from a bucket in one region to a bucket in another region.Note: Replicating objects across buckets in the same region will not incur traffic fees. The traffic fees will vary by source bucket region.
Pay-as-you-go: Cross-region replication traffic (GB) * unit price per GB
Global acceleration traffic
When you enable the global acceleration feature, the traffic generated from data transfers through the acceleration domain, including public network global acceleration traffic and private network global acceleration traffic.
This traffic consists of upstream acceleration traffic and downstream acceleration traffic:
Upstream acceleration traffic is the traffic generated by uploading data to COS at an acceleration endpoint. Upstream acceleration traffic fees will be incurred if you upload files at a global acceleration endpoint and data goes through the private network acceleration linkage.
Downstream acceleration traffic is the traffic generated by viewing or downloading COS data at an acceleration endpoint. Downstream acceleration traffic fees will be incurred if you download files at a global acceleration endpoint and data goes through the private network acceleration linkage.
Pay-as-you-go: Global acceleration traffic (GB) * unit price per GB
Note:
If data is downloaded using a global acceleration domain, both global acceleration outbound traffic fees and public outbound traffic fees will be incurred. If a global acceleration domain is used as the origin domain for CDN/EdgeOne back-to-origin, both global acceleration outbound traffic fees and CDN back-to-origin traffic fees will be incurred.
Billing Restrictions
ARCHIVED data cannot be read or downloaded until it is restored to the STANDARD storage class. Therefore, traffic generated from these requests is counted in the STANDARD storage class.
Public network downstream traffic is generated when the data is returned to COS through origin-pull by using a third-party CDN service.
1. Public network downstream traffic is generated when a user downloads objects through object links or browses objects through a static website endpoint.
Cross-region replication traffic is generated when you replicate data from a bucket in one region to a bucket in another region using APIs or the cross-region replication feature. The traffic fees will vary depending on the region where the source bucket resides.
For INTELLIGENT TIERING, traffic fees are subject to those of the storage class after object movement.
Billing Modes and Calculation Formulas for Traffic Fees
Billing Mode
Applicable Billable Items
Calculation Method
Pay-as-you-go
Public network Downstream Traffic Fees
CDN origin-pull traffic fees
Cross-region replication traffic fees
Global acceleration traffic fees
Daily billing cycle
Traffic fees = unit price per GB * daily accumulated traffic
Traffic Resource Packages (Prepaid)
Public network Downstream Traffic Fees
Global Acceleration Traffic Fees
Traffic packages are classified according to the type of traffic as follows:
Public network downstream traffic package: Used to deduct public network downstream traffic.
Global acceleration traffic package: Used to deduct global acceleration traffic. According to the data transfer acceleration direction, it is divided into the following types:
Chinese mainland only: It can deduct global acceleration traffic (both upstream and downstream traffic) fees for the transfer direction 'Chinese mainland - Chinese mainland', excluding traffic in the financial cloud regions.
Hong Kong (China) and overseas: It can deduct global acceleration traffic (both upstream and downstream traffic) fees for transfer directions 'Chinese mainland - Hong Kong (China) and overseas', 'Hong Kong (China) and overseas - Hong Kong (China) and overseas', and 'Hong Kong (China) and overseas - Chinese mainland'.
Within the validity period of the traffic package, the traffic generated in each cycle (including the purchase day) can be deducted from the specifications of the resource package. The insufficient part will be billed on a pay-as-you-go basis.
After you enable the CDN acceleration domain name, data downloads and access through it will incur fees:
Billable Item
Description
CDN origin-pull traffic
When users utilize COS as the origin for CDN/EdgeOne, the back-to-origin traffic generated from transferring data from COS to Tencent Cloud CDN/EdgeOne edge nodes.
CDN Downstream Traffic
When users use COS as the origin for CDN/EdgeOne, the traffic generated when data is downloaded from CDN/EdgeOne edge nodes to the user's local or client is considered CDN/EdgeOne outbound traffic.
COS request fees
When users utilize COS as the origin server for CDN/EdgeOne, data transmission from COS to Tencent Cloud CDN/EdgeOne edge nodes generates COS request counts. Request fees are calculated based on the number of request instructions sent to COS.
CDN origin-pull traffic fees and COS request fees: These fees are charged by COS. For details, see Pricing | Cloud Object Storage.
CI Public Network Outbound Traffic Fees for COS Domain Names with CI Data Processing Parameters
When users access a COS domain name with CI data processing parameters, the following fees will be incurred:
Note:
The processing parameters of Cloud Infinite (CI) enable operations such as image processing, audio/video processing, document preview, and file processing by appending data processing parameters to the suffix of a COS file URL.
Taking image scaling as an example, the following sample can scale the width and height of the image sample.jpeg in the COS bucket to 50% of the original by carrying CI data processing parameters:
Original image: http://examples-1251000004.cos.ap-shanghai.myqcloud.com/sample.jpeg
Traffic generated by accessing links that use a COS domain name and carry CI processing parameters.
Traffic generated by directly accessing links via a CI domain name.
CI - CDN origin-pull traffic
After a link that uses a COS domain name and carries CI processing parameters is accessed, the back-to-origin traffic generated from transferring data from CI to Tencent Cloud CDN edge nodes.
COS request fee
When users utilize COS as the origin for CDN/EdgeOne and data is transferred from COS to Tencent Cloud CDN/EdgeOne edge nodes, COS request counts are generated, and the request fees are billed by the number of requests sent to COS.
Note:
CI public network outbound traffic and CI-CDN origin-pull traffic fees are charged by CI. For details, see the CI Traffic FeesPublic Network Outbound Traffic section.
Sample: STANDARD storage fees + STANDARD request fees + Public downstream traffic fees
Assume that on November 1, 2020, user A uploaded a 10 GB object to a bucket residing in Guangzhou region in the STANDARD storage class, generating 100 requests. On the same day, User A spent 3.6 USD to purchase a 10 GB public network downstream traffic package valid for one month and applicable across the Chinese mainland. On November 2 and November 3, user A downloaded the object of -10 GB to the local file system over the public network with CDN disabled, generating 100 requests daily. Apart from these operations, user A did not perform any other operations. As storage usage, request, and traffic fees are settled daily, then:
Standard storage usage fee: settled daily starting from November 2, 2020.
STANDARD request fees: Settled on November 2, 3, and 4, 2020.
Traffic fees: Settled on November 3 and 4, 2020.
Fees analysis:
Pay-as-you-go:
STANDARD storage usage fees = 0.024 USD/GB/month / 30 * 10 GB * 30 days = 0.24 USD
Public downstream traffic fees = 0.1 USD/GB x 10 GB x 2 = 2 USD
Traffic package: The 10 GB of public network downstream traffic generated on November 2, 2020 was deducted by the traffic package when the bill was issued on November 3, 2020. The 10 GB of public network downstream traffic generated on November 3, 2020 was billed on a pay-as-you-go basis when the bill was issued on November 4, 2020, as the traffic package quota had been exhausted. The cost was calculated as 0.1 USD/GB x 10 GB = 1 USD.
In summary, the total bill for user A in November is calculated as follows: 0.24 + 0.00006 + 0.51 + 1 =1.75006 USD.
Sample: STANDARD storage usage fees + STANDARD request fees + Global acceleration traffic fees + Public downstream traffic fees
Assume that user B has a bucket in the Singapore region, which stores 100 GB of STANDARD data, and another bucket in the Tokyo region, which stores 200 GB of STANDARD data. On November 1, 2020, user B downloaded 10 GB and 20 GB of data from the Singapore and Tokyo buckets respectively in the Tokyo office area in Japan via the global acceleration domain name. These two download operations generated a total of 600,000 read/write requests. No other operations were performed during the rest of the time. As fees incurred on the previous day are settled daily, then:
Standard storage usage fee: settled daily starting from November 2, 2020.
Request fee: settled on November 2, 2020.
Global acceleration downstream traffic fee: settled on November 2, 2020.
Public network downstream traffic fee: settled on November 2, 2020.
The fee analysis is as follows:
STANDARD storage usage fees: billed on a pay-as-you-go basis, calculated as 0.017 USD/GB/month / 30 * (100 GB + 200 GB) * 30 days = 5.1 USD.
Global acceleration downstream traffic fee: 0.18 USD/GB x 10 GB = 1.8 USD. User B downloaded data from the Tokyo bucket in the Tokyo office area. This is an intra-region transfer, which does not use the acceleration link and therefore incurs no global acceleration downstream traffic fee.
Public network downstream traffic fee: 0.072 USD/GB x 10 GB + 0.07 USD/GB x 20 GB = 2.12 USD.
Based on the analysis above, the total bill for user B in November is calculated as follows: 5.1 + 0.12 + 1.8 + 2.12 = 9.14 USD.
