Should my L7 ILB be cross region or regional

Google Cloud Compute Infrastructure
1

I am trying to use L7 ILB. Backend will be Private Service Connect NEGs pointing to ApigeeX service attachment.

As the backend will be in the region the Apigee is (my use case is to have 1-1 mapping with ILB to Apigee), so what will be better, global access single region ILB for which apps in same vpc or peered vpc will call the ILB; vs ILB’s backend is in other region.

Want to understand which option may add latency?

2

Hi @amitkhosla ,

Welcome to Google Cloud Community!

Below table explains the key differences on Internal Application Load Balancer configurations using two mode of operations:

  1. Cross-region Internal Application Load Balancer - Enables you to load balance traffic to backend services that are globally distributed, including traffic management that ensures traffic is directed to the closest backend. Increased latency due to cross-region Internal Load Balancer-to-backend hop, for Multi-region availability or failover.
  2. Regional Internal Application Load Balancer - Minimal latency for clients in the same region due to intra-region Internal Load Balancer-to-backend communication, for Intra-region microservices or private APIs

Screenshot 2025-07-10 7.15.11 PM.png
Screenshot 2025-07-10 7.15.11 PM.png769×409 53.8 KB

For your use case, it is recommended to use the Regional Internal Application Load Balancer, global access enabled to support clients in the same or peered VPCs across regions and to minimize latency, avoiding cross-region latency for the Internal Load Balancer-to-backend hop.

Other references you may find helpful:

Was this helpful? If so, please accept this answer as “Solution”. If you need additional assistance, reply here within 2 business days and I’ll be happy to help.

2 Likes