asn.dev

Observed topology

AS16591 GOOGLE-FIBER - Google Fiber Inc.

Residential ARIN Cable/DSL/ISP

Upstreams 9 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 10
Adjacent (IPv6) 6
Upstream graph Who carries AS16591, and who carries them, drawn as a map up to the transit-free core. 16 exchanges Where AS16591 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS16591: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv68,108
AS9002RETN LimitedUnclassifiedIPv42,121
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv61,465
AS3356Level 3 Parent, LLCTransitIPv41,416
AS577Bell CanadaMobileIPv4376
AS852TELUS Communications Inc.ResidentialIPv4 IPv6342
AS14907Wikimedia Foundation Inc.HostingIPv4 IPv6342
AS52025ParadoxNetworks LimitedUnclassifiedIPv4189
AS6327Shaw CommunicationsResidentialIPv4188

Transit

Downstream networks

inferred

Networks for which AS16591 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS19165Webpass Inc.ResidentialIPv4 IPv61,520

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS16591 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv69,405
AS9002RETN LimitedUnclassifiedIPv4 IPv62,129
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv61,623
AS19165Webpass Inc.ResidentialIPv4 IPv61,520
AS3356Level 3 Parent, LLCTransitIPv41,416
AS577Bell CanadaMobileIPv4376
AS14907Wikimedia Foundation Inc.HostingIPv4 IPv6372
AS852TELUS Communications Inc.ResidentialIPv4 IPv6369
AS52025ParadoxNetworks LimitedUnclassifiedIPv4189
AS6327Shaw CommunicationsResidentialIPv4188

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.00M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.