asn.dev

Observed topology

AS135724 PVTABNL-AS Allnet Broadband Network Pvt Ltd

Residential APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS135724: 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
AS56268Northeast Dataa Network Pvt LtdUnclassifiedIPv4991
AS9498BHARTI Airtel Ltd.MobileIPv4 IPv6128
AS150008Pioneer Elabs Ltd.UnclassifiedIPv480
AS24482SG.GSHostingIPv4 IPv615

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS142454IT SPECTRUM MEDIA PVT LTDUnclassifiedIPv4 IPv6398
AS142513LEVOTEL BIGNET SOLUTIONS PVT LTDUnclassifiedIPv4122

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS56268Northeast Dataa Network Pvt LtdUnclassifiedIPv41,181
AS142454IT SPECTRUM MEDIA PVT LTDUnclassifiedIPv4 IPv6398
AS9498BHARTI Airtel Ltd.MobileIPv4 IPv6376
AS150008Pioneer Elabs Ltd.UnclassifiedIPv4 IPv6157
AS142513LEVOTEL BIGNET SOLUTIONS PVT LTDUnclassifiedIPv4122
AS24482SG.GSHostingIPv4 IPv620

Provenance

Where this comes from

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