asn.dev

Observed topology

AS14630 INVESCO

Unclassified ARIN

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

Transit

Upstream networks

All 48

Networks observed carrying traffic for AS14630: 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 IPv6323
AS1299Arelion Sweden ABTransitIPv4 IPv6232
AS2914NTT America, Inc.TransitIPv4220
AS812Rogers Communications Canada Inc.MobileIPv4216
AS3356Level 3 Parent, LLCTransitIPv4179
AS3491PCCW Global (HK) Ltd.TransitIPv488
AS9498BHARTI Airtel Ltd.MobileIPv487
AS3758SingNetResidentialIPv4 IPv677
AS6461Zayo BandwidthTransitIPv464
AS174Cogent Communications, LLCTransitIPv4 IPv661

All 48 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 48

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6323
AS1299Arelion Sweden ABTransitIPv4 IPv6232
AS2914NTT America, Inc.TransitIPv4220
AS812Rogers Communications Canada Inc.MobileIPv4216
AS3356Level 3 Parent, LLCTransitIPv4179
AS3491PCCW Global (HK) Ltd.TransitIPv488
AS9498BHARTI Airtel Ltd.MobileIPv487
AS3758SingNetResidentialIPv4 IPv677
AS6461Zayo BandwidthTransitIPv464
AS174Cogent Communications, LLCTransitIPv4 IPv661

All 48 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-11 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.47M 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.