No. Currently, CDN does not support billing by the number of requests.
For more information, please see the note on arrears in the billing description document.
No. The traffic generated by origin-pull from CDN to COS is billed by COS instead of CDN. For more information, please see COS as Origin Server.
After the CDN domain name acceleration service is disabled, if the domain name is still configured with CNAME, a 404 status code will be returned for requests resolved to the node and a small amount of traffic will be consumed. The Console will record this traffic data for your reference. Corresponding logs will also be generated. However, since your domain name has been disabled, you will not be billed for this traffic consumption and log packets. We recommend you modify the origin-pull resolution first before disabling the acceleration service.
If you find the selected billing method unsuitable for your actual business conditions (for more information on how to select the right billing mode for you, please see Choosing a Billing Plan), you can change it by following the steps below:
No. CDN does not charge for this type of traffic.
In CDN billing, 1 Gbps = 1000 Mbps, 1 Mbps = 1000 Kbps, and 1 Kbps = 1000 bps.
Yes. CDN only charges for downstream, not upstream traffic.
Since CDN essentially accelerates content delivery, it cannot identify whether a request is malicious. Therefore, it cannot process malicious requests and avoid generating traffic during the attack. In order to avoid excessive losses caused by malicious requests, after your domain name is attacked and the bandwidth exceeds 10 Gbps, you can submit a ticket to lodge an appeal, and Tencent Cloud CDN will refund the charges for the portion of the bandwidth exceeding 10 Gbps.