Fees for Out-of-plan Resource Usage (Pay-as-You-Go)
포커스 모드
폰트 크기
The overage charges for various EdgeOne packages are structured as follows:
Billable Item | Package Types and Pricing | |||
| Individual Edition | Basic Edition | Standard Edition | Enterprise Edition |
Security acceleration traffic | | | Depending on the access method, the following charges may incur: Domain Access: L7 (Application Layer) Traffic Price IP address + Port Access: L4 (Transport Layer TCP/UDP Applications) Traffic Price | |
Security acceleration request | | | | |
Security Acceleration Traffic
L7 (Application Layer) Traffic Pricing
Pricing models for different plan editions vary:
Personal Edition/Basic Edition/Standard Edition: Hourly billing with monthly progressive tiered pricing, where tiered usage is calculated per billing cycle (actual month).
Enterprise Edition varies based on the selected billing model:
Prepaid Monthly: Hourly billing with monthly progressive tiered pricing, where tiered usage is calculated per billing cycle (actual month).
Postpaid Monthly: Monthly billing with monthly tiered attainment, adopting attained tier pricing, where tiered usage is calculated per billing cycle (calendar month).
Tiered pricing is as follows:
Traffic Tier (USD/GB) | Chinese mainland CN | North America NA | Europe EU | Asia-Pacific Region 1 AS1 | Asia-Pacific Zone 2 AS2 | Asia-Pacific Zone 3 AS3 | Middle East MidEast | Africa AF | South America SA |
0 - 2 TB (exclusive) | 0.0443 | 0.0756 | 0.0756 | 0.1097 | 0.1185 | 0.1229 | 0.1286 | 0.1286 | 0.1286 |
2 - 10 TB (exclusive) | 0.0422 | 0.0634 | 0.0634 | 0.0977 | 0.1098 | 0.1170 | 0.1183 | 0.1183 | 0.1183 |
10 - 50 TB (exclusive) | 0.0399 | 0.056 | 0.0560 | 0.0930 | 0.1030 | 0.1093 | 0.1075 | 0.1075 | 0.1075 |
50 - 100 TB (exclusive) | 0.0375 | 0.0486 | 0.0486 | 0.0882 | 0.0961 | 0.1017 | 0.0967 | 0.0967 | 0.0967 |
100 - 500 TB (exclusive) | 0.0352 | 0.0412 | 0.0412 | 0.0834 | 0.0892 | 0.0940 | 0.0859 | 0.0859 | 0.0859 |
500 - 1000 TB (exclusive) | 0.0329 | 0.0339 | 0.0339 | 0.0787 | 0.0823 | 0.0863 | 0.0751 | 0.0751 | 0.0751 |
≥ 1000 TB | 0.0306 | 0.0265 | 0.0265 | 0.0739 | 0.0754 | 0.0786 | 0.0643 | 0.0643 | 0.0643 |
Billing Region Note (subject to the region where the EdgeOne node serving the actual user's client is located):
billing region | Coverage Region |
Chinese mainland | Chinese mainland |
North America | United States, Canada |
Europe | United Kingdom, Germany, Italy, Ireland, France, Netherlands |
Asia-Pacific Zone 1 | Hong Kong (China), Macao (China), Vietnam, Singapore, Thailand, Pakistan, Cambodia |
Asia-Pacific Zone 2 | Taiwan (China), Japan, South Korea, Malaysia, Indonesia |
Asia-Pacific Zone 3 | Philippines, India, Australia, Nepal, Other Asia-Pacific countries and regions |
Middle East | Saudi Arabia, United Arab Emirates, Türkiye, Qatar, Bahrain, Iraq |
Africa | South Africa, Egypt |
South America | Brazil, Mexico, Colombia, Argentina |
Note
1. EdgeOne only charges for "clean traffic". For the definition of "clean traffic", see: About "Clean Traffic" Billing Description.
2. For domains that do not have Smart Acceleration enabled, only the application-layer downstream traffic from EdgeOne nodes to user clients is counted. This is displayed as "Content Acceleration Traffic" on the Console Plan Usage page.
For domains without Smart Acceleration enabled, if the traffic model meets the conditions where upstream traffic exceeds downstream traffic and upstream bandwidth surpasses 1 Gbps, the application-layer upstream traffic from EdgeOne nodes to user clients will be counted.
3. For domains that have Smart Acceleration enabled, the sum of application-layer upstream and downstream traffic between EdgeOne nodes and user clients is counted. This is displayed as "Smart Acceleration Traffic" on the Console Plan Usage page.
4. HTTPS request-generated SSL handshake traffic will be counted toward L7 (application layer) traffic;
5. In EdgeOne billing rules, 1 TB = 1,000 GB = 1,000,000 MB = 1,000,000,000 KB = 1,000,000,000,000 Byte.
Example 1:
If a user subscribes to the Standard Edition at 23:00 on January 1, and consumes 3 TB, 4 TB, 5 TB, and 6 TB of traffic in the Chinese mainland region during 23:00-24:00 on January 1, 00:00-01:00, 01:00-02:00, and 02:00-03:00 on January 2 respectively (with no consumption in regions outside the Chinese mainland), the 3 TB of Chinese mainland traffic generated during 23:00-24:00 on January 1 is deducted from the plan’s included traffic. Postpaid traffic begins accruing from 00:00 on January 2. In the figure below, the gray area represents the actual billing tiers. Postpaid hourly billing adopts a monthly progressive tiered pricing model, where consumed traffic accumulates across tiers and is billed at corresponding tier rates. The user generated a total of 15 TB of traffic during 00:00-03:00 on January 2, with 2 TB falling into the 0-2 TB tier, 8 TB into the 2-10 TB tier, and 5 TB into the 10-50 TB tier. Therefore, the overage charges for January 2 are calculated as follows:
The actual cost incurred from 00:00 - 01:00 on January 2 is: 2 * 1000 * 0.0443 + 2 * 1000 * 0.0422 = 173 USD;
The actual cost incurred from 01:00 - 02:00 on January 2 is: 5 * 1000 * 0.0422 = 211 USD;
The actual cost incurred from 02:00 - 03:00 on January 2 is: 1 * 1000 * 0.0422 + 5 * 1000 * 0.0399 = 241.7 USD.
By analogy, the postpaid cost for each hour's traffic is calculated. Starting at 23:00 on February 1, a new billing cycle begins, and the cumulative tiered usage will be reset to zero.
Example 2:
If a user subscribes to the Enterprise Edition at 23:00 on January 5, and consumes a total of 15 TB of L7 (application layer) traffic by 23:59 on January 31, all traffic is distributed in the Chinese mainland region. Assuming that all 15 TB of traffic is counted as overage charges beyond the plan, then the total cost incurred in January is: 15 * 1000 * 0.0399 = 598.5 USD. Starting at 00:00 on February 1, a new billing cycle begins, and the cumulative tiered usage will be reset to zero.
L4 (Transport Layer TCP/UDP Applications) Traffic Pricing
If you use the IP address + port method to access in EdgeOne Console > Layer-4 Proxy, the traffic generated by layer-4 proxy instances will be counted toward L4 (transport layer TCP/UDP application) traffic.
Enterprise Edition varies based on the selected billing model:
Prepaid Monthly: Hourly billing with monthly progressive tiered pricing, where tiered usage is calculated per billing cycle (actual month).
Postpaid Monthly: Monthly billing with monthly tiered attainment, adopting attained tier pricing, where tiered usage is calculated per billing cycle (calendar month).
Tiered pricing is as follows:
Traffic Tier (USD/GB) | Chinese mainland CN | North America NA | Europe EU | Asia-Pacific Region 1 AS1 | Asia-Pacific Zone 2 AS2 | Asia-Pacific Zone 3 AS3 | MidEast | Africa AF | South America SA |
0 - 2 TB (exclusive) | 0.1705 | 0.2657 | 0.2657 | 0.2514 | 0.4561 | 0.4730 | 0.4950 | 0.4950 | 0.4950 |
2 - 10 TB (exclusive) | 0.1624 | 0.2229 | 0.2229 | 0.2241 | 0.4229 | 0.4505 | 0.4554 | 0.4554 | 0.4554 |
10 - 50 TB (exclusive) | 0.1534 | 0.1969 | 0.1969 | 0.2132 | 0.3964 | 0.4209 | 0.4138 | 0.4138 | 0.4138 |
50 - 100 TB (exclusive) | 0.1445 | 0.1709 | 0.1709 | 0.2022 | 0.3698 | 0.3914 | 0.3722 | 0.3722 | 0.3722 |
100 - 500 TB (exclusive) | 0.1355 | 0.1449 | 0.1449 | 0.1913 | 0.3433 | 0.3618 | 0.3307 | 0.3307 | 0.3307 |
500 - 1000 TB (exclusive) | 0.1266 | 0.1190 | 0.1190 | 0.1804 | 0.3168 | 0.3323 | 0.2891 | 0.2891 | 0.2891 |
≥ 1000 TB | 0.1176 | 0.0930 | 0.0930 | 0.1694 | 0.2902 | 0.3027 | 0.2475 | 0.2475 | 0.2475 |
Note
1. IP address + port access is an exclusive benefit of the Enterprise Edition. If you have related requirements, Contact Us;
2. Only business traffic after protection and scrubbing is billed; traffic generated by attacks is not billed;
3. L4 (transport layer) traffic statistics refer to the sum of TCP/UDP uplink and downlink traffic between EdgeOne nodes and user clients, shown as "Layer-4 Acceleration Traffic" on the plan usage page in the console.
Example 1: The Enterprise Edition adopts hourly billing with monthly progressive tiered pricing
If a user subscribes to the Enterprise Edition at 23:00 on January 1, adopting the prepaid monthly billing mode, and consumes 3 TB, 4 TB, 5 TB, and 6 TB of traffic in the Chinese mainland region during 23:00-24:00 on January 1, 00:00-01:00, 01:00-02:00, and 02:00-03:00 on January 2 respectively (with no consumption in regions outside the Chinese mainland), the 3 TB of Chinese mainland traffic generated during 23:00-24:00 on January 1 is deducted from the included traffic in the plan. Postpaid traffic begins accruing from 00:00 on January 2. In the figure below, the gray area represents the actual billing tiers. The postpaid hourly billing adopts a monthly progressive tiered pricing model, where the traffic generated by the user accumulates across different tiers and is billed at corresponding tier rates. The user generated a total of 15 TB of traffic during 00:00-03:00 on January 2, with 2 TB falling into the 0-2 TB tier, 8 TB into the 2-10 TB tier, and 5 TB into the 10-50 TB tier. Therefore, the overage charges for January 2 are calculated as follows:
The actual cost incurred from 00:00 - 01:00 on January 2 is: 2 * 1000 * 0.1705 + 2 * 1000 * 0.1624 = 665.8 USD;
The actual cost incurred from 01:00 - 02:00 on January 2 is: 5 * 1000 * 0.1624 = 812 USD;
The actual cost incurred from 02:00 - 03:00 on January 2 is: 1 * 1000 * 0.1624 + 5 * 1000 * 0.1534 = 929.4 USD.
By analogy, the postpaid cost for each hour's traffic is calculated. Starting at 23:00 on February 1, a new billing cycle begins, and the cumulative tiered usage will be reset to zero.
Example 2: The Enterprise Edition adopts monthly billing with monthly tiered pricing
If a user subscribes to the Enterprise Edition at 23:00 on January 5, adopting the postpaid monthly billing mode, and consumes a total of 15 TB of L4 (transport layer TCP/UDP application) traffic by 23:59 on January 31, all traffic is distributed in the Chinese mainland region. Assuming that all 15 TB of traffic is counted as overage charges beyond the plan, then the total cost incurred in January is: 15 * 1000 * 1.07 = 16,050 CNY. Starting at 00:00 on February 1, a new billing cycle begins, and the cumulative tiered usage will be reset to zero.
Security Acceleration Request
HTTP/HTTPS request price
Personal/Basic/Standard Editions: Hourly settlement with linear pricing postpaid.
Enterprise Edition varies based on the selected billing model:
Prepaid monthly: Hourly settlement with linear pricing postpaid.
Postpaid monthly: Monthly settlement with linear pricing postpaid.
Specific prices are as follows:
Billable Item | Price (USD/10,000 requests) |
HTTP/HTTPS request | 0.0071 |
Note:
1. Only clean requests after they are scrubbed are billed; attack requests are not billed.
2. Number of HTTP/HTTPS requests counts all application-layer requests from user clients to EdgeOne node servers, regardless of protocol or whether they are static or dynamic requests. This is displayed as "Security acceleration request" on the Console Plan Usage page.
3. For domains with Smart Acceleration enabled, an additional Smart Acceleration Request Fee will be charged.
피드백