asn.dev

Observed topology

AS135872 GTPLKCBPL-AS GTPL KCBPL BROADBAND PVT LTD

Residential APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS135872: 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
AS55836Reliance Jio Infocomm LimitedMobileIPv41,652
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv4 IPv61,624
AS9498BHARTI Airtel Ltd.MobileIPv4267
AS35280F5 Networks SARLHostingIPv4 IPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS135214Spider Broadband Pvt. Ltd.UnclassifiedIPv4 IPv6514
AS135253Mft Internet Private LimitedResidentialIPv4 IPv6188
AS134302Oxynet Telecommunications Private LimitedUnclassifiedIPv4177

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv4 IPv62,419
AS55836Reliance Jio Infocomm LimitedMobileIPv41,736
AS135214Spider Broadband Pvt. Ltd.UnclassifiedIPv4 IPv6514
AS9498BHARTI Airtel Ltd.MobileIPv4267
AS135253Mft Internet Private LimitedResidentialIPv4 IPv6188
AS134302Oxynet Telecommunications Private LimitedUnclassifiedIPv4177
AS35280F5 Networks SARLHostingIPv4 IPv62

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.