asn.dev

Observed topology

AS137654 NETSTRA-AS-IN Netstra Communications Pvt Ltd

Unclassified APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS137654: 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
AS151170Netstra Communications Pvt LtdUnclassifiedIPv4 IPv6701
AS18229CtrlSHostingIPv4301
AS9498BHARTI Airtel Ltd.MobileIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS132563MegaHostZoneUnclassifiedIPv4 IPv6167
AS136692Nomura Research Institute Financial Technologies India Pvt. LtdUnclassifiedIPv436

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS151170Netstra Communications Pvt LtdUnclassifiedIPv4 IPv61,005
AS18229CtrlSHostingIPv4365
AS132563MegaHostZoneUnclassifiedIPv4 IPv6332
AS136692Nomura Research Institute Financial Technologies India Pvt. LtdUnclassifiedIPv436
AS9498BHARTI Airtel Ltd.MobileIPv43

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.