On Tue, Dec 5, 2023 at 5:09 PM Tom Beecher <beec...@beecher.cc> wrote: >> >> 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. >
sure, good enough :) (I have not looked at our config in a bit to be sure) > On Tue, Dec 5, 2023 at 1:29 PM Christopher Morrow <morrowc.li...@gmail.com> > wrote: >> >> On Tue, Dec 5, 2023 at 11:06 AM Tom Beecher <beec...@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.wea...@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 >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >>
