Meta tags:
description=Determine the optimal Google Cloud load balancer for your application based on the type of traffic you want to support, the location of your clients, and whether you need a global or regional deployment.;

Headings (most frequently used words):

load, balancing, versus, and, choose, balancer, stay, organized, with, collections, save, categorize, content, based, on, your, preferences, aspects, summary, of, google, cloud, balancers, what, next, traffic, type, external, internal, global, regional, proxy, passthrough, premium, standard, network, service, tiers, products, pricing, support, resources, engage,

Text of the page (most frequently used words):
load (183), the (107), #balancer (101), and (74), cloud (46), balancers (46), backend (42), set (42), external (40), backends (39), overview (35), you (35), global (35), balancing (34), with (33), tier (33), regional (31), traffic (31), network (30), internal (27), your (27), application (27), google (25), proxy (25), premium (24), for (23), region (23), that (22), use (21), neg (21), choose (17), instance (17), service (16), group (16), tcp (15), zonal (14), using (13), managed (13), standard (13), passthrough (13), ssl (13), http (13), https (13), hybrid (13), cross (12), management (12), resources (11), only (11), from (11), can (11), internet (11), vpc (11), other (10), are (10), type (10), which (10), architecture (9), need (9), forwarding (9), buckets (9), custom (9), clients (8), regions (8), classic (8), external_managed (8), udp (8), address (8), client (8), versus (8), distributed (8), multiple (8), add (8), support (7), all (7), thumb (7), this (7), services (7), table (7), based (7), when (7), storage (7), url (7), negs (7), mtls (7), capabilities (7), see (6), information (6), more (6), rules (6), such (6), connections (6), determine (6), tls (6), ipv6 (6), target (6), serverless (6), premises (6), shared (6), run (6), code (5), down (5), content (5), policies (5), same (5), access (5), migrate (5), available (5), either (5), internal_managed (5), whether (5), icmp (5), esp (5), offload (5), following (5), summary (5), not (5), deployed (5), don (5), between (5), terminate (5), across (5), troubleshooting (5), metrics (5), redirect (5), português (4), español (4), source (4), scheme (4), envoy (4), always (4), each (4), tiers (4), high (4), connectivity (4), networks (4), latency (4), have (4), addresses (4), preserve (4), handle (4), distribution (4), also (4), require (4), connected (4), protocols (4), tools (4), maps (4), certificates (4), view (4), logs (4), monitor (4), troubleshoot (4), configure (4), terraform (4), examples (4), create (4), headers (4), samples (3), products (3), understand (3), under (3), its (3), send (3), feature (3), next (3), default (3), however (3), rule (3), migration (3), new (3), open (3), gfe (3), icmpv6 (3), gre (3), optional (3), documentation (3), peering (3), configured (3), backbone (3), close (3), performance (3), applications (3), requirements (3), authentication (3), connection (3), might (3), want (3), identity (3), works (3), vms (3), terminated (3), proxies (3), depending (3), outage (3), scope (3), must (3), over (3), security (3), globally (3), comes (3), distribute (3), protocol (3), best (3), modes (3), product (3), guides (3), networking (3), health (3), frontend (3), explore (3), tutorials (3), directory (3), registration (3), 한국어 (2), 日本語 (2), עברית (2), brasil (2), italiano (2), indonesia (2), français (2), américa (2), latina (2), deutsch (2), english (2), sign (2), third (2), terms (2), site (2), youtube (2), started (2), pricing (2), last (2), updated (2), 2026 (2), utc (2), noted (2), licensed (2), details (2), license (2), feedback (2), features (2), comparison (2), allow (2), possible (2), recommend (2), term (2), indicates (2), front (2), without (2), deployment (2), resource (2), decision (2), point (2), where (2), quality (2), certain (2), packets (2), optimize (2), low (2), different (2), first (2), instead (2), packet (2), then (2), responses (2), back (2), option (2), given (2), resilient (2), summarizes (2), resilience (2), compliance (2), specific (2), one (2), termination (2), stay (2), provide (2), multi (2), private (2), aspects (2), additional (2), like (2), two (2), operation (2), sdk (2), languages (2), frameworks (2), infrastructure (2), costs (2), usage (2), observability (2), monitoring (2), industry (2), solutions (2), multicloud (2), databases (2), data (2), analytics (2), pipelines (2), compute (2), hosting (2), development (2), logging (2), pools (2), tags (2), checks (2), optimizations (2), authorization (2), workload (2), failover (2), concepts (2), pool (2), convert (2), capacity (2), web (2), request (2), routing (2), app (2), engine (2), functions (2), error (2), constraints (2), console (2), reference (2), technology (2), areas (2), subscribe, newsletter, our, decade, climate, action, join, manage, cookies, privacy, about, tech, twitter, events, blog, engage, training, certification, center, getting, github, system, status, release, notes, community, forums, contact, sales, marketplace, easy, easytounderstand, solved, problem, solvedmyproblem, otherup, hard, hardtounderstand, incorrect, sample, incorrectinformationorsamplecode, missing, missingtheinformationsamplesineed, otherdown, tell, except, otherwise, page, java, registered, trademark, oracle, affiliates, developers, apache, creative, commons, attribution, comparative, offered, what, enabling, attach, cannot, attached, take, advantage, existing, process, described, implemented, requests, routed, end, attribute, used, sctp, mode, provides, operates, along, because, level, some, others, help, make, tree, plan, budget, accordingly, enters, exits, closest, therefore, associated, apply, egress, charges, specify, defaults, traverses, intent, enter, exit, edge, lets, systems, instances, delivers, while, uses, regular, isp, general, cost, alternative, strict, form, relies, keeping, track, opened, expects, second, compatible, aware, iap, method, note, balanced, received, destination, applicable, port, unchanged, directly, through, direct, server, return, name, suggests, come, category, incoming, work, way, they, ends, gfes, affects, zones, critical, component, most, highly, important, overall, depends, just, but, redundancy, workloads, regionalized, reasons, mandate, kept, geographic, control, should, connect, thus, guarantee, transport, layer, locations, minimize, ipv4, jurisdictional, particular, subnet, providing, review, learn, single, anycast, span, making, them, suitable, flexibility, grows, geographies, vpn, interconnect, virtual, these, another, factor, determining, decide, suits, implementation, consider, click, enlarge, diagram, further, narrow, choices, facing, regionally, avoid, overhead, implement, flexible, document, helps, meets, needs, save, categorize, preferences, organized, collections, home, clean, setup, check, audit, operate, maintain, map, size, quota, units, subnets, endpoint, groups, dns, names, firewall, draining, advanced, customize, post, quantum, authenticated, user, provided, mutual, encryption, self, secure, switch, deploy, hub, spoke, hop, common, party, appliances, hops, affinity, weighted, testing, deliver, published, domain, faster, improved, protection, practices, fail, availability, rewrite, header, query, parameter, roll, response, project, bucket, organization, policy, iam, conditions, roles, permissions, get, model, discover, start, free, skip, main,

Text of the page (random words):
cloud backends zonal and hybrid neg external backend internet neg add capabilities traffic management overview set up traffic management set up high availability set up http to https redirect set up a load balancer with backend service using shared vpc set up a load balancer with backend buckets using shared vpc create custom headers in url maps fail over to regional load balancers monitor and troubleshoot overview global load balancers regional load balancers troubleshooting best practices explore tutorials request routing to a multi region external https load balancer faster web performance and improved web protection for load balancing deliver http and https content over the same published domain optimize application latency with load balancing application capacity optimizations with global load balancing capacity management with load balancing internal load balancer architecture overview set up cross region load balancer managed vm instance group backend cloud storage backend buckets on premises or other cloud backends zonal and hybrid neg cloud run backends serverless neg set up regional load balancer terraform examples vm instance group backends cloud run backends serverless neg cloud storage backend buckets on premises or other cloud backends zonal and hybrid neg external backend internet neg add capabilities traffic management overview set up traffic management set up http to https redirect create custom headers in url maps set up regional internal load balancer with backend service using shared vpc set up cross region load balancer with backend buckets using shared vpc set up a regional internal application load balancer with backend buckets using shared vpc service directory registration load balancing and connected networks monitor and troubleshoot view logs and metrics troubleshooting convert load balancer to ipv6 use custom metrics load testing backends proxy network load balancer tcp ssl proxy overview external load balancer architecture overview set up global load balancer global ssl proxy with vm instance group backends global tcp proxy with vm instance group backends set up global load balancer classic terraform examples global ssl proxy with vm instance group backends global tcp proxy with vm instance group backends set up regional load balancer vm instance group backends zonal neg backends hybrid connectivity hybrid negs external backend internet neg internal load balancer architecture overview set up cross region load balancer managed vm instance group backends on premises or other cloud backends zonal and hybrid neg set up regional load balancer managed vm instance group backends zonal neg backends hybrid connectivity hybrid negs external backend internet neg add capabilities load balancing and connected networks view logs and metrics convert load balancer to ipv6 passthrough network load balancer tcp udp overview external load balancer regional load balancer backend service based architecture traffic distribution concepts target pool based architecture set up a load balancer vm instance group backends tcp udp only vm instance group backends multiple protocols zonal neg backends target pool based load balancer add capabilities configure failover configure weighted load balancing migrate from target pools to backend services service directory registration explore tutorials use udp with network load balancers monitor and troubleshoot view logs and metrics troubleshooting internal load balancer architecture overview traffic distribution concepts set up load balancer terraform examples vm instance group backends vm instance group backend for multiple protocols zonal neg backends add capabilities configure failover zonal affinity load balancers as next hops overview set up load balancing for third party appliances forwarding rules that use a common ip address service directory registration load balancing and connected networks explore tutorials set up load balancer as next hop with tags deploy a hub and spoke network set up a load balancer with internal ipv6 only backends monitor and troubleshoot view logs and metrics troubleshooting protocol forwarding overview set up protocol forwarding switch between a target instance and a backend service secure ssl certificates overview use self managed ssl certificates use google managed ssl certificates encryption to the backends troubleshooting ssl policies overview use ssl policies mutual tls frontend mtls overview set up frontend mtls with user provided certificates set up frontend mtls with a private ca backend mtls overview set up backend authenticated tls set up backend mtls backend mtls with managed workload identity overview set up backend mtls using managed workload identity post quantum tls authorization policies overview set up authorization policies customize load balancer advanced load balancing optimizations backend buckets backend services connection draining firewall rules forwarding rules health checks overview use health checks internal dns names ipv6 network endpoint groups overview hybrid connectivity negs internet negs serverless negs zonal negs overview set up zonal negs proxy only subnets tags target pools target proxies url maps overview use url maps url map size and quota units operate and maintain audit logging information health check logging information clean up a load balancer setup ai and ml application development application hosting compute data analytics and pipelines databases distributed hybrid and multicloud industry solutions migration networking observability and monitoring security storage access and resources management costs and usage management infrastructure as code sdk languages frameworks and tools home documentation networking load balancing guides send feedback choose a load balancer stay organized with collections save and categorize content based on your preferences this document helps you determine which google cloud load balancer best meets your needs to see an overview of all the cloud load balancing products available see cloud load balancing overview to determine which cloud load balancing product to use you must first determine the traffic type that your load balancers must handle choose an application load balancer when you need a flexible feature set for your applications with http s traffic choose a proxy network load balancer to implement tcp proxy load balancing to backends in one or more regions choose a passthrough network load balancer to preserve client source ip addresses avoid the overhead of proxies and to support additional protocols like udp esp and icmp you can further narrow down your choices depending on your application s requirements whether your application is external internet facing or internal and whether you need backends deployed globally or regionally the following diagram summarizes all the available deployment modes for cloud load balancing choose a load balancer click to enlarge 1 global external application load balancers support two modes of operation global and classic 2 global external proxy network load balancers support two modes of operation global and classic 3 passthrough network load balancers preserve client source ip addresses passthrough network load balancers also support additional protocols like udp esp and icmp load balancing aspects to decide which load balancer best suits your implementation of google cloud consider the following aspects of cloud load balancing traffic type external versus internal load balancing global versus regional load balancing premium versus standard network service tiers proxy versus passthrough load balancing traffic type the type of traffic that you need your load balancer to handle is another factor in determining which load balancer to use load balancer type traffic type application load balancers http or https passthrough network load balancers tcp or udp these load balancers also support other ip protocol traffic such as esp gre icmp and icmpv6 proxy network load balancers tcp with optional ssl offload external versus internal load balancing google cloud load balancers can be deployed as external or internal load balancers external load balancers distribute traffic that comes from the internet to your google cloud virtual private cloud vpc network internal load balancers distribute traffic that comes from clients in the same vpc network as the load balancer or clients connected to your vpc network by using vpc network peering cloud vpn or cloud interconnect to determine which load balancer works for your application use the summary table global versus regional load balancing depending on the type of traffic you need the load balancer to handle and whether your clients are internal or external you might have the option to choose between either a global load balancer or a regional load balancer choose a global load balancer or cross region load balancer when you want the load balancer to be distributed globally or span multiple regions such load balancers can also distribute traffic to backends across multiple regions making them suitable when your application or content is distributed across multiple regions or when you want the flexibility to add multi region backends as your application grows to new geographies only external load balancers are available as global load balancers for internal load balancers with backends in multiple regions choose the cross region load balancer cross region load balancers provide access by using a regional internal ip address that comes from the regional subnet in the vpc network this is different from global load balancers which provide access by using a single anycast ip address and by providing ipv6 termination at the load balancer review the following table to learn more choose a regional load balancer when you need backends in one region only you require only ipv4 termination not ipv6 or when you have jurisdictional compliance requirements for traffic to stay in a particular region workloads that require regionalized resources for compliance reasons mandate that certain resources must be kept in a specific region or require traffic to be terminated in a given region if you require geographic control over where tls is terminated you should use a regional load balancer a regional load balancer is deployed in a specific region that you choose and can connect to backends in the same region only thus regional load balancers guarantee that you terminate tls only in the region in which you ve deployed your load balancer and its backends global load balancers terminate transport layer security tls in locations that are distributed globally so as to minimize latency between clients and the load balancer load balancers are a critical component of most highly available applications it is important to understand that the resilience of your overall application depends not just on the scope of the load balancer you choose global or regional but also on the redundancy of your backend services the following table summarizes load balancer resilience based on the load balancer s distribution or scope load balancer scope architecture resilient to zonal outage resilient to regional outage global each load balancer is distributed across all regions cross region each load balancer is distributed across multiple regions regional each load balancer is distributed across multiple zones in the region an outage in a given region affects the regional load balancers in that region to determine which load balancer works for your application use the summary table proxy versus passthrough load balancing depending on the type of traffic you need the load balancer to handle and whether your clients are internal or external you might have the option to choose between either a proxy load balancer or a passthrough load balancer proxy load balancers terminate incoming client connections at the load balancer and then open new connections from the load balancer to the backends all the application load balancers and the proxy network load balancers work this way they terminate client connections by using either google front ends gfes or envoy proxies passthrough load balancers don t terminate client connections instead load balanced packets are received by backend vms with the packet s source destination and if applicable port information unchanged connections are then terminated by the backend vms responses from the backend vms go directly to the clients not back through the load balancer the term for this is direct server return use a passthrough load balancer when you need to preserve the client packet information as the name suggests the passthrough network load balancers come under this category to determine which load balancer works for your application use the summary table note proxy based load balancers send connections to the backends from different gfe or envoy ip addresses if you re using a form of authentication that relies on keeping track of the ip address that opened the first connection and expects that same ip address to open the second connection you might not want to use a proxy load balancer proxy load balancers don t preserve client ip addresses by default this type of authentication is more compatible with the passthrough load balancers for proxy load balancers such as the internal and external application load balancers we recommend that you use identity aware proxy iap as your authentication method instead premium versus standard network service tiers network service tiers lets you optimize connectivity between systems on the internet and your google cloud instances premium tier delivers traffic on google s premium backbone while standard tier uses regular isp networks as a general rule you d choose premium tier for high performance and low latency you can choose standard tier as a low cost alternative for applications that don t have strict requirements for latency or performance premium tier if the ip address of the load balancer is in the premium tier the traffic traverses google s high quality global backbone with the intent that packets enter and exit a google edge peering point as close as possible to the client if you don t specify a network tier your load balancer defaults to using the premium tier certain external load balancers such as the global external application load balancer and the global external proxy network load balancer can only be configured in premium tier all the internal load balancers always use google s high quality global backbone and are therefore always configured to be premium tier by default however the internet egress charges associated with premium tier don t apply to internal load balancer traffic standard tier if the ip address of the load balancer is in the standard tier the traffic enters and exits the google network at a peering point closest to the google cloud region where the load balancer is configured as noted in the summary table not all load balancers can ...