Load Balancer Health Checks in Google Cloud: Probe Ranges, Firewall Rules and Pass Conditions

GCP Study Hub
November 15, 2026

A load balancer health check is a probe that Google Cloud sends to each backend so the load balancer can stop sending traffic to backends that are unhealthy. Two things commonly go wrong. The first is a firewall that blocks the probes, which makes every backend look unhealthy even when the application is running. The second is a check that is too shallow, which keeps a broken backend in rotation because the probe still passes. For the Professional Cloud Network Engineer exam, it helps to know where the probes come from, how they interact with VPC firewall rules, and how health check resources are created and configured.

Where health check probes come from

Health check probes for Google Cloud load balancers come from two Google ranges, 35.191.0.0/16 and 130.211.0.0/22. Every VPC network has an implied deny ingress rule, so unless an ingress rule allows those ranges, the probes are dropped and every backend reports unhealthy. That holds no matter how well the application itself is running, since a probe that never arrives cannot pass.

The fix is an ingress firewall rule on the backends' network that allows TCP from the two probe ranges. Once the rule exists, the probes reach the instances, the backends turn healthy and the load balancer starts sending requests to them.

How probes interact with firewall rules

Firewall rules are stateful, and the implied allow egress rule already permits outbound traffic. Once an ingress rule admits a probe, the reply goes back automatically, so the ingress side is where the probe ranges need to appear. The load balancer and its probes also reach backends over Google's network rather than through a VM's public address, which means health checking does not depend on the backends having external IP addresses.

Making the check reflect application health

By default, an HTTP health check passes whenever the backend returns HTTP 200. That confirms a web server is answering, but not that the application behind it is working, because a web server can keep returning 200 after the application has failed.

A content-based check closes that gap. Point the health check's request path at the application's own status endpoint, and set the expected response to a string that only the running application returns. The probe then passes only when the reply contains that string, so a backend whose application is down fails the check and is removed from rotation. The expected response is the setting that moves the pass condition from the status code to the content of the reply.

Creating and configuring health checks

Application Load Balancers use the current health check resources, and there is more than one way to create them:

  • From the command line, gcloud compute health-checks create https builds an HTTPS health check. For a regional load balancer, add the --region flag so the health check sits in the same region, and specify the port and the request path the application serves.
  • In the Google Cloud console, a health check can be created while defining the backend service, without leaving the load balancer workflow.

The older gcloud compute http-health-checks create command makes a legacy health check. Legacy health checks are meant for target pool-based passthrough Network Load Balancers and cannot be attached to an Application Load Balancer's backend service.

Beyond the request path and expected response, the interval, timeout and unhealthy threshold settings control how long it takes to mark a failing backend unhealthy.

Across all of these, we would keep the two layers apart when reading a Professional Cloud Network Engineer scenario. The firewall decides whether probes arrive at all, and the health check configuration decides what a passing answer looks like.

Our Professional Cloud Network Engineer practice exams cover load balancer health checks alongside VPC firewall rules and backend services, with detailed explanations that drill these distinctions.

Get tips and updates from GCP Study Hub

arrow