tencent cloud

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.

Billable Item	Applicable Storage Class	Description	Applicable Billing Mode
Public network downstream traffic	MAZ_STANDARD MAZ_STANDARD_IA MAZ_INTELLIGENT TIERING INTELLIGENT TIERING STANDARD STANDARD_IA ARCHIVE DEEP ARCHIVE	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		Origin-pull traffic generated by data transfer from COS to the CDN edge node when COS is used as the CDN origin.	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		Traffic generated by data transfer at an acceleration endpoint through the global acceleration feature. 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 the global acceleration domain name is used to download data, global acceleration downstream traffic fees and public network downstream traffic fees will be incurred. If the global acceleration domain name is used as the CDN origin domain name for origin-pull, global acceleration downstream traffic fees and CDN origin-pull traffic fees will be incurred.

Billing Restrictions

1. 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.
2. Public network downstream traffic is generated when the data is returned to COS through origin-pull by using a third-party CDN service.
3. Public network downstream traffic is generated when a user downloads objects through object links or browses objects through a static website endpoint.
4. 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.
5. For INTELLIGENT TIERING, traffic fees are subject to those of the storage class after object movement.

Traffic Generated by Using COS as CDN Origin

After you enable the CDN acceleration domain name, data downloads and access through it will incur fees:

Billable Item	Description
CDN origin-pull traffic	Origin-pull traffic generated by data transfer from COS to the CDN edge node when COS is used as the CDN origin.
CDN traffic	CDN outbound traffic generated by data download from the CDN edge node to the local system or client when COS is used as a CDN origin.
COS request	COS requests generated by data transfer from COS to the CDN edge node when COS is used as the CDN origin. Request fees are billed by the number of requests sent to COS.

Note：

CDN traffic fees are charged by CDN. For detailed pricing, see Pricing | Content Delivery Network.

Billing Mode and Calculation Formulas

Billing Mode	Applicable Billable Items	Calculation Formula
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 Pricing

For the unit prices of traffic, see Pricing | Cloud Object Storage.

Billing Examples

Note：

Prices in the example below are for reference only. For the actual prices, see Pricing | Cloud Object Storage.

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 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 fees: 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:

• STANDARD storage usage fees = 0.024 USD/GB/month / 30 * 10 GB * 30 days = 0.24 USD
• STANDARD request fees = 0.002 USD/10,000 requests * 100 requests / 10,000 * 3 = 0.00006 USD
• Public downstream traffic fees = 0.1 USD/GB x 10 GB x 2 = 2 USD

In summary, the total bill for user A in November is calculated as follows: 0.24 + 0.00006 + 2 = 2.24006 USD.