Product billing FAQ
Frequently asked questions about Web Application Firewall (WAF) 3.0 billing, including upgrade costs, pay-as-you-go activation, refund policies, and instance pricing.
Why am I still receiving bills after disabling WAF?
After you disable a pay-as-you-go instance, you may still receive bills within 1 to 3 days. Common causes are as follows:
Bill delay: Pay-as-you-go fees are settled daily. The fees incurred on the day of disabling are included in the last bill generated on the next day, and no new bills are generated from the third day onward. First, check whether the billing cycle of the bill covers usage before the instance was disabled.
Instance fee: The instance is billed at 0.5 SeCU per hour (about CNY 0.6 per day) as soon as it is activated, regardless of whether assets are added or traffic is generated. Instance fees incurred before disabling are included in the last bill.
WAF-enabled ALB instance: If you added protection through ALB, ALB separately charges for the WAF-enabled ALB instance. After you disable WAF, also check on the ALB side that the related instance or feature has been released.
Log Service: WAF logs are metered and billed independently by SLS. Disabling WAF does not automatically stop log billing on the SLS side, nor does it delete logs that have already been written. Stop log collection or delete the logstore on the SLS side as needed.
Other pay-as-you-go items: After a SeCU resource plan expires, fees are automatically deducted from your account balance. Bot Management and API Security are billed by Credit after they are upgraded to the Agentic edition. Check these items separately.
If new bills are still generated more than 3 days after disabling, submit a ticket and include the billing cycle and the instance ID.
How do I troubleshoot a bill amount that differs from my expectation?
Check the following items in order:
Confirm the billing method: Pay-as-you-go bills are generated daily. Subscription bills are generated only once at purchase, upgrade, or renewal. The daily bill of a subscription instance usually contains only the overage fee for burstable QPS.
Check the instance fee: A pay-as-you-go instance incurs 0.5 SeCU per hour once activated, even if no assets are added.
Check protection feature fees: After assets are added, the default template of Web core protection rules is billed at 10 SeCU per hour. IP blacklist and custom rules are billed by the number of rules, including rules in the disabled state.
Check access feature fees: Check the tier that the number of CNAME record domains falls into, and whether features such as dedicated IP, non-standard port, intelligent load balancing, and IPv6 are enabled.
Check request processing fees: Check whether peak QPS exceeds 1,000 and whether the number of requests exceeds 5,000 per hour. Attack requests are also counted in the request count.
Check independently billed items: Check whether you added protection through ALB (WAF-enabled ALB instances are billed separately by ALB), whether you use SLS logs (billed independently by SLS), and whether Bot Management or API Security has been upgraded to the Agentic edition (billed by Credit).
Check the resource plan: Check whether the SeCU resource plan is depleted or has expired. After the plan is used up or expires, fees are automatically deducted from your account balance.
To view the specific configuration corresponding to each billable item, see View bills. For the complete billing rules of each billable item, see Pay-as-you-go billing.
How do charges change after upgrading from WAF 2.0 to WAF 3.0?
The upgrade is free, but your charges may change after you upgrade to WAF 3.0. For pricing details of subscription and pay-as-you-go instances, see Subscription billing and Pay-as-you-go billing.
Subscription
WAF 3.0 introduces a Basic edition suitable for users with low traffic.
Billing is simplified:
Traffic is now measured only by QPS, not bps. Elastic capacity is available on a pay-as-you-go basis to prevent service disruptions from QPS overages.
WAF no longer distinguishes between primary and other domains for billing. Instead, additional domains use tiered pricing, where the unit price decreases as you add more domains.
Hybrid Cloud Protection is available in more editions.
After a WAF 2.0 instance is migrated to WAF 3.0, its billing method and edition remain unchanged. For information about billing changes after migration, see Changes in fees for subscription instances.
Pay-as-you-go
This billing method uses the security capacity unit (SeCU) to simplify billing. SeCU resource plans feature tiered pricing, where the price decreases as usage increases.
WAF 3.0 supports hourly billing. Charges automatically cease when you disable a feature or delete its configuration, requiring no manual deprovisioning.
Does using WAF and ESA (Edge Security Acceleration) together cause conflicts? How do I deploy them?
The two services do not conflict and are often deployed together. ESA focuses on global acceleration, static content caching, and DDoS protection, while WAF focuses on application-layer security such as SQL injection and XSS prevention.
ESA includes a built-in WAF feature that differs from the standalone WAF described here. Choose the appropriate option based on your needs.
Billing difference: The WAF protection feature of ESA is deeply integrated. The costs are included under ESA billing. The WAF described in this document is an independent cloud product that requires separate activation and is billed according to its own Billing methods.
Feature difference: The built-in WAF feature of ESA is primarily adapted for edge security acceleration scenarios and meets common website protection needs. The WAF product described in this document is more comprehensive. It not only covers all capabilities of ESA WAF but also provides protection rules that cover a full range of business scenarios.
How to check whether pay-as-you-go WAF is activated?
Follow these steps:
-
Log on to the Web Application Firewall 3.0 console. From the top menu bar, select the resource group and region (Chinese Mainland or Outside Chinese Mainland) for the WAF instance.
- Important
The WAF instances for the Chinese Mainland and Outside Chinese Mainland are separate. We recommend that you switch between regions to check each instance separately.
Check the left-side navigation pane:
Activated: The left-side navigation pane appears.
Not activated: The left-side navigation pane does not appear.
In the left-side navigation pane, click Overview. If you have not added any assets to WAF, a welcome page appears. Click Go to Console on the right. Then, check the current WAF edition in the Edition Information section.
To disable WAF and stop billing, see Disable WAF. After you complete the operation, a final bill for usage up to that day is generated on the following day. No further charges will be incurred starting on the third day.
Are refunds available for pay-as-you-go WAF bills that have already been incurred?
After a WAF 3.0 pay-as-you-go instance is activated, billing continues even if no assets are added: the instance incurs an instance fee of 0.5 SeCU per hour (about CNY 0.6 per day). Refunds are not available for charges already incurred. If you no longer need the instance, disable it promptly to stop further billing. For the complete pay-as-you-go billing rules, see Billing overview.
Can I add a Simple Application Server to WAF?
Yes. WAF CNAME record mode allows you to add any internet-accessible domain name. This mode supports multi-cloud and cross-account scenarios without restrictions on specific cloud products.
How to query the billing type (pay-as-you-go or subscription) of a WAF instance?
-
Log on to the Web Application Firewall 3.0 console. From the top menu bar, select the resource group and region (Chinese Mainland or Outside Chinese Mainland) for the WAF instance.
In the left-side navigation pane, click Overview. If you have not added any assets to WAF, a welcome page appears. Click Go to Console on the right. Then, check the current WAF edition in the Edition Information section.
If you have multiple assets that require WAF protection, how many WAF instances should you purchase?
WAF provides two region options: Chinese Mainland and Outside Chinese Mainland. Only one instance can be purchased per region.
Role of the region: The region determines the physical location of the WAF protection nodes, which affects access latency and data compliance.
Recommendations:
If your origin server is in the Chinese Mainland, select the Chinese Mainland WAF instance.
If your origin server is outside the Chinese mainland, select the Outside Chinese Mainland WAF instance.
What does the RegionId parameter in WAF OpenAPI represent? What is its relationship with the actual protection node region?
The RegionId parameter in WAF OpenAPI represents only the management region of the WAF instance, not the physical protection node that handles traffic. Traffic scheduling works as follows:
Fixed values for RegionId: When you call an API operation, the RegionId parameter must be set to a specific value that corresponds to your WAF instance:
Chinese Mainland instance: Use
cn-hangzhou.Outside Chinese Mainland instance: Use
ap-southeast-1.
Distribution and scheduling of physical protection nodes: WAF has 12 protection node clusters deployed worldwide. The system automatically routes traffic to the lowest-latency node based on your origin server IP address. The node resource pools are divided as follows:
Chinese Mainland resource pool (4 nodes): Beijing, Hangzhou, Shenzhen, and Chengdu. When you purchase a Chinese Mainland WAF instance, the system automatically selects one of these four nodes.
Outside Chinese Mainland resource pool (8 nodes): China (Hong Kong), Singapore, Malaysia, US West, Germany, Indonesia, Dubai, and Japan. When you purchase an Outside Chinese Mainland WAF instance, the system automatically selects one of these eight nodes.
After adding resources to WAF, will other ECS instances in the account that have not been added be billed or affected?
No. WAF 3.0 charges apply only to instances or domain names that are added for protection. Other ECS instances in your account that are not added to WAF are not affected and do not incur WAF-related charges.
Does the cost increase as more cloud product instances (such as ECS or CLB instances) are added to WAF?
No. Adding multiple cloud product instances (such as ECS or CLB) does not incur cumulative per-instance charges. WAF 3.0 pay-as-you-go billing is based on total traffic volume, not the number of instances. For details, see Pay-as-you-go billing.