gcp · us-central2

Google Cloud uses 14 prefixes for us-central2.

Short answer

Google Cloud lists these prefixes under “us-central2”. Google Cloud publishes cloud.json: the external address ranges available to Google Cloud customers, with the region (scope) each one is used in.

IPv4 prefixes12
IPv6 prefixes2
Regions in the first 100us-central2
Fetched by peekip3 Nov 2026

Prefixes

PrefixRegion / locationService
107.167.160.0/20us-central2us-central2
108.59.88.0/21us-central2us-central2
136.73.0.0/16us-central2us-central2
173.255.120.0/21us-central2us-central2
34.183.115.0/24us-central2us-central2
34.184.116.0/24us-central2us-central2
34.22.0.0/19us-central2us-central2
35.186.0.0/17us-central2us-central2
35.186.128.0/20us-central2us-central2
35.206.32.0/19us-central2us-central2
35.220.46.0/24us-central2us-central2
35.242.46.0/24us-central2us-central2
2600:1900:4070::/44us-central2us-central2
2600:1902:220::/44us-central2us-central2
Showing 14 of 14 prefixes All prefixes (CSV)

What changed

No prefixes added or removed since we started tracking this list. Changes appear here the day after the provider publishes them.

Allowlist formats

nginx (first 5 prefixes)
allow 107.167.160.0/20;
allow 108.59.88.0/21;
allow 136.73.0.0/16;
allow 173.255.120.0/21;
allow 34.183.115.0/24;
deny all;
iptables (first 5 prefixes)
iptables -A INPUT -s 107.167.160.0/20 -j ACCEPT
iptables -A INPUT -s 108.59.88.0/21 -j ACCEPT
iptables -A INPUT -s 136.73.0.0/16 -j ACCEPT
iptables -A INPUT -s 173.255.120.0/21 -j ACCEPT
iptables -A INPUT -s 34.183.115.0/24 -j ACCEPT

Generate the full list from the CSV, and refresh it on a schedule: providers add and retire prefixes often.

Sources

  1. Google Cloud: published IP ranges · checked 3 Nov 2026
  2. Google Cloud documentation