Help Center> Content Delivery Network> Billing> High Bill Risk Warning
Updated on 2024-05-15 GMT+08:00
View PDF

High Bill Risk Warning

If your site is attacked or has malicious traffic coming, there may be sudden traffic spikes that result in a bill higher than your normal expenditures. This part describes the potential risks and solutions.

Risks

  • Attacks and malicious traffic generate excessive bandwidth usage, and you need to pay significantly more than you usually do.
  • The bill fee may exceed your account balance, resulting in an outstanding amount. For details about how to handle the outstanding amount, see Expiration and Overdue Payment.

Solutions

You can use the protection and notification functions by referring to the suggestions in Table 1 to reduce the risks caused by burst bandwidth.

Table 1 Solutions

Solution

Description

Access control

You can use access control functions such as referer validation, IP address access control lists (ACLs), and token authentication for domain names to avoid unnecessary traffic or bandwidth consumption. For details, see Access Control.

Association between CDN and Cloud Eye

You can view basic data (such as traffic, bandwidth, and status codes) of domain names under your account in real time and set alarms. When the monitoring metrics trigger the alarm conditions, alarms are sent by email or SMS, helping you detect potential risks in a timely manner. For details, see Cloud Eye Monitoring.

Usage cap

When a usage cap is set, CDN will disable the acceleration service for your domain names when the access bandwidth reaches the threshold you specify to avoid excessive fee.

Request rate limiting

If request rate limiting is enabled, when a single request reaches the rate limit, the access speed of the user is limited to reduce the risk of burst bandwidth.

To ensure the integrity of statistics and accuracy of bills, a bill is usually generated after a billing cycle ends. For details, see Basic Service Billing. Therefore, the bill time is later than the time when resources are consumed, so you cannot check the real-time resource consumption through bills. This is due to the distributed architecture of CDN PoPs. This method is widely used.