A web app hosted in us-central1 shows high latency for users in Asia; a Network Load Balancer produced no improvement. How should you reduce latency for global users?

An HTTP(S) Load Balancer (specifically, a Global External HTTP(S) Load Balancer) is a global, Layer 7 load balancer that can distribute traffic across multiple regions. By deploying backend services in regions closer to your users (e.g., Asia for users in Asia), it automatically routes requests to the nearest healthy backend, significantly reducing latency. A Network Load Balancer is a regional, Layer 4 load balancer and does not offer global distribution or proximity routing. Policy-based routing rules prioritize traffic within a network but don't inherently reduce latency by moving the service closer to the user. Dynamic Routing is for internal network routing and doesn't address external user latency. Reducing DNS TTL affects how quickly DNS changes propagate, but doesn't change the physical location of your application or how traffic is routed to it.