Regional vs Global Dynamic Routing Mode in Google Cloud

GCP Study Hub
November 16, 2026

A VPC network's dynamic routing mode controls how far Cloud Router's routes reach. In regional mode, a Cloud Router's learned routes and default advertisements stay within its own region. In global mode, each Cloud Router applies its learned routes to every region in the network and advertises subnets from all regions. A VPC network created with default settings uses regional dynamic routing, so global mode is a deliberate change, and many hybrid designs on the Professional Cloud Network Engineer exam depend on it.

Regional dynamic routing

In regional mode, routes a Cloud Router learns over BGP are only programmed for VMs in the same region as the Cloud Router. In default advertisement mode, the router also advertises only its own region's subnets to the peer. Both effects matter at once. A VM in another region has no learned route toward on-premises, and the on-premises network never learns that VM's subnet, so traffic fails in both directions.

Global dynamic routing

In global mode, each Cloud Router applies the routes it learns to every region in the network, and its default advertisement includes subnets from all regions. One Cloud Router can therefore carry hybrid traffic for the whole network. The mode affects both directions together: where the learned on-premises routes are programmed, and which subnets the default advertisement includes.

Route advertisements and the routing mode solve different problems. An advertisement, default or custom, controls only what the BGP peer learns. It doesn't change where the routes the Cloud Router learns are programmed inside the VPC network, which is the job of the dynamic routing mode. In regional mode, the routes from every BGP session on a Cloud Router are programmed only in that router's region.

When global dynamic routing is required

Global dynamic routing is required whenever hybrid paths in one region must serve workloads in another. Typical cases include:

  • An HA VPN connection in one region backing up a Cloud Interconnect connection in another region.
  • The 99.99% Cloud Interconnect topology, where Cloud Routers in two regions must advertise and learn routes for the whole network.
  • A Cross-Cloud Interconnect connection whose attachments sit in the location's region while the workloads that use it run in a distant region.
  • One HA VPN pair serving workloads in two regions.

The primary and backup case also involves route priority. Google Cloud prefers the route with the lowest priority value, and when a route learned in one region is used from another region, an inter-region cost is added to it. The primary path's advertised route priority therefore has to stay below the backup's even after that cost is added. Cloud Router sends its advertised route priority to on-premises as MED, so on-premises routers that have no other attribute differences to compare make the matching choice.

For Professional Cloud Network Engineer scenarios, a quick check is whether the hybrid connection and the workloads that use it share a region. If they don't, regional mode leaves those workloads without the learned routes.

Where global dynamic routing doesn't help

  • It doesn't let a regional internal load balancer accept clients from other regions.
  • It has no effect on internet clients reaching a load balancer.
  • It changes nothing when the Cloud Router and the destination, such as a Cloud SQL instance, are already in the same region. A router in regional mode still sees every subnet in its own region.
  • It doesn't let a NAT gateway in one region translate traffic from VMs in another region.

Our Professional Cloud Network Engineer practice exams cover dynamic routing modes alongside custom route advertisements and Cloud Interconnect SLA topologies, with detailed explanations that drill these distinctions.

Get tips and updates from GCP Study Hub

arrow