Load Balancing

Worldwide Autoscaling and Load Balancing allows you to scale your applications on intelHUB Compute Engine from zero to full-throttle with intelHUB Cloud Load Balancing, with no pre-warming needed. Distribute your load-balanced compute resources in single or multiple regions, close to your users and to meet your high availability requirements. Cloud Load Balancing can put your resources behind a single anycast IP and scale your resources up or down with intelligent Autoscaling. Cloud Load Balancing comes in a variety of service types and is integrated with Cloud CDN for optimal application and content delivery.

High performance, scalable load balancing

Global Load Balancing with Single Anycast IP

With Cloud Load Balancing, a single anycast IP front-ends all your backend instances in regions around the world. It provides cross-region load balancing including automatic multi-region failover which gently moves traffic in fractions if backends become unhealthy. In contrast to DNS-based Global Load Balancing solutions, Cloud Load Balancing reacts instantaneously to changes in users, traffic, network, backend health and other related conditions.

Software-Defined Load Balancing

Cloud Load Balancing is a fully distributed, software-defined, managed service for all your traffic. It is not an instance or device based solution, so you won’t be locked into physical load balancing infrastructure or face the HA, scale and management challenges inherent in instance based LBs. You can apply Cloud Load Balancing to all of your traffic: HTTP(S), TCP/SSL, and UDP. You can also terminate your SSL traffic with HTTPS Load Balancing and SSL proxy.

Over One Million Queries Per Second

Cloud Load Balancing is built on the same front-end serving infrastructure that powers intelHUB. It supports 1 Million+ queries per second with consistent high performance and low latency. Traffic enters Cloud Load Balancing through 80+ distinct global load balancing locations, maximising the distance traveled on a fast private network backbone.

Seamless Autoscaling

Cloud Load Balancing can scale as your users and traffic grow, including easily handling huge, unexpected and instantaneous spikes by diverting traffic to other regions in the world that can take traffic. Autoscaling does not require pre-warming, you can scale from zero to full throttle in a matter of seconds.

Internal Load Balancing

Internal Load Balancing enables you to build scalable and highly available internal services for your internal client instances without requiring your load balancers to be exposed to the internet. GCP Internal Load Balancing is architected using Andromeda, a software-defined network virtualisation platform. Internal Load Balancing also includes support for clients across VPN.

Support for cutting edge protocols

Cloud Load Balancer includes support for the latest application delivery protocols. It supports HTTP/2 with gRPC when connecting to Backends and also is the first major public cloud to offer QUIC support for our HTTPS load balancers to provide faster session setup to provide customers with a more responsive application experience.

Cloud Load Balancing

intelHUB Cloud Platform Load Balancing enables you to do the following:


  • Distribute load-balanced resources in single or multiple regions
  • Meet your high availability requirements
  • Put your resources behind a single anycast IP address
  • Scale your resources up or down with intelligent Autoscaling
  • Use Cloud CDN for optimal content delivery


With Cloud Load Balancing, you can serve content as close as possible to your users, on a system that can respond to over 1 million queries per second. Cloud Load Balancing is a fully distributed, software defined, managed service. It is not instance or device based, so you do not need to manage a physical load balancing infrastructure.

Deciding on a load balancer

To decide which load balancer best suits your implementation of intelHUB Cloud Platform, consider the following aspects of Cloud Load Balancing:


  • Global versus regional load balancing
  • External versus internal load balancing
  • Traffic type


After you determine whether you need global or regional load balancing, external or internal load balancing, and what traffic type your load balancers must handle, use the following flow chart to determine which load balancers are available for your client, protocol, and network configuration.

Summary of Cloud load balancers

The following table provides some specifics about each load balancer.

Load balancer Traffic type Global/Regional External/Internal External Ports for Load Balancing
HTTP(S) HTTP or HTTPS Global External HTTP on 80 or 8080; HTTPS on 443
SSL Proxy TCP with SSL offload Global External 25, 43, 110, 143, 195, 443, 465, 587, 700, 993, 995, 1883, and 5222
TCP Proxy TCP without SSL offload. Does not preserve client IP addresses Global External 25, 43, 110, 143, 195, 443, 465, 587, 700, 993, 995, 1883, 5222
Network TCP/UDP TCP/UDP without SSL offload. Preserves client IP addresses Regional External Any
Internal TCP/UDP TCP or UDP Regional Internal Any

intelHUB Cloud Load Balancing Features

High performance, scalable load balancing on intelHUB Cloud Platform

HTTP(S) Load Balancing

HTTP(S) load balancing can balance HTTP and HTTPS traffic across multiple backend instances, across multiple regions. Your entire app is available via a single global IP address, resulting in a simplified DNS setup. HTTP(S) load balancing is scalable, fault-tolerant, requires no pre-warming, and enables content-based load balancing. For HTTPS traffic, it provides SSL termination and load balancing.

TCP/SSL Load Balancing

TCP load balancing can spread TCP traffic over a pool of instances within a Compute Engine region. It is scalable, does not require pre-warming, and health checks help ensure only healthy instances receive traffic. SSL proxy provides SSL termination for your non-HTTPS traffic with load balancing.

SSL Offload

SSL offload enables you to centrally manage SSL certificates and decryption. You can enable encryption between your load balancing layer and backends to ensure the highest level of security, with some additional overhead for processing on backends.

Advanced Feature Support

Cloud Load Balancer also includes advanced support features, such as IPv6 Global Load Balancing, WebSockets, user-defined request headers, and protocol forwarding for private VIPs.

UDP Load Balancing

UDP load balancing can spread UDP traffic over a pool of instances within a Compute Engine region. It is scalable, does not require pre-warming, and health checks help ensure only healthy instances receive traffic.

Stackdriver Logging

Stackdriver Logging for load balancing logs all the load balancing requests sent to your load balancer. These logs can be used for debugging as well as analysing your user traffic. You can view request logs and export them to Cloud Storage, BigQuery, or Cloud Pub/Sub for analysis.

Seamless Autoscaling

Autoscaling helps your applications gracefully handle increases in traffic and reduces cost when the need for resources is lower. You just define the autoscaling policy and the autoscaler performs automatic scaling based on the measured load. No pre warming required – go from zero to full throttle in seconds.

High Fidelity Health Checks

Health checks ensure that new connections are only load balanced to healthy backends that are up and ready to receive them. High fidelity health checks ensure that the probes mimic actual traffic to backends.


Cloud Load Balancing Affinity provides the ability to direct and stick user traffic to specific backend instances.

Cloud CDN Integration

Enable Cloud CDN for HTTP(S) Load Balancing for optimising application delivery for your users with a single checkbox.

Want To Know More​

Need further information or require a quotation?

All calls are recorded for security, training and quality purposes

Our lines are open Monday to Friday from 9am to 5.30pm. Dialling an 0330 number costs the same to dial as a call to a geographic (local) number. They cost the same to call from a landline or mobile and are included in mobile call packages.

You are calling our Network Operations Centre based in London, United Kingdom.

Just so you know, we are not able to accept telesales or telemarketing calls and can't be transferred.

Working proudly with skilled teams of people knowing we push the boundaries staying ahead of the curve producing high performance results.