Request Fees
Terakhir diperbarui:2025-10-28 10:44:52
Billable requests include user requests and backend requests generated after you configure a feature. The request fees are billed by the number of requests sent to COS.
User requests: Include requests sent to COS to upload, download, query, delete, and perform other operations through APIs, SDKs, or the console.
Backend requests: Include requests to delete STANDARD copies (when the restored archived objects expired or after a lifecycle transition), read/write data for cross-bucket replication, and deliver inventory reports.
Based on different storage types and usage scenarios, costs are categorized into read requests, write requests, INTELLIGENT_TIERING object monitoring fees, and retrieval request fees.
Note:
For more information on storage classes, see Overview.
The billing unit of the request billing item and request packages is 10,000 requests.For example,A standard storage request package with a quota of 100,000 requests can deduct fees of 100,000 standard storage requests.
Request Cost Billing Items
Read/Write Request Fees
Billable Item Description | Applicable Storage Class | Applicable Billing Mode |
Fees incurred by the daily total number of sent read/write requests. Both successful and failed requests are billed. The minimum number of requests for billing is 10,000. If the daily number of requests is less than 10,000, fees will be calculated based on the actual number of requests. If the daily request fees don't reach the minimum deduction value, the request fees will be 0 on the bill. For more information, see Billing. For archive types (such as ARCHIVE and DEEP_ARCHIVE), data cannot be directly read or downloaded. Uploading archive type data will generate upload requests. These requests are billed as read or write requests for archive types (such as archive storage, deep archive storage). For details, see Product Pricing. If you directly access unrecovered (or unfrozen) archive type data, error requests will occur. These requests are billed as read or write requests for archive types (such as archive storage, deep archive storage). For details, see Product Pricing. If you recover (or unfreeze) archive storage type data, a standard storage replica will be created and billed as standard storage. Accessing this replica will generate read and write requests, which will be billed as standard storage read and write requests. If you recover (or unfreeze) MAZ_DEEP_ARCHIVE data, a MAZ_STANDARD replica will be created and billed as MAZ_STANDARD. Accessing this replica will generate read and write requests, which will be billed as MAZ_STANDARD read and write requests. If you restore an object in DEEP_ARCHIVE, a copy will be generated in the STANDARD storage class, which will be billed at the STANDARD storage usage price. If you access the copy, a read/write request will be generated, which will be billed at the DEEP_ARCHIVE read/write request price. | All | Pay-as-you-go STANDARD request package STANDARD_IA request package NOTE: request packages are not available for INTELLIGENT_TIERING storage |
Intelligent Tiering Storage Object Monitoring Fees
Billable Item Description | Applicable Storage Class | Applicable Billing Mode |
After the INTELLIGENT_TIERING storage configuration is enabled for a bucket, the system will monitor it in real time. If INTELLIGENT_TIERING objects are uploaded into this bucket, relevant fees will be incurred. These fees are calculated based on the number of objects which are greater than or equal to 64 KB. | INTELLIGENT_TIERING MAZ_INTELLIGENT_TIERING | Pay-as-you-go |
Data Retrieval Request Fees
Billable Item Description | Applicable Storage Class | Applicable Billing Mode |
When restoring (thawing) data from ARCHIVE or DEEP_ARCHIVE storage, COS will charge retrieval request fees based on the number of restore requests sent. Fees are divided into the following categories based on the user-selectable retrieval modes: DEEP_ARCHIVE standard retrieval request fees DEEP_ARCHIVE bulk retrieval request fee | DEEP_ARCHIVE | Pay-as-you-go |
Billing Modes and Calculation Formulas for Request Fees
Billing Mode | Applicable Billable Item | Calculation Formula |
Pay-as-You-Go | Read Request Fees Write Request Fees INTELLIGENT_TIERING Object Monitoring Fees DEEP_ARCHIVE Retrieval Request Fees | Daily Settlement Read request fees = Daily price per ten thousand requests × Daily cumulative number of requests/10000 Object monitoring fees = Monthly price per ten thousand objects for monitoring/30 × Daily cumulative number of objects/10000
= Daily price per ten thousand objects for monitoring × Daily cumulative number of objects/10000 Retrieval request fees = Daily price per ten thousand requests × Daily cumulative number of requests/10000 |
Read/Write Request Resource Package (Prepaid) | STANDARD Read Request Fees STANDARD Write Request Fees STANDARD_IA Read Request Fees STANDARD_IA Write Request Fees | Read/write request resource package: According to the STANDARD and STANDARD_IA types, it is divided into the following categories STANDARD request package: Used to detuct the fees incurred by STANDARD read/write requests STANDARD_IA request package: Used to deduct the fees incurred by STANDARD_IA read/write requests Note: The request package is not applicable to INTELLIGENT_TIERING. |
Note:
Billing days: If settled monthly, billing will be based on 30 days per month. If settled daily, billing will be based on the actual number of days in each month. If you use the service for an entire month, January will be billed for 31 days, February for 28 (or 29) days, and April for 30 days.
Request Pricing
Note:
Starting from September 30, 2021, published prices for COS DEEP_ARCHIVE read/write requests will be adjusted. For details, refer to the Documentation.
The price for public cloud services in Chinese mainland, Hong Kong (China), and overseas regions will be reduced to 0.07 USD/10,000 times.
This price will take effect in the billing statement of October 01, 2021 (that is, September 2021 billing statement).
Billing Examples
Note:
Prices in the following examples are for reference only. For the actual prices, see Pricing | Cloud Object Storage.
Both successful and failed requests are billed.
Example: STANDARD storage usage fees + STANDARD request fees
Assuming that on April 1, 2024, user A uploaded 10 GB of STANDARD data to a COS bucket in the Guangzhou region, and on the same day spent 0.01 USD to purchase a STANDARD request package of 100,000 times, universally valid in the Chinese mainland for a validity period of 1 month. On that day, the user repeatedly called the GET Bucket API to query the object list, making a total of 100,000 requests. With no other operations performed for the rest of the time and settling daily charges incurred on the previous day, then:
STANDARD storage usage fees: Settled daily starting from April 2, 2024.
STANDARD request fees: Settled on April 2, 2024.
Fees analysis:
STANDARD storage usage fees: Pay-as-you-go, 0.024 USD/GB/Month/30 x 10 GB x 30 days = 0.24 USD
STANDARD request fees: Using the STANDARD request package, 100,000 requests are deducted within the validity period (April 1, 2024, to April 30, 2024). Total: 0.01 USD.
In summary, based on the analysis above, the total bill for user A in April is 0.24 + 0.01 = 0.25 USD.
Apakah halaman ini membantu?
Anda juga dapat Menghubungi Penjualan atau Mengirimkan Tiket untuk meminta bantuan.
Ya
Tidak
masukan