COS is pay-as-you-go. For more information, see Billing Overview.
COS billable items include storage usage, requests, data retrievals, traffic, and management features. For more information, see Pricing | Cloud Object Storage.
No. COS can be billed only on a pay-as-you-go (postpaid) basis.
Request fees are calculated based on the number of requests sent to COS, including user requests and backend requests generated after you configure a feature. For more information, see Request Fees.
On September 30, 2021, the published prices of COS were reduced as follows:
The reduction in the unit price of STANDARD_IA storage usage from 0.018 USD/GB/month to 0.015 USD/GB/month will apply to certain regions, including Mumbai, Seoul, Bangkok, Silicon Valley, Jakarta, and São Paulo. The reduction has taken effect on July 1, 2022.
COS offers a limited free tier to all new users (both individual and enterprise users) to deduct the fees incurred by data stored in the STANDARD storage class. For more information, see Free Tier.
Yes. The free tier is applicable to public cloud regions (including those outside the Chinese mainland). For more information, see Regions and Access Endpoints.
The free tier offered by COS can be used to deduct only STANDARD storage usage but not other billable items, such as STANDARD_IA storage usage, ARCHIVE storage usage, requests, and traffic. For more information, see Billable Items.
The following are some of the possible reasons why your account has overdue payments if your free tier hasn't expired:
No. The free tier is applicable only to STANDARD storage usage but not other billable items such as STANDARD_IA/ARCHIVE storage usage, requests, and traffic.
INTELLIGENT TIERING is an independent storage class and incurs INTELLIGENT TIERING storage usage fees, which cannot be deducted from the free tier for the STANDARD storage class. For more information, see Free Tier.
No. COS and CDN are different products. The CDN origin-pull traffic generated by the use of CDN is billed by COS on a pay-as-you-go basis, and the generated CDN traffic is billed by CDN. For more information on the differences between these two types of traffic, see Traffic Fees.
COS sends notifications for new feature launch, product change, expiration, repossession, and alarms.
You can customize the recipients of COS notifications by setting Message Recipient in Subscription Management in Message Center.
Public network downstream traffic is traffic generated by data transfer from COS to the client over the Internet. Traffic generated by downloading an object directly through an object link or by browsing an object through a static website access node is public network downstream traffic. For more information on billing for such traffic, see Billable Items and Product Pricing.
The traffic (private or public network traffic) generated by accessing COS is subject to the use case, and only access to COS from a Tencent Cloud product in the same region will be over the private network by default, with no public network downstream traffic fees incurred. For more information on how to identify private network access, see Overview > Private Network Access.
Public network downstream traffic is the traffic generated by data transfer from COS to the client over the internet. Downloading a file stored in COS in the COS console, accessing or downloading an object through a tool, object address, or custom domain name, and previewing an object in a browser will generate public network downstream traffic. For more information, see Overview.
Accessing COS over the private network will incur storage usage fees and request fees but not traffic fees. For more information, see Billable Items.
After COS is connected to CDN, the fees incurred by COS and CDN will be billed separately.
It may be because you are still using the COS origin domain name formatted as <bucketname-appid>.cos.<region>.myqcloud.com
to access COS files after you enabled CDN acceleration. We recommend that you use the CDN acceleration domain name instead, which only generates CDN origin-pull traffic.
CDN origin-pull is to pull data from COS to the cache node by CDN when a file not cached on a CDN edge node is accessed at a CDN domain name.
Note:CDN origin-pull will incur origin-pull traffic fees. For more information, see Traffic Fees.
CDN origin-pull traffic is the traffic generated by data transfer from COS to a Tencent Cloud CDN edge node. After CDN acceleration is enabled, traffic generated by browsing or downloading COS data on the client at a CDN acceleration domain name is CDN origin-pull traffic. For billing details, see Billing Overview and Pricing | Cloud Object Storage.
CDN origin-pull traffic is a billable item in COS. It is the origin-pull traffic generated by data transfer from COS to the CDN edge node when COS is used as the CDN origin.
CDN traffic is a billable item in CDN. It is the traffic generated by data transfer from a CDN edge node to the client.
When data transfer happens between COS and CVM from different regions, there are charges for both traffic and requests. When data is transferred in the same region, there are charges for requests, but not for traffic (free for data transfer over private network). For more information, see How to determine access over private network.
No. The upstream traffic generated by file uploads is free of charge.
Tencent Cloud products within the same region access each other over the private network by default, with no traffic fees incurred. For more information, see How to determine an access over private network.
You can view the fees incurred by the use of COS under your account in the Billing Center in the console. For more information, see Viewing and Downloading Bill. You can view bucket-level bill details by downloading the usage details in the Billing Center.
Log in to the Tencent Cloud console, select Billing Center > Bill Download Center, and download the target bill packages, PDF bills (L0), bill summary (L1), bills by instance (L2), and bill details (L3). For more information, see Bill Download Center.
APPID
together as the resource ID and using the bucket name as the instance name, i.e., generating bills by bucket. You can view the fees and usage of billable items by bucket.COS supports billing by bucket and cost allocation by tag.
Note:
After your account is added to the allowlist, billing by bucket will take effect only for new bills, while existing bills will remain unchanged. In addition, you cannot go back to the previous billing option.
You can determine this in two ways:
Below are the effects after billing by bucket is enabled:
(1) Bill by instance
(2) Bill details
(3) Bill details (L3)
Note: After the billing by bucket feature of COS is fully launched, on the Cost Allocation - Month sheet in the usage details, the bucket cost allocation information won't be displayed, while other information stays unchanged. For specific bucket fees, download the L2 or L3 bill.
The billing by bucket feature of COS was made available through an allowlist starting from October 28, 2022 as follows:
APPID
and Instance Name is a bucket name.Starting from February 1, 2023, the feature was made available to users in batches by UIN as follows:
Launch Date | Description | Bill Description |
---|---|---|
October 28, 2022 | Feature launch - through allowlist. | (1) Billing stayed unchanged for users not in the allowlist. (2) Billing by bucket was enabled for users in the allowlist. |
February 1, 2023 | Before full launch - allowed account verification. | (1) Billing stayed unchanged for users not in the allowlist. (2) Billing by bucket was enabled for users in the allowlist. |
February 6, 2023 | Batch 1 launch - for UINs ending in 9 | (1) Billing by bucket was enabled for users in the allowlist and with UINs ending in 9. (2) Billing stayed unchanged for other users. |
February 20, 2023 | Batch 2 launch - for UINs ending in 2 | (1) Billing by bucket was enabled for users in the allowlist and with UINs ending in 9 or 2. (2) Billing stayed unchanged for other users. |
March 7, 2023 | Batch 3 launch - for UINs ending in 3 | (1) Billing by bucket will be enabled for users in the allowlist and with UINs ending in 9, 2, or 3. (2) Billing will stay unchanged for other users. |
March 14, 2023 | Batch 4 launch - for UINs ending in 4 | (1) Billing by bucket will be enabled for users in the allowlist and with UINs ending in 9, 2, 3, or 4. (2) Billing will stay unchanged for other users. |
March 21, 2023 | Batch 5 launch - for UINs ending in 5 | (1) Billing by bucket will be enabled for users in the allowlist and with UINs ending in 9, 2, 3, 4, or 5. (2) Billing will stay unchanged for other users. |
Log in to the Tencent Cloud console, select Billing Center > Bill Overview, and view the billing statistical period of your account.
COS adopts the pay-as-you-go (postpaid) billing mode.
For more information on billing cycles, see Bill Management.
Starting from July 1, 2022, the settlement cycle of COS storage usage, request, and data retrieval fees was upgraded from monthly to daily to help you manage fees in a more refined manner. The upgrade was implemented on user accounts in batches and went through a two-month beta test. The release dates of different bill statistical periods are as listed below. For more information, see Daily Billing for COS Storage Usage, Request, and Data Retrieval and Bill Management.
Release Date | Release Note | Bill Description |
---|---|---|
July 1, 2022 | The first release for the first batch of accounts in beta test | (1) Resources were settled monthly before July 1, 2022. Fees incurred from 00:00 on June 1 to 23:59 on June 30 were deducted on July 1. The record was posted to the bill for July by deduction cycle and to the bill for June by billing cycle. (2) Resources were settled daily after July 1, 2022. Fees incurred from 00:00 to 23:59 on July 1 were deducted on July 2. The record was posted to the bill for July 2 by deduction cycle and to the bill for July 1 by billing cycle. |
August 1, 2022 | The second release for the second batch of accounts in beta test | (1) Resources were settled monthly before August 1, 2022. Fees incurred from 00:00 on July 1 to 23:59 on July 31 were deducted on August 1. The record was posted to the bill for August by deduction cycle and to the bill for July by billing cycle. (2) Resources were settled daily after August 1, 2022. Fees incurred from 00:00 to 23:59 on August 1 were deducted on August 2. The record was posted to the bill for August 2 by deduction cycle and to the bill for August 1 by billing cycle. |
September 1, 2022 | The third release for all accounts | (1) Resources were settled monthly before September 1, 2022. Fees incurred from 00:00 on August 1 to 23:59 on August 31 were deducted on September 1. The record was posted to the bill for September by deduction cycle and to the bill for August by billing cycle. (2) Resources were settled daily after September 1, 2022. Fees incurred from 00:00 to 23:59 on September 1 were deducted on September 2. The record was posted to the bill for September 2 by deduction cycle and to the bill for September 1 by billing cycle. |
Therefore, if the monthly usage remained the same, after monthly settlement was upgraded to daily settlement, the bill amount varied by billing statistical period and billable items as follows:
In the first month after the upgrade from monthly settlement to daily settlement, the storage fees increased. This was because two bills were generated for billing by deduction cycle. The first bill was the monthly bill for the last month, while the second bill was the daily bill for the current month. Therefore, the bill amount seemed to have increased, but no additional fees were deducted in fact, which was normal under the settlement and billing logic.
In the second month after the upgrade from monthly settlement to daily settlement, your bills were settled daily, and the bill amount "decreased" compared with that in the first month, which was also normal under the settlement and billing logic.
For example:
Your account is billed by deduction cycle and was upgraded from monthly settlement to daily settlement on September 1, 2022, and you downloaded the bill details (L3) of COS in the Billing Center on September 30.
Taking the COS STANDARD storage usage billable item as an example, the bills consisted of the monthly bill for August and daily bill for September as detailed below:
Therefore, if your monthly fees increased in the first month after the upgrade from monthly settlement to daily settlement and your bill was generated by deduction cycle, the increase was normal under the settlement and billing logic, and no additional fees were deducted in fact. If you have any questions, contact us for assistance.
Before the upgrade, COS' storage, requests, STANDARD_IA data retrievals, and ARCHIVE data retrievals are settled monthly, and their monthly settlement details are displayed in the transaction details, while DEEP ARCHIVE data retrievals, traffic, and management features are still settled daily, and their daily settlement details are still displayed in the transaction details. After the upgrade, all COS billable items are settled daily. For more information, see Billing Overview.
In addition, you can view the L3 bill to check whether the billable items are settled daily or monthly as instructed in Billing.
Activating COS is free of charge, and fees will be incurred only after you use it. For billing details, see Billing Overview.
If you upload multiple files in a total size of 1 GB to the STANDARD storage class after activating COS and then view and download them, STANDARD storage, write requests, public/private network upstream traffic, and public network downstream traffic (of about 1 GB) will be generated, and the bill generated on the next day will include the STANDARD storage, STANDARD write request, and public network downstream traffic fees. As the public/private network upstream traffic is free of charge, it will not be included in the bill.
When you upload a file to COS, the generated traffic is free of charge, but the generated write request will incur fees, and the storage usage fees will be calculated based on the file size. If you access or download the object over the public network, public network downstream traffic fees will be incurred. For billing details, see Billing Overview and Pricing | Cloud Object Storage.
If you no longer use the COS service, you need to delete all the buckets under your account. Double check whether all the buckets have been deleted. If fees are still incurred after all the buckets are deleted, they may be the daily fees incurred on the previous day. COS storage usage fees and request fees are billed daily, that is, a bill generated on the current day is for usage on the previous day. You can go to the transaction details page and click Details on the right of a billable item to view fee deduction details.
The details about the change from monthly settlement to daily settlement are as follows: Starting from July 1, 2022, the settlement cycle of COS storage usage, request, and data retrieval fees was upgraded from monthly to daily to help you manage fees in a more refined manner. The upgrade was implemented on user accounts in batches and went through a two-month beta test. The release dates of different bill statistical periods are as listed below. For more information, see Daily Billing for COS Storage Usage, Request, and Data Retrieval and Bills.
You can deactivate COS or stop its billing as follows:
Notes
The minimum data storage duration in STANDARD_IA storage class is 30 days.
Below are the specific rules:
For more information, see "STANDARD_IA storage usage fees" and "Billing Mode and Calculation Formula" in Storage Usage Fees.
The minimum data storage duration in ARCHIVE storage class is 90 days.
Below are the specific rules:
For more information, see "ARCHIVE storage usage fees" and "Billing Mode and Calculation Formula" in Storage Usage Fees.
The minimum data storage duration in DEEP ARCHIVE storage class is 180 days.
Below are the specific rules:
For more information, see "DEEP ARCHIVE storage usage fees" and "Billing Mode and Calculation Formula" in Storage Usage Fees.
Data retrieval fees are fees incurred by reading or downloading MAZ_STANDARD_IA/STANDARD_IA data or restoring ARCHIVE or DEEP ARCHIVE data to STANDARD. They are calculated based on the amount of retrieved data. The higher the amount, the higher the fees. If you don't have special storage needs, you can directly use STANDARD, which doesn't involve data retrieval fees.
Copying MAZ_STANDARD_IA/STANDARD_IA data will incur request fees and data retrieval fees and may also incur cross-region replication traffic fees if the destination and source files are in different regions.
For the calculation details of such fees, see Request Fees, Data Retrieval Fees, and Traffic Fees.
A copy generated by restoring ARCHIVE or DEEP ARCHIVE data is in the STANDARD storage class and will incur STANDARD storage usage fees.
The read/write requests are priced by storage class and billed based on the actual quantity, with a minimum billable quantity of 10,000. For more information, see Pricing | Cloud Object Storage and Request Fees.
If the number of requests does not reach the minimum value for fee deduction, the request fees will be zero.
Case study: If 23 STANDARD read requests for your data stored in the STANDARD storage class in a bucket in Beijing region were made in December 2021, the unit price of STANDARD read/write requests was 0.002 USD/10,000 requests, and your account wasn't entitled to any discount, then the STANDARD read request fees were 0.0023 * 0.002 = 0.0000046 USD. As fee deduction is accurate down to two decimal places, your request fees for the month were 0 USD.
Cause: As bills support eight decimal places at most, while fee deduction is accurate down to two decimal places, the system will automatically adjust the accuracy difference. For more information, see Bills.
After the COS service is suspended due to overdue payment, you cannot read or write data from or to COS, but you can top up your account. For more information, see Payment Overdue.
Your account will be automatically unblocked in 10 minutes after it is topped up. If your account is still displayed as blocked, the browser may have cached the historical page. In this case, we recommend you refresh the webpage or clear the browser cache first.
The document processing service is offered by CI, so its fees are also charged by CI. Fees will be incurred for every request; that is, fees will be deducted every time you refresh the URL. For more information, see Document Processing Fees.
When you migrate data from another cloud to Tencent Cloud COS, outbound traffic fees will be charged by your source cloud storage vendor. The write traffic generated by migration to Tencent Cloud is free of charge, but storage usage and request fees will be incurred. For COS billing details, see Billing Overview.
Public network downstream traffic fees and request fees may be incurred. If you enable CDN and access data through a CDN domain name, CDN traffic fees and CDN origin-pull traffic fees will also be incurred.
No. For more information, see Specifications and Limits.
Apakah halaman ini membantu?