Purchase Methods

Cloud Load Balancer (CLB) supports two network types: public and private.

• In a public network, CLB handles traffic coming from the internet.
• In a private network, CLB distributes traffic within the Converge Cloud internal network.

Private network CLB instances do not support certain settings, such as: Elastic IP (EIP), IP version, ISP selection, instance specifications, network billing options, and bandwidth limits—so these options are hidden by default.

Support for network types depends on the billing method:

• Under the pay-as-you-go model, both public and private networks are supported.

• If you do not select an Elastic IP (EIP), Converge Cloud will provide a public network CLB instance with a fixed public IP address that cannot be modified.
• If you choose to use an EIP, Converge Cloud will assign an Elastic IP along with a private network CLB instance that functions similarly to a public CLB.

Note: Only pay-as-you-go public CLB instances support the option to bind an EIP.

Cloud Load Balancer (CLB) supports three IP versions: IPv4, IPv6, and IPv6 NAT64. Note that only pay-as-you-go CLB instances currently support IPv6, which is still in beta testing.

Load Balancer (LB) supports both classic network and Virtual Private Cloud (VPC) environments

• The classic network is a shared public network where private IP addresses are automatically assigned by Converge Cloud. Users cannot define IP ranges or specific addresses.
• A VPC is an isolated, customizable network within Converge Cloud. It allows users to set custom IP ranges, assign specific IPs, and define routing rules.

For greater flexibility and control, using a VPC is recommended—especially for applications that require tailored network configurations.

The primary availability zone (AZ) is the main zone that actively handles incoming traffic. The secondary AZ remains on standby and only takes over if the primary AZ becomes unavailable, ensuring service continuity and high availability.

Shared Instances provide performance based on their defined specifications. Each instance can handle up to 50,000 concurrent connections, support 5,000 new connections per second, and process 5,000 queries per second, ensuring reliable service for typical workloads.

Cloud Load Balancer supports multiple network billing options, including bandwidth-based billing (monthly or hourly), traffic-based billing, and bandwidth packages. For pay-as-you-go instances, the available billing modes are: hourly bandwidth, traffic-based, and bandwidth package.

For shared CLB instances, the maximum public network bandwidth is capped at 2 Gbps. For the private network, it’s recommended to keep the bandwidth limit within 5 Gbps to ensure stable performance. For CLB instances that support Load Capacity Units (LCU), the bandwidth cap is determined by the instance specification selected during setup.

Select a project.

Select a tag key and value.

You can assign a name with up to 60 characters, including letters, numbers, hyphens (-), underscores (_), and dots (.).
If no name is provided, Converge Cloud will generate one automatically.