asn.dev

Observed topology

AS17466 GENPACT-AS-AP Genpact India Private Limited

Unclassified DROP-listed space APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS17466: 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
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv4654
AS55836Reliance Jio Infocomm LimitedMobileIPv4199
AS9299Philippine Long Distance Telephone CompanyUnclassifiedIPv4197
AS3356Level 3 Parent, LLCTransitIPv4180
AS9498BHARTI Airtel Ltd.MobileIPv4179
AS6181Cincinnati Bell Telephone Company LLCResidentialIPv466
AS55410Vodafone Idea LtdMobileIPv460
AS3257GTT Communications Inc.TransitIPv43
AS17639Converge ICT Solutions Inc.UnclassifiedIPv41

Transit

Downstream networks

inferred

Networks for which AS17466 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

observed

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

ASNetworkTypeFamiliesPaths seen
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv4654
AS55836Reliance Jio Infocomm LimitedMobileIPv4199
AS9299Philippine Long Distance Telephone CompanyUnclassifiedIPv4197
AS3356Level 3 Parent, LLCTransitIPv4180
AS9498BHARTI Airtel Ltd.MobileIPv4179
AS6181Cincinnati Bell Telephone Company LLCResidentialIPv466
AS55410Vodafone Idea LtdMobileIPv460
AS3257GTT Communications Inc.TransitIPv43
AS17639Converge ICT Solutions Inc.UnclassifiedIPv41

Provenance

Where this comes from

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