All Products
Search
Document Center

Elastic IP Address:Limits

Last Updated:Sep 19, 2025

This topic describes the quotas and performance limits of Elastic IP Address (EIP) and the limits on associating an EIP with different cloud resources.

Quota limits

Resource

Default quota

Request a quota increase

Number of EIP that can be requested per Alibaba Cloud account

20

Go to the Quota Management page or Quota Center to request a quota increase.

Performance limits

  • Only EIP in the Available state can be associated with cloud resources. One EIP can be associated with only one cloud resource. The association takes effect immediately.

  • An EIP that is locked for security reasons cannot be associated, disassociated, or released.

  • The following table describes the peak bandwidth limits for EIP.

    Pay-by-traffic EIP

    Pay-by-bandwidth EIP

    The maximum bandwidth for a single EIP is 200 Mbps. This is an upper limit for reference only and is not guaranteed. Bandwidth may be limited during periods of resource contention.

    The maximum bandwidth for a single pay-as-you-go, pay-by-bandwidth EIP is 500 Mbps. This bandwidth is guaranteed, even during periods of resource contention.

    The total peak bandwidth of all pay-by-traffic EIP under a single Alibaba Cloud account in a region cannot exceed 5 Gbps. If your business requires guaranteed bandwidth or a higher maximum bandwidth, you can use pay-by-bandwidth EIP.

    The total peak bandwidth of all pay-by-bandwidth EIP under a single Alibaba Cloud account in a region cannot exceed 50 Gbps. To request a higher bandwidth, contact your account manager.

    Note

    When a pay-by-traffic EIP instance joins an Internet Shared Bandwidth instance, the original billing method and maximum bandwidth of the EIP instance no longer apply. You are charged a data transfer fee for the Internet Shared Bandwidth instance, and the EIP instance shares the maximum bandwidth of the Internet Shared Bandwidth instance. Therefore, the preceding rules do not apply to the EIP instance.

  • For EIP that are purchased, renewed, or have their configurations changed after 00:00:00 (UTC+8) on February 15, 2020, the following bandwidth throttling rules for inbound and outbound traffic apply:

    • Inbound bandwidth (bandwidth consumed by traffic that flows to the EIP)

      • If the maximum bandwidth of your EIP is 10 Mbps or higher, Alibaba Cloud allocates an inbound bandwidth equal to the maximum bandwidth.

      • If the maximum bandwidth of your EIP is less than 10 Mbps, Alibaba Cloud allocates an inbound bandwidth of 10 Mbps.

    • Outbound bandwidth (bandwidth consumed by traffic that flows from the EIP)

      Alibaba Cloud allocates an outbound bandwidth equal to the maximum bandwidth of the EIP.

  • The following limits apply to the security protection level configuration of EIP:

    • Only pay-as-you-go EIPs of the BGP (Multi-ISP) line type support Anti-DDoS Pro.

    • When you create an Anti-DDoS Pro EIP from a specified address pool, the address pool must also be of the Anti-DDoS Pro type.

    • You can select Anti-DDoS Pro only when you purchase an EIP or create an address pool. You cannot switch between the default security protection and Anti-DDoS Pro.

    • The following regions support Anti-DDoS Pro:

      EIP

      • China: China (Beijing), China (Hangzhou), China (Shanghai), and China (Hong Kong)

      • Asia Pacific: Philippines (Manila), Japan (Tokyo), Singapore, Malaysia (Kuala Lumpur), Indonesia (Jakarta), South Korea (Seoul), and Thailand (Bangkok)

      • Others: US (Virginia), US (Silicon Valley), Germany (Frankfurt), UK (London), and Mexico

      IP address pool

      • China: China (Hong Kong)

      • Asia Pacific: Philippines (Manila), Japan (Tokyo), Singapore, Malaysia (Kuala Lumpur), Indonesia (Jakarta), South Korea (Seoul), and Thailand (Bangkok)

      • Others: US (Virginia), US (Silicon Valley), Germany (Frankfurt), UK (London), and Mexico

  • When an Elastic Compute Service instance in a region in China (including Hong Kong (China) and Macao (China), but not including Taiwan (China)) uses an EIP to access an Elastic Compute Service instance in another country or region, you may experience high access latency and, in extreme cases, packet loss. We recommend that you deploy your services in the same region or use Cloud Enterprise Network for cross-region connections.

Limits on associating with an ECS instance

  • The ECS instance must be deployed in a virtual private cloud (VPC).

  • The ECS instance and the EIP must be in the same region.

  • The ECS instance must be in the Running or Stopped state.

  • The ECS instance cannot be assigned a static public IP address or be associated with another EIP.

  • An ECS instance can be associated with only one EIP. However, you can associate multiple EIP with an ECS instance by attaching secondary elastic network interfaces (ENIs) to the ECS instance.

Limits on associating with an NAT Gateway

  • The NAT Gateway and the EIP must be in the same region.

  • An NAT Gateway can be associated with up to 20 EIP.

Starting from September 19, 2022, when you associate an EIP with a newly created Internet NAT gateway, a private IP address is used from the vSwitch of the NAT gateway. This does not affect existing NAT gateway instances. Make sure that the vSwitch of the NAT gateway has sufficient private IP addresses. If no private IP addresses are available in the vSwitch, you cannot associate new EIPs.

Limits on associating with a CLB instance

  • The CLB instance must be deployed in a VPC.

  • The CLB instance and the EIP must be in the same region.

  • A CLB instance can be associated with only one EIP.

Limits on associating with a high-availability virtual IP address

  • The high-availability virtual IP address and the EIP must be in the same region.

  • The high-availability virtual IP address must be in the Available or Allocated state.

  • A high-availability virtual IP address can be associated with only one EIP.

Limits on associating with a secondary ENI

  • The secondary ENI must be deployed in a VPC.

  • The secondary ENI and the EIP must be in the same region.

  • You can associate an EIP with a secondary ENI in NAT Mode or Cut-through Mode.

    • In NAT Mode, the number of EIP that you can associate with a secondary ENI depends on the number of private IP addresses that are assigned to the secondary ENI.

    • In Cut-through Mode, you can associate only one EIP with a secondary ENI.