asn.dev

Observed topology

AS17465 ASIANET Cable ISP in India

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS17465: 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
AS9498BHARTI Airtel Ltd.MobileIPv4 IPv612,106
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv4 IPv66,608
AS9730Bharti Telesonic LtdUnclassifiedIPv4 IPv6627
AS18229CtrlSHostingIPv465
AS35280F5 Networks SARLHostingIPv4 IPv612

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS137624Ebenezar Communications Private LimitedUnclassifiedIPv4236
AS142470SREEDEVI COMMUNICATIONS PRIVATE LIMITEDUnclassifiedIPv4 IPv6138
AS146865Sporada Technologies India Private LimitedUnclassifiedIPv4120
AS138279Onepipe Telecom Pvt LtdUnclassifiedIPv459

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9498BHARTI Airtel Ltd.MobileIPv4 IPv612,716
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv4 IPv66,728
AS9730Bharti Telesonic LtdUnclassifiedIPv4 IPv6627
AS137624Ebenezar Communications Private LimitedUnclassifiedIPv4236
AS138279Onepipe Telecom Pvt LtdUnclassifiedIPv4236
AS142470SREEDEVI COMMUNICATIONS PRIVATE LIMITEDUnclassifiedIPv4 IPv6138
AS146865Sporada Technologies India Private LimitedUnclassifiedIPv4120
AS18229CtrlSHostingIPv465
AS35280F5 Networks SARLHostingIPv4 IPv612

Provenance

Where this comes from

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