This topic describes the billing rules and pricing for public bandwidth when an Edge Node Service (ENS) instance accesses the internet.
Bandwidth pricing
Bandwidth prices vary by region. The following tables list the unit prices.
Prices in the Chinese mainland
Carrier | Area | Single-line daily peak bandwidth (USD/Mbps/day) | Single-line monthly 4th peak bandwidth (USD/Mbps/month) | Single-line monthly 95th percentile bandwidth (USD/Mbps/month) |
China Telecom, China Unicom | Beijing, Shanghai, and prefecture-level cities of Guangdong Province | 0.3077 | 7.6923 | 0.0714 |
Regional centers | 0.1538 | 3.8462 | 0.0357 | |
Other cities | 0.1231 | 3.0769 | 0.0286 | |
China Mobile | Beijing, Shanghai, and prefecture-level cities of Guangdong Province | 0.1846 | 4.6154 | 0.0429 |
Regional centers | 0.0923 | 2.3077 | 0.0214 | |
Cities | 0.0738 | 1.8462 | 0.0171 |
Regional centers refer to provincial capitals and municipalities directly under the central government, excluding Beijing, Shanghai, and all prefecture-level cities in Guangdong Province. This term also includes sub-provincial cities that are not provincial capitals, such as Dalian, Qingdao, Xiamen, and Ningbo.
Prices in other countries and regions
For more information about the edge node coverage for each billing region of Alibaba Cloud ENS, see Node distribution.
Region | Country/Region | Pay-by-traffic (USD/GB) | Pay-by-daily-peak-bandwidth (USD/Mbps/day) | Pay-by-monthly-95th-percentile-bandwidth (USD/Mbps/month) |
North America | United States | 0.0286 | 0.095 | 2.857 |
Europe | France, Germany, Switzerland, Netherlands | 0.0286 | 0.095 | 2.857 |
Asia-Pacific | Thailand, Philippines, Malaysia, Singapore, Japan, China (Hong Kong), Indonesia | 0.0543 | 0.181 | 5.429 |
Australia | 0.0729 | 0.243 | 7.286 | |
Macao (China) | 0.1421 | 0.474 | 14.214 | |
South Korea | 0.0814 | 0.271 | 8.143 | |
Middle East | Türkiye, UAE | 0.0629 | 0.210 | 6.286 |
Africa | Egypt, South Africa | 0.0629 | 0.210 | 6.286 |
Nigeria | 0.1400 | 0.467 | 14.000 | |
Central and South America | Brazil | 0.0500 | 0.167 | 5.000 |
Billing details
ENS instances can access the internet through a static public IP address of a network interface card, an Elastic IP Address (EIP), or an edge NAT Gateway. The bandwidth generated by each access method is measured and billed separately.
The Edge NAT Gateway feature is currently free of charge. Affected customers will be notified one month before billing starts.
Billing for static public IP bandwidth
When you create an ENS instance, you can choose to assign a public IP address to its network interface card. The system then automatically assigns a static public IP address to the instance for internet access. If you use a static public IP address, you are charged only for public bandwidth.
In pay-as-you-go mode, the peak inbound and outbound bandwidth values are upper limits and not guaranteed service commitments. The peak bandwidth may be limited when resource contention occurs.
Outbound bandwidth refers to the public bandwidth traffic that flows out of an ENS instance. Inbound bandwidth refers to the public bandwidth traffic that flows into an ENS instance. ENS measures the inbound and outbound bandwidth of all instances on each edge node every 5 minutes. The higher of the two values is used as a valid peak bandwidth data point.
The daily peak bandwidth, monthly 4th peak bandwidth, and monthly 95th percentile bandwidth billing methods are supported. For more information about the billing rules, see Public bandwidth billing rules.
Billing for EIP bandwidth
If an ENS instance is attached to an EIP, the instance can access the internet through the EIP. You are charged for the EIP configuration and the public bandwidth that the EIP uses.
Currently, EIPs under the same Alibaba Cloud account can use different billing methods. For example, if you purchase three EIPs, you can use the pay-by-traffic billing method for the first EIP and the monthly 95th percentile billing method for the other two. For billing purposes, ENS merges the bandwidth of EIPs that are under the same account, on the same edge node, and use the same billing method.
The inbound and outbound bandwidth of all EIPs on an edge node is measured. The higher of the two values is used as a valid peak bandwidth data point.
Starting from 00:00 on April 1, 2024, configuration fees apply to EIPs. The billing rules are as follows:
Category
Description
Billing method
Pay-as-you-go.
Billing cycle
Bills are generated on a calendar month basis.
Unit price
USD 14.3/month/instance.
Billing rules
The final fee is the sum of the configuration fees for all EIP instances in the current month.
Configuration fee for an EIP instance = Unit price × Validity factor.
Scenario 1: An instance is created on June 5, 2024, and released on June 25, 2024. The number of valid days in June 2024 is 21.
Scenario 2: An instance is created on June 5, 2024, and is used until the end of the month. The number of valid days in June 2024 is 26.
NoteValidity factor = Number of valid days / Total days in the month. For example, if June 2024 has 30 days and the number of valid days in the bill is 17, the validity factor is 17/30 = 0.56666667.
Number of valid days: The number of days from when an EIP instance is created to when it is released within a calendar month. If the instance is not released in the current month, the period ends on the last day of the month. For example:
Public bandwidth billing rules
A single billing cycle and billing method are used for all static public IP bandwidth under the same Alibaba Cloud account. This billing cycle also applies to other pay-as-you-go resources, such as instances and disks, under the same account. For example, if you select the monthly 95th percentile bandwidth billing method when you create your first instance, all existing and new static public IPs under your account are billed using the monthly 95th percentile method. Consequently, the monthly billing cycle also applies to all existing and new pay-as-you-go instances and disks under your account. For more information about billing methods, see Pay-as-you-go (user-level, deprecated).
Daily peak bandwidth
Item | Description |
Billing rules | The daily peak bandwidth is billed on a daily basis. The inbound and outbound bandwidth of all instances on each edge node is measured every 5 minutes. The higher of the two values is used as a valid peak bandwidth data point. This process generates 288 data points per day. The highest value among them is taken as the daily peak bandwidth for the node. |
Billing method | Pay-as-you-go. |
Billing cycle | Bills are generated on a daily basis. After 00:00 each day, a bill for the previous day is generated and the fee is deducted. The actual billing time is subject to the system. |
Formula |
|
Monthly 4th peak bandwidth
Category | Description |
Billing rules | The monthly 4th peak bandwidth is billed on a calendar month basis. Within a calendar month, the daily peak bandwidth is calculated. The inbound and outbound bandwidth of all instances on each edge node is measured every 5 minutes, and the higher value is used as a valid peak bandwidth data point. All daily peak bandwidth values are sorted in descending order. The fourth highest value is used as the billable bandwidth. If no bandwidth is used during certain periods, no data points are generated for those periods. |
Billing method | Pay-as-you-go. |
Billing cycle | Bills are generated on a calendar month basis. On the first day of the next calendar month, a bill for the previous month is generated and the fee is deducted. The actual billing time is subject to the system. |
Formula |
Note
|
Monthly 95th percentile bandwidth
Category | Description |
Billing rules | The monthly 95th percentile bandwidth is billed on a calendar month basis. Within a calendar month, the inbound and outbound bandwidth of all instances on each edge node is measured every 5 minutes. The higher of the two values is used as a valid peak bandwidth data point. All data points (N) are sorted in descending order. The top M data points are discarded, where M is calculated as N × 0.05 and rounded down to the nearest integer. The (M+1)th data point is the 95th percentile billable bandwidth for the month. If no bandwidth is used during certain periods, no data points are generated for those periods. |
Billing method | Pay-as-you-go. |
Billing cycle | Bills are generated on a calendar month basis. On the first day of the next calendar month, a bill for the previous month is generated and the fee is deducted. The actual billing time is subject to the system. |
Formula |
Note
|