Any comprehensive listing of where Google's IPs originate from?

Tue Dec 5 22:08:54 UTC 2023

>
> i would expect that google announces the /16 at least from 'everywhere',
> yes.
>

I see the specific /18s Drew asked about initially. Didn't check for the
covering /16.

On Tue, Dec 5, 2023 at 1:29 PM Christopher Morrow <morrowc.lists at gmail.com>
wrote:

> On Tue, Dec 5, 2023 at 11:06 AM Tom Beecher <beecher at beecher.cc> wrote:
> >
> > From my observations, all us-east-5 IPs are announced via transit and
> peering at all of my locations Chicago and east.
> >
>
> i would expect that google announces the /16 at least from 'everywhere',
> yes.
>
> > On Mon, Dec 4, 2023 at 9:11 AM Drew Weaver <drew.weaver at thenap.com>
> wrote:
> >>
> >> Hello,
> >>
> >>
> >>
> >> We are trying to reduce latency to a region in Google Cloud which we
> are in the same city of. Latency is currently about 22ms rt for the traffic
> to go 9 miles.
> >>
> >>
> >>
> >> I am having the hardest time finding any comprehensive list of what
> exchanges, transit, etc their IP addresses are being announced over.
> >>
>
> 100% chance the best option is peeringdb ....(I'm betting closest to
> drew is chicago-land-ix-ville)
>
> >>
> >>
> >> Specifically trying to get closer to addresses in these prefixes:
> >>
> >>
> >>
> >> 34.162.192.0/18
> >>
> >> 34.162.64.0/18
> >>
> >>
> >>
> >> Any info is greatly appreciated.
> >>
> >>
> >>
> >> Thanks,
> >>
> >> -Drew
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20231205/6acdf403/attachment.html>