Managed L4 (NLB) and L7 (ALB) load balancers with HTTP/3 and QUIC support, health checks, TLS termination, weighted forwarding, geo-aware routing, and integration with Alibaba's Anti-DDoS and WAF
Jurisdictional exposure
Attributes
- Http3support
- Yes
Sub-services (3)
Application Load Balancer (ALB)
L7 LB with host and path routing, HTTP/2, HTTP/3, and WebSocket
Network Load Balancer (NLB)
L4 TCP and UDP LB with source-IP preservation and microsecond latency
Classic Load Balancer (CLB)
Legacy shared-tenant LB for smaller workloads
Compliance & Certifications
This service is attested for the following frameworks. Always verify with the provider before relying on a specific compliance posture.
Where this runs
Sovereign regions (13)
- China (Hangzhou) · HangzhouAlibaba Cloud China
- China (Beijing) · BeijingAlibaba Cloud China
- China (Shanghai) · ShanghaiAlibaba Cloud China
- China (Shenzhen) · ShenzhenAlibaba Cloud China
- China (Chengdu) · ChengduAlibaba Cloud China
- China (Zhangjiakou) · ZhangjiakouAlibaba Cloud China
- China (Hohhot) · HohhotAlibaba Cloud China
- China (Qingdao) · QingdaoAlibaba Cloud China
- China (Heyuan) · HeyuanAlibaba Cloud China
- China (Ulanqab) · UlanqabAlibaba Cloud China
- China (Wuhan) · WuhanAlibaba Cloud China
- China (Guangzhou) · GuangzhouAlibaba Cloud China
- China (Zhongwei) · ZhongweiAlibaba Cloud China
Commercial regions (18)
Europe (3)
- France (Paris)
- Frankfurt
- London
North America (3)
- Mexico
- Silicon Valley
- Virginia
South America (1)
- Brazil (São Paulo)
Asia (9)
- Hong Kong
- Jakarta
- Tokyo
- Malaysia (Johor)
- Kuala Lumpur
- Manila
- Singapore
- Seoul
- Bangkok
Middle East (2)
- SAU (Riyadh - Partner Region)
- Dubai
Tags
Equivalent services on other platforms
Managed L4/L7 load balancers for Linodes and LKE, with health checks, TLS termination, session stickiness and a flat monthly price per balancer
Distribute incoming traffic across multiple targets with four load balancer types: Application (L7), Network (L4), Gateway (inline appliances), and Classic (legacy)
Anycast network layer that routes client traffic to the nearest AWS edge and across the AWS global backbone to healthy endpoints in multiple regions, with two static anycast IPs, automatic failover, TCP and UDP support, and DDoS protection via Shield Standard
High-performance L4 load balancing with public and internal endpoints, zonal and zone-redundant SKUs, TCP/UDP health probes, and outbound SNAT rules
Layer 7 load balancer with integrated web application firewall, SSL termination, URL-based routing, cookie-based session affinity, and autoscaling based on traffic
Global application delivery network and CDN with anycast acceleration, caching, rules engine, WAF, bot protection and Private Link origins, in Standard and Premium tiers. Front Door (classic) is closed to new resources and retires 31 March 2027.
Managed HTTP/HTTPS/TCP load balancers with SSL termination, health checks, and zero-downtime backend rotation
Multi-tenant, programmable load balancer as a service offering Layer 4 and Layer 7 balancing with TLS termination for Catalyst Cloud instances and Kubernetes services. Billed hourly per load balancer (n1.lb).
Managed L4/L7 load balancers fronting Civo Compute and Kubernetes workloads with health checks, sticky sessions, and TLS termination
OpenStack-Octavia managed load balancer for Cleura Compute and Kubernetes workloads. Layer-4 and layer-7 balancing, health checks, TLS termination, and integration with Neutron floating IPs.
Global DNS and anycast-based traffic load balancing across pools of origins with weighted, geo-steering, random, proximity, and least-outstanding-requests policies plus active health checks and automatic failover
Managed regional and global load balancers distributing traffic across Droplets and Kubernetes nodes with health checks, TLS termination and sticky sessions
Zone-scoped Layer 4 (TCP/UDP) load balancer that spreads traffic across Instance Pool members, with health checks and Round Robin, Source-Hash or Maglev-Hash strategies; billed per hour
Managed L4 and L7 load balancing with TLS termination, health checks, sticky sessions, and integration with Gcore's compute and managed Kubernetes
Global software-defined L4 and L7 load balancing with a single anycast IP, cross-region failover, CDN integration, and Cloud Armor DDoS protection
Managed L4/L7 load balancers with health checks, sticky sessions, and managed certificate provisioning
Managed L4 and L7 load balancing with shared and dedicated instance types, HTTP/HTTPS/TCP/UDP listeners, cross-zone forwarding, health checks, TLS termination, and integration with WAF and Anti-DDoS
Edge delivery and security bundle powered by Cloudflare, offering DNS, global load balancing, WAF, DDoS protection, CDN, rate limiting, and Page Rules through a single IBM Cloud-native control plane
OpenStack Octavia load balancers for Public Cloud instances and Kubernetes services, alongside floating IPs and DDoS protection, hosted in Switzerland.
Managed Layer 4 (TCP) network load balancer, deployable as public or private, with forwarding rules to VMs in a listener LAN; available in all IONOS Cloud locations, including the US.
Layer-7 load balancer with HTTP/HTTPS path-based routing, SSL termination, sticky sessions, and integration with Compute Engine and Managed Kubernetes target pools
Layer 4 (network) and Layer 7 (application) load balancers with health checks, SSL termination, and integration with WAF
Private networks, routers, floating IPs, security groups, and load-balancing — OpenStack Neutron-backed. The networking primitives stitching together Leaf VMs and Kubernetes clusters.
Managed Application, Network and Network Proxy load balancers distributing traffic across VPC servers with health checks and SSL termination
Load balancers for Nscale workloads, managed through the Nscale CLI and API (create, update, list and delete).
Managed load balancer for NumSpot VMs and Kubernetes services: HTTP/HTTPS and TCP/SSL listeners, health checks, sticky sessions, SSL termination (TLS 1.1/1.2) or passthrough, in internet-facing or internal mode
Load Balancer as a Service powered by HAProxy (or a vendor backend), with TLS termination, L4/L7 routing, autoscaling pools, and amphora-based active/standby high availability — the OpenStack equivalent of ELB / Azure Load Balancer / Cloud Load Balancing
Managed load balancing with both L7 HTTP/HTTPS flavour (Flexible Load Balancer with SSL offload, WAF integration, path-based routing) and L4 Network Load Balancer (UDP, TCP, ultra-low-latency) across OCI regions with auto-scaling bandwidth
Managed L4 and L7 load balancers — TCP/UDP passthrough, HTTP/HTTPS with path-based routing, TLS termination with managed certificates, sticky sessions, and cross-AZ health checks
Load Balancer Unit - load balancer with HTTP/HTTPS and TCP/SSL listeners, health checks, sticky sessions, SSL termination (TLS 1.1-1.3) or passthrough, AWS ELB-compatible API; internet-facing or internal (in a Net) modes
Layer-4 and Layer-7 managed load balancer for Public Cloud Instances and Managed Kubernetes, with HTTP/HTTPS path routing, SSL termination, and cross-zone health checks
Managed Google Cloud load balancing operated by S3NS within its SecNumCloud-qualified Cloud de Confiance, distributing traffic across backends in the u-france-east1 region.
Managed L4 and L7 load balancer with health checks, SSL termination, sticky sessions, and integration with Instances and Kubernetes Kapsule target pools
Managed Layer 4 (TCP/UDP) load balancer with listeners, target pools and health checks, sized by connection limit and used by Kubernetes Engine for Services of type LoadBalancer; for HTTP(S) routing and TLS termination see the Application Load Balancer
Layer-7 load balancer with HTTP/HTTPS path-based routing, SSL termination, and integration with Compute Engine and Kubernetes Engine target pools — distinct from the L4 STACKIT Load Balancer
Managed L4 and L7 load balancing with internet-facing and internal variants, HTTP/HTTPS/TCP/UDP/QUIC listeners, WebSocket support, session persistence, configurable health checks, and automatic integration with TCR and CKafka origins
Layer 4 / Layer 7 managed load balancer with automated failover across UpCloud zones and managed certificate provisioning
Managed load balancers distributing incoming traffic across Vultr instances, with configurable forwarding rules and global load balancer regions