Bills
You can view CDN bills on the Billing page in Billing Center. For details, see Bills.
Precautions
- CDN does not support bill generation by domain name, enterprise project, or tag. You can use cost splitting to view the amortized costs.
- Traffic statistics on the CDN console are the logged traffic statistics. However, the billable traffic is 10% higher than the logged statistics because TCP/IP packet headers and TCP retransmissions also consume traffic.
- If you have purchased a traffic package, you cannot view the package bill by package ID. You can query the bill by package name. For details about how to obtain the package name, see Resource Packages.
Bill Reporting Period
The usage of pay-per-use resources is reported to the billing system at a fixed interval for settlement. Pay-per-use products can be settled by hour, day, or month based on the usage type. For details about the fee deduction rules, see Bill Run for Pay-per-Use Resources.
- CDN traffic is billed by hour. Traffic used in an hour will be settled 4 hours later.
- CDN peak bandwidth is billed by day. The system settles the bandwidth at about 20:00 (GMT+08:00) the next day.
- In the average daily peak bandwidth and 95th percentile bandwidth billing options, the system settles the bandwidth at about 20:00 (GMT+08:00) on the first day of the next month.
Example: If traffic-based billing is used, the fee generated from 08:00 to 09:00 is deducted at about 13:00. On the Billing Center > Billing > Expenditure Details page, Expenditure Time indicates the time when a pay-per-use product is used.
Viewing Bills of a Specific Resource
- CDN is billed by account. Bills cannot be queried by resource (acceleration domain name). For details about how to view the cost of each acceleration domain name, see Cost Management.
- A resource ID in a CDN bill is in the format of UUID + Billing region + Billing option. The UUID is generated by account. The resource ID is used only for billing and cannot be queried on the CDN console.
- For details about the mapping between resource IDs and usage types in bills, see Mapping Between Usage Types and Resource IDs in CDN Bills.
Checking CDN Usage Based on Bills
To check whether the CDN usage is consistent with that in bills, log in to the CDN console, choose
in the navigation pane, and check the billing option on the right. The following table lists whether a billing option supports CDN usage check and the check methods.
Billing Option |
Usage Type |
Usage Check Method |
---|---|---|
Traffic |
|
|
Peak bandwidth fee |
|
|
95th percentile bandwidth |
|
Usage cannot be checked by enterprise project, domain name, or tag. For details about how to split costs by enterprise project, domain name, or tag, see Enabling Cost Splitting. |
Average daily peak bandwidth |
|
- Checking the total usage
Example: Assume that you changed the billing option from peak bandwidth to traffic on May 12, 2023. The change took effect at 00:00 on May 13, 2023. Then, you changed the billing option from traffic to peak bandwidth on May 30, 2023 and the change took effect at 00:00 on May 31, 2023. Therefore, you were billed by traffic from May 13, 2023 to May 30, 2023. The service area of domain names under this account is Chinese mainland. To check bills, perform the following operations:
- Log in to the CDN console, choose Create Export Task, and set the parameters.
- Task Name: user-defined
- Export Mode: All
- Period: May 13, 2023 – May 30, 2023
- Data: Statistics
- Granularity: 1 hour
- Metric: Traffic
- Region: Chinese mainland
, click - Click OK. After the task is complete, download the Excel file.
- Calculate the sum of all usage values to obtain the total CDN usage.
- Go to the Billing Center. In the navigation pane, choose . Select a billing cycle, search for CDN fees, and click on the right to download the bill.
- In the exported bill, filter Usage Type by traffic.
Total usage = Usage + Package Usage = 5,252,506,434,878
- The value obtained in step 5 (5,252,506,434,878 bytes) slightly differs from that obtained in step 3 (5,252,506,754,351 bytes). CDN traffic is charged in GB, and the conversion results of the two values are both 4891.778 GB, which does not affect the charged fee.
The exported bills may be the logged traffic statistics. However, the billable traffic is 10% higher than the logged statistics because TCP/IP packet headers and TCP retransmissions also consume traffic. Therefore, the usage exported from the CDN console must be multiplied by 1.1.
- Log in to the CDN console, choose Create Export Task, and set the parameters.
Mapping Between Usage Types and Resource IDs in CDN Bills
Specifications |
Usage Type |
Resource ID |
Conversion Rule |
---|---|---|---|
Chinese mainland |
Number of requests |
{UUID}-wsa-Request |
- |
Traffic |
{UUID} |
1,024 |
|
Peak bandwidth in the Chinese mainland |
{UUID} |
1,000 |
|
95th percentile bandwidth in the Chinese mainland |
{UUID} |
1,000 |
|
Average daily peak bandwidth in the Chinese mainland |
{UUID} |
1,000 |
|
Outside the Chinese mainland |
Number of requests outside the Chinese mainland |
{UUID}-wsa-Request-ov |
- |
Traffic outside the Chinese mainland |
{UUID}OverseaFlux |
1,024 |
|
Peak bandwidth outside the Chinese mainland |
{UUID}OverseaBandwidth |
1,000 |
|
95th percentile bandwidth outside the Chinese mainland |
{UUID}OverseaBandwidth |
1,000 |
|
Average daily peak bandwidth outside the Chinese mainland |
{UUID}OverseaBandwidth |
1,000 |
|
Region-based billing outside the Chinese mainland |
Bandwidth in other Asia Pacific regions |
{UUID}OverseaAsiapacificBandwidth |
1,000 |
Bandwidth in Hong Kong (China), Macao (China), Taiwan (China), Japan, and South Korea |
{UUID}OverseaEastasiaBandwidth |
1,000 |
|
Bandwidth in Europe |
{UUID}OverseaEuropeBandwidth |
1,000 |
|
Bandwidth in India |
{UUID}OverseaIndiaBandwidth |
1,000 |
|
Bandwidth in the Middle East and Africa |
{UUID}OverseaMeAfricaBandwidth |
1,000 |
|
Bandwidth in North America |
{UUID}OverseaNorthAmericaBandwidth |
1,000 |
|
Bandwidth in Oceania |
{UUID}OverseaOceaniaBandwidth |
1,000 |
|
Bandwidth in South America |
{UUID}OverseaSouthAmericaBandwidth |
1,000 |
|
Traffic in other Asia Pacific regions |
{UUID}OverseaAsiapacificFlux |
1,024 |
|
Traffic in Hong Kong (China), Macao (China), Taiwan (China), Japan, and South Korea |
{UUID}OverseaEastasiaFlux |
1,024 |
|
Traffic in Europe |
{UUID}OverseaEuropeFlux |
1,024 |
|
Traffic in India |
{UUID}OverseaIndiaFlux |
1,024 |
|
Traffic in the Middle East and Africa |
{UUID}OverseaMeAfricaFlux |
1,024 |
|
Traffic in North America |
{UUID}OverseaNorthAmericaFlux |
1,024 |
|
Traffic in Oceania |
{UUID}OverseaOceaniaFlux |
1,024 |
|
Traffic in South America |
{UUID}OverseaSouthAmericaFlux |
1,024 |
- UUIDs are generated by account. Different resource IDs of the same account share the same UUID.
- Only customers who have enabled region-based billing outside the Chinese mainland have IDs of region-based resources outside the Chinese mainland.
- The bandwidth and traffic in the Chinese mainland use the same resource ID. Therefore, the billing option cannot be identified based on the resource ID.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot