IP Quota Limits

Resource	Default Quota	Quota Increase
Number of EIPs that a single customer can apply for in a single resource pool (single resource pool quota)	10 per account per region	Submit Ticket
Number of EIPs that a single customer can apply for in all Class I node resource pools (global quota)	20 Class I nodes per account	Submit Ticket

IP Quota Management Rules

Created Elastic IP (EIP) resources consume both the current resource pool EIP quota and the global quota. EIP resources in unpaid orders also consume the resource pool EIP quota and global quota. If the number of created EIPs does not match the occupied quota, please complete or cancel unpaid orders first.
The single resource pool quota refers to the maximum number of EIPs a single account can apply for in a single resource pool, with a default of 10.
The global quota refers to the maximum number of EIPs a single account can apply for across all Class I node resource pools, with a default of 20.
When creating an EIP, both the single resource pool quota and the global quota must be met simultaneously, meaning:

(1) When purchasing an EIP in Resource Pool A, both the remaining quota of Resource Pool A and the remaining global quota must be greater than 0.

(2) If the remaining quota of Resource Pool A is greater than 0 but the remaining global quota is less than 0, no new EIPs can be created in Resource Pool A or in any other resource pool.

(3) If the remaining quota of Resource Pool A is less than 0 but the remaining global quota is greater than 0, no new EIPs can be created in Resource Pool A, but you may switch to Resource Pool B to create a new EIP.

For pricing, see Billing Instructions.

Bandwidth and Performance Limits

Resource	Default Quota	Quota Increase	Bandwidth Peak Limits
Bandwidth Range (EIP billed by fixed bandwidth)	[1 Mbps, 300 Mbps]	Submit a ticket, with the maximum value of up to 2,000 Mbps.	The bandwidth peak of a single EIP is a committed metric. When bandwidth contention occurs, the bandwidth peak is guaranteed and will not be limited.
Bandwidth Range (EIP billed by traffic)	[1 Mbps, 300 Mbps]	Adjustment is not supported. When the bandwidth exceeds the 300 Mbps limit, customers are advised to purchase shared bandwidth and add the traffic-billed EIP to the shared bandwidth.	The bandwidth peak is only the maximum upper limit and is not a committed metric. When bandwidth contention occurs, the bandwidth peak may be restricted. Under a single account within a single resource pool, the total peak bandwidth of all traffic-billed EIPs must not exceed 5 Gbps. If a higher total bandwidth peak is required, please use fixed-bandwidth billing.

EIPs provide a selectable bandwidth range of 1–300 Mbps by default. The bandwidth you select represents the achievable peak bandwidth for your service. If the actual bandwidth exceeds this peak, speed limiting will be applied:

l Outbound bandwidth (Bandwidth from the ECS to the Internet through the EIP)
Outbound bandwidth is allocated equal to the purchased bandwidth value, with a slight over-limit allowed.

l Inbound bandwidth (Bandwidth from the Internet to the ECS bound to the EIP)

(1) When the purchased bandwidth is less than or equal to 20 Mbps, inbound bandwidth is allocated at 20 Mbps.
(2) When the purchased bandwidth is greater than 20 Mbps, inbound bandwidth is allocated equal to the purchased bandwidth, with a slight over-limit allowed in some resource pool nodes.

General Usage Restrictions

l One EIP supports binding to only one cloud resource, and the EIP and cloud resource must be in the same resource pool (Region). Cross-resource-pool usage is not supported.

l Only EIPs in normal unbound status can be bound to cloud resources. EIPs in frozen or expired status must be recharged or renewed before use. EIPs already bound must be unbound before binding to new resources.

l EIPs and cloud resources are different types of resources and are independent of billing mode. All billing modes support binding to cloud resources. After unsubscribing or deleting cloud resources, the EIP continues to incur charges. Release the EIP if no longer needed.

l If your EIP is frozen for security reasons, it cannot be restored through recharge and will not support bind, unbind, or release operations.

l Only EIPs not bound to cloud resources can be released. Bound EIPs must be unbound first.

l EIPs released may be purchased by other users and cannot be recovered.

l In pay-as-you-go billing mode, EIPs incur IP retention fees and bandwidth/traffic fees. When not bound to an instance and not released, IP retention fees apply. When bound, IP retention fees are waived. Release unused EIPs promptly.

l EIPs do not support cross-account transfer.

l When an ECS/DPS binds an EIP via an ENI, unbinding the ECS/DPS from the ENI automatically unbinds the EIP from the ENI.

Special Scenarios Overview

l EIPs provided by eSurfing Cloud are Telecom single-line IPs. When intercommunication between different networks, traffic passes through other carriers’ interconnection nodes, and congestion at peak times may cause occasional packet loss or bandwidth degradation.

Note

Starting September 2025, eSurfing Cloud EIP will no longer retain or forward DSCP values in data packets. DSCP fields for inbound and outbound Internet traffic will be cleared. Please evaluate the impact and adjust your policies in advance.

Restrictions on Binding ECSs/DPSs

To bind an EIP, the following conditions must be met:

l The region of the ECS/DPS must match the region of the EIP.

l The ECS/DPS must be in normal and stable status, running or stopped. Binding is not allowed when the order status is incomplete or the resource is frozen/expired.

From October 15, 2023, depending on the vCPU configuration of your ECS, the number of EIPs that can be bound to a single ECS is limited by the upper limit for bound EIPs, as shown in the following table:

ECS vCPU Cores	Maximum number of EIPs supported (including EIPs bound via an NIC or virtual IP)
1–5	2
6–11	3
12–17	4
18–23	5
24–29	6
30–35	7
36–41	8
42–47	9
≥ 48	10

Note

If your ECS is already bound to out-of-limit EIPs before function enforcement, your existing EIPs will not be unbound, and only the binding operations will be restricted.

Restrictions on Binding NAT Gateways

l The region of the NAT gateway must match that of the EIP.

Restrictions on Binding LBs

l The region of the load balancer (LB) must match that of the EIP.

l An LB can bind only one EIP.

Restrictions on Binding Virtual IPs

l The region of the virtual IP must match that of the EIP.

l The virtual IP must be in the Available or Assigned state.

l Each virtual IP supports binding only one EIP.

Elastic IP

Specifications and Use Restrictions