Anti-DDoS Origin 2.0 (subscription) uses a combination of subscription and pay-as-you-go billing. This topic covers instance types, billing items, mitigation session accounting, bandwidth overage handling, and account management policies for overdue payments, expiration, and refunds.
Choose an instance type
Anti-DDoS Origin 2.0 (subscription) offers two instance types: Inclusive Edition for Small and Medium Enterprises and Enterprise Edition. Each type provides two protection modes: Insurance mode and Worry-free mode.
Use the following criteria to select an instance type:
Inclusive Edition for Small and Medium Enterprises: Assets are in a single region, fewer than 30 IP addresses need protection, and clean bandwidth does not exceed 1,000 Mbps.
Enterprise Edition: Assets span multiple regions, more than 30 IP addresses need protection, or the assets include both IPv4 and IPv6 addresses.
For assets deployed outside the Chinese mainland, purchase elastic IP addresses (EIPs) with Anti-DDoS (Enhanced) enabled or Anti-DDoS Pro (outside the Chinese mainland). If Anti-DDoS Origin 2.0 (subscription) is required for such assets, contact your pre-sales account manager. Before purchasing the Worry-free mode for the Inclusive Edition for Small and Medium Enterprises or the Insurance mode for the Enterprise Edition, also contact your pre-sales account manager.
Feature comparison
The following table compares all four configurations to help you select the right plan.
| Feature | Inclusive Edition SME — Insurance mode | Inclusive Edition SME — Worry-free mode | Enterprise Edition — Insurance mode | Enterprise Edition — Worry-free mode |
|---|---|---|---|---|
| Mitigation sessions | 2 sessions/month. After all sessions are consumed, only Anti-DDoS Basic mitigation capacity remains. See thresholds that trigger blackhole filtering in Anti-DDoS Basic. | Unlimited sessions | 2 sessions/month. After all sessions are consumed, only Anti-DDoS Basic mitigation capacity remains. See thresholds that trigger blackhole filtering in Anti-DDoS Basic. | Unlimited sessions |
| Mitigation capabilities | Varies by region. See Comparison of version mitigation capabilities. | Unlimited protection | Varies by region. See Comparison of version mitigation capabilities. | Unlimited protection |
| IP protocol support | IPv4 or IPv6 (one protocol per instance) | IPv4 or IPv6 (one protocol per instance) | IPv4 or IPv6 (one protocol per instance) | IPv4 and IPv6 (both protocols per instance) |
| Regions covered | 1 region | 1 region | All regions in the Chinese mainland | All regions in the Chinese mainland |
| Number of IPs | 1–29 | 1–29 | 30–2,000. For higher specifications, contact your account manager. | 30–2,000. For higher specifications, contact your account manager. |
| Clean bandwidth | 50 Mbps–1,000 Mbps | 50 Mbps–1,000 Mbps | Starts at 100 Mbps with unlimited scale-out | Starts at 100 Mbps with unlimited scale-out |
| Burstable clean bandwidth | Not supported | Not supported | Not supported | Supported. Total clean bandwidth = 5× baseline clean bandwidth. |
| SLS logs | Not supported | Not supported | Not supported | Supported |
| Multi-account management | Not supported | Not supported | Not supported | Supported |
Upgrade paths
The following table describes when and how to upgrade between configurations.
| Current configuration | Upgrade trigger | Target configuration |
|---|---|---|
| Inclusive Edition SME — Insurance mode | Need more than 2 mitigation sessions per month | Inclusive Edition SME — Worry-free mode |
| Inclusive Edition SME — Insurance mode | Need to protect assets in multiple regions | Enterprise Edition — Insurance mode or Worry-free mode |
| Inclusive Edition SME — Worry-free mode | Need to protect assets in multiple regions | Enterprise Edition — Worry-free mode |
| Enterprise Edition — Insurance mode | Need more than 2 mitigation sessions per month | Enterprise Edition — Worry-free mode |
Inclusive Edition SME — Worry-free mode and Enterprise Edition — Insurance mode are only available as upgrade targets, not as new purchases. To purchase a new instance in these configurations, contact your account manager.
Billing items
Total cost = Subscription fee (protection feature fee + bandwidth fee + IP quantity protection fee) + Pay-as-you-go fee (burstable clean bandwidth fee).
Subscription fees
Subscription fees cover three components.
Protection feature fee
This is the base fee for the instance's protection mode.
| Instance protection mode | Unit price (USD/month) |
|---|---|
| Inclusive Edition for Small and Medium Enterprises — Insurance mode | 1,950 |
| Enterprise Edition — Worry-free mode | 6,000 |
Bandwidth fee
| Instance protection mode | Unit price (USD/month/Mbps) |
|---|---|
| Inclusive Edition SME — Insurance mode and Enterprise Edition — Insurance mode | 5 |
| Inclusive Edition SME — Worry-free mode and Enterprise Edition — Worry-free mode | 10 |
IP quantity protection fee
The IP quantity protection fee uses tiered pricing based on the number of protected IP addresses.
Inclusive Edition for Small and Medium Enterprises (Insurance mode and Worry-free mode):
| Number of IPs | Unit price (USD/month/instance) |
|---|---|
| [0, 100] | 24 |
Enterprise Edition (Insurance mode and Worry-free mode):
| Number of IPs | Unit price (USD/month/instance) |
|---|---|
| [0, 30] | 0 |
| (30, 100] | 24 |
| (100, 300] | 19.2 |
| (300, 500] | 14.4 |
| (500, 700] | 12 |
| (700, 1,000] | 9.6 |
For IP counts above 1,000, contact us.
Example A: Enterprise Edition — Worry-free mode with 200 IPs
| IP range | Calculation | Monthly fee |
|---|---|---|
| [0, 30] (30 IPs) | 0 × 30 | USD 0 |
| (30, 100] (70 IPs) | 24 × 70 | USD 1,680 |
| (100, 300] (100 IPs) | 19.2 × 100 | USD 1,920 |
| Total | USD 3,600 |
Example B: Enterprise Edition — Worry-free mode with 500 IPs
| IP range | Calculation | Monthly fee |
|---|---|---|
| [0, 30] (30 IPs) | 0 × 30 | USD 0 |
| (30, 100] (70 IPs) | 24 × 70 | USD 1,680 |
| (100, 300] (200 IPs) | 19.2 × 200 | USD 3,840 |
| (300, 500] (200 IPs) | 14.4 × 200 | USD 2,880 |
| Total | USD 8,400 |
Pay-as-you-go: burstable clean bandwidth fee
Burstable clean bandwidth is a pay-as-you-go add-on available for Enterprise Edition instances. After enabling the Metering Method of 95th Percentile Burstable Clean Bandwidth, the instance's clean bandwidth increases by 4× the baseline, bringing the total to 5× the baseline clean bandwidth. For example, a 1 Gbps baseline becomes 5 Gbps total.
Traffic that peaks above the baseline is not rate-limited, but you are charged for the excess. Traffic that stays within the baseline incurs no additional fees. Query burstable clean bandwidth usage in the Billing Center.
Two billing modes are available:
| Billing mode | Unit price(USD/month/instance)USD 12.5/month/Mbps(USD/month/Mbps)(USD/month) | Cost formula |
|---|---|---|
| Daily 95th percentile | USD 1.79/day/Mbps | 95th percentile billing bandwidth × daily unit price |
| Monthly 95th percentile (recommended) | USD 12.5/month/Mbps | 95th percentile billing bandwidth × effective factor × monthly unit price |
Use monthly 95th percentile by default. Switch to daily 95th percentile only for short-term sales promotions or campaigns.
How the 95th percentile billing bandwidth is calculated
Daily 95th percentile:
Sample clean traffic peaks at 5-minute intervals within a calendar day. This generates 288 values per day.
Remove values recorded during DDoS attacks, then remove the top 5 values.
Take the maximum of the remaining values as the total traffic peak.
95th percentile billing bandwidth = min(total traffic peak, total clean bandwidth) − baseline clean bandwidth.
Monthly 95th percentile:
Daily bandwidth peak: Sample at 5-minute intervals (288 values/day). Remove attack values. Take the maximum of the remaining values.
Total traffic peak: Sort daily bandwidth peaks for the calendar month in descending order. Average the top 5 values.
Total clean bandwidth: Take the baseline clean bandwidth for the top 5 daily peak days. Multiply the highest value by 5.
Baseline clean bandwidth: The baseline clean bandwidth on the last day of the month when burstable clean bandwidth is enabled.
Effective factor = effective days ÷ total days in the month.
95th percentile billing bandwidth = min(total traffic peak, total clean bandwidth) − baseline clean bandwidth.
Example: Effective factor calculation
If you enable burstable clean bandwidth on July 15, 2024, and keep it enabled through July 31, the effective days are July 16–31 (16 days). The effective factor is 16 ÷ 31 ≈ 0.516.
Billing generation and settlement times
| Billing mode | Bill generation | Settlement |
|---|---|---|
| Daily 95th percentile | ~10:00 AM the next day (email and internal message) | ~4:00 PM the next day (fees deducted from account balance) |
| Monthly 95th percentile | ~10:00 AM on the 1st of the next month (email and internal message) | ~11:00 AM on the 3rd of the next month (fees deducted from account balance) |
Switching billing modes
Disable: Takes effect the next day. Can be disabled only once per month.
Switch between modes: Takes effect the next month. Can switch only once per month.
Estimate your clean bandwidth requirements
Before purchasing, estimate your 95th percentile bandwidth to select the right baseline clean bandwidth.
Sample inbound and outbound traffic at 5-minute intervals. For each interval, calculate the average inbound and outbound bandwidth and take the higher value as the bandwidth for that sample. At the end of the month, sort all sample values in descending order and remove the top 5%. The highest remaining value is your 95th percentile bandwidth — use it as your baseline clean bandwidth reference.
The following diagram illustrates billable bandwidth over a 30-day period.
Mitigation sessions
The system records a traffic data point every 5 seconds (12 per minute). When attack traffic exceeds the threshold N Gbps, the system starts accumulating attack duration (shown as X+Y in the figure below). One mitigation session is consumed for every 15 minutes of accumulated attack time (equivalent to 180 data points).

The red line represents the inbound traffic of an asset with a public IP address.
The attack threshold N differs by location:
Assets in the Chinese mainland: N = 20 Gbps
Assets outside the Chinese mainland: N = 10 Gbps
Example: A Chinese mainland asset experiences two attacks exceeding 20 Gbps — one lasting 10 minutes, another lasting 12 minutes (22 minutes total). The first session is consumed after the initial 15 minutes. The remaining 7 minutes carry over toward a second session. If additional attacks accumulate another 8 minutes in the same month, the second session is consumed.
To check remaining mitigation sessions, see Query remaining mitigation sessions for Inclusive Edition for Small and Medium Enterprises.
Bandwidth overage
Anti-DDoS Origin allows clean traffic to temporarily exceed the instance's clean bandwidth. When cumulative overage duration reaches the following milestones within a month, Alibaba Cloud sends an alert through your configured notification channels. Alerts are sent on the morning of T+1 day.
| Cumulative overage | Alert sent |
|---|---|
| 1 hour | Yes |
| 9 hours | Yes |
| 18 hours | Yes |
| 27 hours | Yes |
| 36 hours | Yes — Anti-DDoS Origin mitigation becomes invalid; only Anti-DDoS Basic capacity remains |
After the 36-hour overage alert, restore Anti-DDoS Origin mitigation using one of the following methods:
Method 1: Wait for automatic recovery at the start of the next month.
Method 2 (Enterprise instances only): Enable burstable clean bandwidth. Recovery is immediate. Total clean bandwidth becomes 5× the baseline.
Method 3: Upgrade the baseline clean bandwidth. Recovery is immediate.
If overage has already reached 36 hours before applying Method 2 or Method 3, mitigation is already invalid. If bandwidth overage occurs again in the same month after applying either method, mitigation is downgraded again after the T+1 overage alert. If overage has not yet reached 36 hours, the cumulative duration continues to count after applying Method 2 or Method 3 — if it later reaches 36 hours, mitigation is downgraded at that point.
View overage details in the Billing Center.
Overdue payments
An overdue payment occurs when your available balance — including cash, coupons, and vouchers — is insufficient to cover outstanding bills. Top up your account promptly to prevent service interruptions.
Instance expiration
| Time period | Effect on service | Effect on configuration |
|---|---|---|
| Within 7 days (inclusive) after expiration | Service stops immediately. Resume service by completing renewal. | Configuration is retained. |
| On the 8th day after expiration | Instance is released and cannot be recovered. | Configuration is permanently deleted. |
Refund policy
Refunds are not supported after purchasing an instance.
Query bills
Query bills in the Expenses and Costs console. For more information, see Monthly bill overview. For more information, see Monthly Bill Overview.