All systems operational · 99.99% uptime SLA
Console Support Docs Blog Contact →
Load Balancer — ALB · NLB · CLB · Layer 4 & Layer 7

Every request.
The right server.
Every time.

Three purpose-built load balancer types — Application (Layer 7), Network (Layer 4), and Classic — for every traffic distribution pattern. Intelligent health checks, content-based routing, TLS termination, and session persistence. Built for production from day one.

Create Load Balancer → ALB vs NLB vs CLB
L4 + L7Protocol layers
3LB types
AutoHealth checks
TLSTermination
Browser GET /api/users Mobile App HTTPS:443 TCP Client TCP:8080 IoT Device UDP:5000 LOAD BALANCER ALB · NLB · CLB Listener: HTTPS:443 Listener: TCP:8080 Rule: /api → api-pool Rule: /web → web-pool Health check: all nodes OK Backend Server Pool Web Server A 10.0.1.10 · Healthy Web Server B 10.0.1.11 · Healthy API Server A 10.0.2.10 · Healthy API Server B 10.0.2.11 · Removed Round Robin · Weighted · Hash TLS Termination · SNI Session Persistence
How It Works

Distribute traffic in four steps

From creation to live traffic distribution in minutes. Health checks and routing rules start running the moment you configure them.

ALB NLB CLB ★
01

Choose LB Type

Pick Application (HTTP/HTTPS routing), Network (ultra-high performance TCP/UDP), or Classic (multi-algorithm). Choose public or private network mode.

HTTPS:443 HTTP:80 /api → pool-a /web → pool-b
02

Configure Listeners

Define ports and protocols. Add content forwarding rules (path, host, header). Attach TLS certificates with SNI support for HTTPS termination.

Node A · W:5 Node B · W:3 Node C · W:2 Cross-VPC supported
03

Add Service Nodes

Register backend servers from your VPC or across VPCs. Set weights for Weighted Round Robin. Health checks start automatically on every registered node.

EIP LB Live
04

Go Live

Bind an Elastic IP for public access. Traffic distributes immediately. Health checks auto-remove failed nodes — your application keeps running without any manual intervention.

Load Balancer Types

Three types. Every traffic pattern covered.

Each type is purpose-built for a specific use case. Choose by protocol, throughput requirements, and routing complexity.

Clients HTTPS HTTP WebSocket ALB Layer 7 /api/* → api /web/* → web host → pool TLS + SNI API Pool 3 nodes · Healthy Web Pool 4 nodes · Healthy Auth Pool 2 nodes · Healthy
Application Load Balancer
ALB
Layer 7 · HTTP / HTTPS · Content routing
  • Content-based forwarding — path, host, header, query string rules
  • HTTPS termination with TLS security policies and SNI
  • SSL certificate management from the console
  • Cross-VPC service node mounting
  • Access logs and operation audit logs
Best for: Web apps, microservices API gateways, HTTPS services requiring path/host-based routing.
NLB Layer 4 TCP:8080 UDP:5000 Proxy + TOA 10M conn Server A Server B Server C Server D
Network Load Balancer
NLB
Layer 4 · TCP / UDP · Ultra-high performance
  • Ultra-high performance — minimal overhead, maximum throughput
  • TCP and UDP protocol support up to 10M concurrent connections
  • Proxy protocol and TOA for client IP passthrough
  • Cross-VPC service node mounting
  • Operation audit logs
Best for: Game servers, real-time streaming, IoT ingestion, financial trading — any TCP/UDP workload where throughput and latency are critical.
Client TCP / HTTP CLB L4 + L7 Classic Round Robin Weighted RR Least Conn IP Hash Node W:5 10.0.1.10 Node W:3 10.0.1.11 Node W:2 10.0.1.12 Node W:1 10.0.1.13
Classic Load Balancer
CLB
Layer 4 + 7 · Multiple algorithms · Proven
  • Four algorithms: Round Robin, Weighted RR, Least Connections, IP Hash
  • Layer 4 packet forwarding and Layer 7 request forwarding modes
  • Content forwarding rules for Layer 7 mode
  • Session persistence (cookie or source IP)
  • SSL certificates, security policies, public network firewall
Best for: Stable services migrating from self-built LBs, mixed L4/L7 workloads, teams needing proven algorithm flexibility.
Feature ALB NLB CLB
OSI LayerLayer 7Layer 4Layer 4 + 7
ProtocolsHTTP / HTTPSTCP / UDPHTTP / TCP
Content routing✓ Path / Host / Header✗✓ L7 mode
TLS termination✓ + SNI✗ (passthrough)✓
PerformanceHighUltra-highHigh
Cross-VPC nodes✓✓✗
Session persistence✓~ Via TOA✓ Cookie / IP
Architecture

How traffic flows through the load balancer

From incoming request to backend response — every component in the path, and what it does.

Internet Users HTTPS :443 TCP :80 EIP Public IP LOAD BALANCER Listener: HTTPS:443 Listener: HTTP:80 TLS Termination + SNI /api/* → api-pool /web/* → web-pool Health checks · Auto remove on failure Algorithm Round Robin Weighted RR Least Conn IP Hash API POOL API Server A · 10.0.2.10 Healthy · Weight 5 API Server B · 10.0.2.11 Healthy · Weight 3 WEB POOL Web Server A · 10.0.1.10 Healthy Web Server B · 10.0.1.11 Failed · Removed MONITORING QPS · Connections · Bandwidth Access Logs · Audit Logs Alerts on node failure
Pricing

Pay per instance and traffic.

Choose hourly for development, monthly or annual for stable production. Annual billing gives 12 months for the price of 10.

Application LB
ALB
HTTP / HTTPS · Layer 7
$15 / mo from
Small (100 Mbps) $15
Medium (500 Mbps) $45
Large (1 Gbps) $90
Per month, prepaid. Hourly billing available at 1.5× daily rate.
Network LB
NLB
TCP / UDP · Layer 4
$25 / mo from
Standard (500K conn) $25
High-perf (2M conn) $75
Ultra (10M conn) $200
Per month, prepaid. Billed by concurrent connection tier.
Annual Billing
10 months
pay for 10, get 12
17% off
Lock in your load balancer tier for a full year. Best for stable production workloads with predictable traffic.
Also included: CLB pricing available in console. Elastic IPs bound to public-facing LBs billed separately. No per-request fees.
Scenarios

Every traffic distribution challenge. One solution.

From a simple two-server web setup to a multi-service microservices mesh — the right load balancer type handles it.

Internet HTTPS ALB TLS term. Web A Web B Web C
ALB · Layer 7

Web Application High Availability

ALB terminates HTTPS, distributes traffic across server pool using Round Robin or Weighted Round Robin. Failed nodes are removed automatically by health checks — users never see an error from a dead server.

TLS termination Health checks Auto failover
All Requests ALB /api → /auth → /pay → API Service Auth Service Pay Service
ALB · Content Routing

Microservices Path Routing

A single ALB routes all traffic using path-based rules — /api to the API service pool, /auth to authentication, /payment to the payment service. One public IP, multiple backend services.

Path routing Host routing 1 IP many services
NLB UDP/TCP Game Server 1 Game Server 2 Game Server 3
NLB · Layer 4

Gaming & Real-time Applications

NLB's Layer 4 ultra-high performance handles millions of concurrent TCP/UDP connections with minimal latency overhead. Ideal for game servers, video streaming, and any real-time protocol where latency is critical.

UDP support Ultra-low latency
Private VPC · Internal only Web Tier Internal LB App Server A App Server B App Server C
Private Mode · Internal LB

Internal Service Mesh

An internal (private network mode) load balancer distributes traffic between tiers within your VPC — web tier to application tier, application tier to database tier. No public IP, no external exposure, just internal load distribution.

Private VPC only Tier-to-tier
Global Network

A truly global infrastructure for fast, reliable service delivery.

26
Regions
33
Availability Zones
25ms
Regional latency
99.95%
SLA uptime
Active region
Hub region (Dubai HQ)
Backbone link
Customer Stories

How teams are running traffic on NubexCloud Load Balancer

We switched our API gateway from a self-managed Nginx cluster to NubexCloud ALB. The path-based routing to different microservice pools replaced 400 lines of Nginx config. TLS termination, health checks, access logs — all managed. Our infra team reclaimed a full sprint of maintenance time per month.

SaaS · ALB
VP Engineering
B2B SaaS platform, UAE
400
lines of config eliminated

Our game servers handle 2.4 million concurrent UDP connections at peak. NLB is the only managed load balancer in the region that handles this at Layer 4 without packet inspection overhead. We went from 12ms average session setup to 3ms. That difference is audible to players.

Gaming · NLB
Head of Infrastructure
Online gaming platform, GCC
75%
reduction in session setup time

We run a three-tier application — ALB for the public-facing web layer, internal CLB between web and application tiers. The Weighted Round Robin algorithm lets us do zero-downtime deployments: bring new nodes up at weight 0, ramp to full weight, drain and remove old nodes. No user impact at all.

E-commerce · ALB + CLB
CTO
Retail platform, MENA
Zero
downtime deployments
Trusted by leading teams across the region
Falcon AITradeSparkMasaarNEXAGENSalam DigitalOrbita
FAQ

Common questions about NubexCloud Load Balancer

Start distributing traffic today

Every request. The right server. Every time.

ALB for Layer 7 content routing. NLB for ultra-high performance TCP/UDP. CLB for proven multi-algorithm distribution. Deploy the right type in minutes — health checks run automatically from the first node.

Create Load Balancer → Read the Docs