Billing Items
Billing Description
When using EdgeSec, you will be billed for the service edition (mandatory), requests or service traffic protected (mandatory), and expansion package (optional) you use. For details, see EdgeSec billing items.
Billing Item |
Description |
Billing Mode |
Formula |
|
---|---|---|---|---|
Edition (mandatory) |
You are charged by service edition (enterprise edition). |
Yearly/Monthly billing |
Service edition x Required duration |
|
Service traffic |
Security acceleration traffic |
You are billed by the traffic used per hour. You can also buy traffic packages to deduct traffic used. You are billed at tiered traffic prices. The billing cycle is one calendar month.
NOTE:
The actual network traffic is 7% to 15% higher than the traffic measured at the application layer as there is certain amount of traffic generated by TCP/IP packet headers and TCP retransmission. Therefore, the billable traffic will be typically 10% higher than the statistics displayed on the console. |
Pay-per-use billing |
Actual traffic (GB) x Tiered traffic price
There are five tiers:
|
Service requests |
Number of HTTP/HTTPS requests that are protected by EdgeSec |
Pay-per-use billing |
Actual number of requests (per 10,000 requests) x Unit price |
|
Rule expansion package (optional) |
Billed based on how many packages you purchased |
Yearly/Monthly billing |
Unit price of a package x Required duration |
|
Domain expansion package (optional) |
Billed based on how many packages you purchased |
Yearly/Monthly billing |
Unit price of a package x Required duration |
|
Dynamic acceleration service request |
Number of CDN dynamic acceleration requests. |
Pay-per-use billing |
Actual number of requests (per 10,000 requests) x Unit price Bills are settled on a monthly basis. |
Billing Rules
- If a domain name is added to Edge Security Acceleration (ESA), the incremental service fees (including acceleration and security functions) generated by the domain name are charged by ESA only. CDN stops the billing for the domain name.
- If a domain name is removed from ESA, the domain name is still charged by ESA before 24:00 on the day it is deleted and then charged by CDN after that time.
- For pay-per-use ESA incremental services (billed by traffic and number of requests), the minimum billing cycle is 5 minutes. For example, if a domain name is added to ESA at 10:03, the domain name is charged by CDN before 10:05, and the domain name is charged by ESA from 10:05 to 24:00.
- The traffic volume displayed on the statistical analysis page is calculated based on application-layer logs. The actually network traffic (TCP/IP packet header traffic and TCP retransmission traffic) is 7% to 15% higher than the traffic volume displayed. So, you will find the billed traffic is 10% higher than the statistical traffic.
Impacts of Expiration
EdgeSec resource lifecycle shows the statuses a yearly/monthly EdgeSec can go through throughout its lifecycle. After a service is purchased, it enters the valid period and runs normally during this period. If the service is not renewed after it expires, before being deleted, it first enters a grace period and then a retention period.
Expiration Reminder
From the 7th day before a yearly/monthly EdgeSec subscription expires, the system will send an expiration reminder to the creator of the account by email, SMS, and internal message.
Impacts of Expiration
If your yearly/monthly EdgeSec resource expires and is not renewed, the resource enters the grace periods. During the grace period, you can use the service.
If you do not renew the yearly/monthly EdgeSec resource within the grace period, the resource enters the retention period and the resource status changes to Frozen. You cannot perform any operation on the yearly/monthly resource during the retention period.
If the yearly/monthly EdgeSec resource is not renewed by the time the retention period ends, the resource will be released and data cannot be restored.
For details about renewal, see Overview.
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