tencent cloud

Cloud Object Storage

DocumentaçãoCloud Object StorageBillingBillable ItemsRequest Fees

Request Fees

Download
Modo Foco
Tamanho da Fonte
Última atualização: 2026-08-19 15:49:20
Traduzido por IA
The number of requests includes user requests and backend requests generated after users configure the feature. The request fee is calculated based on the number of request commands sent to COS (Cloud Object Storage).
User requests: These refer to operations such as data upload, download, query, and deletion performed by users via API, SDK, or the console. These operations are implemented by sending request commands to Tencent Cloud COS.
Backend requests: These refer to the number of requests for operations such as deleting STANDARD replicas after lifecycle transitions or archive retrieval expiration, reading from and writing to cross-region replication, and delivering inventory reports.

Fees are categorized into read request fees, write request fees, INTELLIGENT_TIERING object monitoring fees, and retrieval request fees based on storage type and usage scenario.
Note:
For more information on storage classes, see Overview.
The billing unit for read requests, write requests, and request packages is ten thousand requests, and the unit conversion factor is 10,000. For example: 10,000 STANDARD write requests = 10,000 requests; a 100,000 STANDARD request package, after conversion, is 100,000 STANDARD requests.

Request Fee Billing Items

Read and Write Request Fees

Description
Applicable Storage Class
Applicable Billing Mode
Number of read and write requests refers to the number of request commands sent. Its cost is calculated based on the total daily number of requests.
Requests are charged regardless of success or failure.
The request fee is billed in units of ten thousand requests as the minimum counting unit.
If the number of daily requests is less than 10,000, the fee is calculated based on the actual number of requests.
If the fee for the daily number of requests does not reach the minimum deduction threshold, the request fee bill will be CNY 0. For details, see the FAQ document.
Data of archive classes (such as ARCHIVE and DEEP_ARCHIVE) cannot be read or downloaded directly.
Uploading data of archive classes generates upload requests. These requests are billed as read and write requests for the corresponding archive class (such as ARCHIVE or DEEP_ARCHIVE). For details, see Product Pricing.
If you directly access data of an archive class that has not been restored (or thawed), an error request is generated. This request is billed as a read or write request for the corresponding archive class (such as ARCHIVE or DEEP_ARCHIVE). For details, see Product Pricing.
If you restore (or thaw) data of the ARCHIVE class, a STANDARD class copy is created and billed as STANDARD storage. If you access this copy, read and write requests are generated and billed as STANDARD read and write requests.
If you restore (or thaw) data of the MAZ_ARCHIVE class, an MAZ_STANDARD class copy is created and billed as MAZ_STANDARD storage. If you access this copy, read and write requests are generated and billed as MAZ_STANDARD read and write requests.
If you restore (or thaw) data of the DEEP_ARCHIVE class, a STANDARD class copy is created and billed as STANDARD storage. If you access this copy, read and write requests are generated and billed as DEEP_ARCHIVE read and write requests.
All Storage Class
Pay-as-you-go
STANDARD request package
STANDARD_IA request package

Note: Request packages are not applicable to INTELLIGENT_TIERING.

INTELLIGENT_TIERING Object Monitoring Fees

Description
Applicable Storage Class
Applicable Billing Mode
After the INTELLIGENT_TIERING configuration is enabled for a bucket, the system monitors it in real time. If you upload data of the INTELLIGENT_TIERING storage class to that bucket, this fee is incurred. This fee is calculated based on the number of objects that are 64 KB or larger.
INTELLIGENT_TIERING
MAZ_INTELLIGENT_TIERING
Pay-as-you-go

Retrieval Request Fees

Description
Applicable Storage Class
Applicable Billing Mode
When data stored in DEEP_ARCHIVE is restored (thawed), COS charges a retrieval request fee based on the number of restoration requests sent.

Categorized into the following fees based on the user-selectable retrieval mode.
DEEP_ARCHIVE Standard Retrieval Request Fee
DEEP_ARCHIVE Batch Retrieval Request Fee
Deep archive storage
Pay-as-you-go

Billing Method and Calculation for Request Fees

Billing Mode
Applicable Billable Items
Calculation Method
Pay-as-you-go
Read Request Fee
Write Request Fee
INTELLIGENT_TIERING Object Monitoring Fee
DEEP_ARCHIVE Retrieval Request Fee
Daily billing cycle
Read Request Fee = Daily Price per 10,000 Requests × Daily Cumulative Number of Requests / -10,000.
Object Monitoring Fee = Monthly Price per 10,000 Monitored Objects / 30 × Daily Cumulative Number of Objects / 10,000
= Daily price per 10,000 monitored objects × Daily cumulative number of objects / 10000.
Retrieval Request Fee = Daily Price per 10,000 Requests × Daily Cumulative number of requests / 10,000.
Read/write request resource package (prepaid)
STANDARD Read Request Fee
STANDARD Write Request Fee
STANDARD_IA Read Request Fee
STANDARD_IA Write Request Fee
READ/WRITE request package: categorized into the following types based on STANDARD and STANDARD_IA storage classes.
STANDARD Request Package: Used to offset fees incurred by STANDARD read and write requests.
STANDARD_IA Request Package: Used to offset fees incurred by STANDARD_IA read and write requests.

Note: Request packages are not applicable to INTELLIGENT_TIERING.
Attention:
Billing Days: For monthly billing, fees are calculated based on 30 days per month. For daily billing, fees are calculated based on the actual number of days in each month. If you use the service for an entire month, fees for January are calculated based on 31 days, for February based on 28 (or 29) days, and for April based on 30 days.

Request Pricing

Attention:
Effective September 30, 2021, the list price for DEEP_ARCHIVE read and write requests has been reduced. For details, see the documentation.
The price for public cloud services in the Chinese mainland, Hong Kong (China), and overseas regions is reduced to USD 0.07 per 10,000 requests.
This price will take effect in the bill dated October -1, 2021 (that is, the bill for September 2021).
Specific prices are subject to the real-time list prices published by the Tencent Cloud Pricing Center. Please go to the Product Pricing Center to view the latest unit prices and cost estimates. Details are as follows:
Pay-as-you-go Pricing: see Product Pricing - Pay-as-you-go Pricing.
Resource Package Pricing: see Product Pricing - Resource Package Pricing.

Billing Examples

Note:
Prices in the example below are for reference only. For the actual prices, please see COS Pricing.
The number of requests is counted regardless of whether the requests succeed or fail.

Case: STANDARD Storage Usage Fees + STANDARD Request Fees

Assume that on April 1, 2024, User A uploaded 10 GB of data in the STANDARD storage class to a COS bucket in the Guangzhou region. On the same day, User A spent USD 0.01 to purchase a 100,000-request STANDARD request package valid for one month and applicable across the Chinese mainland. Also on that day, User A called the GET Bucket API repeatedly to query the object list, totaling 100,000 times. No other operations were performed during the remaining time. Fees incurred on the previous day are settled daily. Then:
STANDARD storage usage fees: settled daily starting from April 2, 2024.
STANDARD request fees: settled on April 2, 2024.
The fee analysis is as follows:
STANDARD storage usage fees: billed on a pay-as-you-go basis, 0.024 USD/GB/month / 30 * 10 GB * 30 days = 0.24 USD.
STANDARD request fee: Use a STANDARD request package to offset 100,000 requests within the validity period (April 1, 2024, to April -30, 2024). Total: 0.01 USD.
Based on the analysis above, the total bill for user A in April is 0.24 + 0.01 = 0.25 USD.
Anterior: Storage Usage FeesPróximo: Data Retrieval Fees

Ajuda e Suporte

Esta página foi útil?

comentários