asn.dev

Observed topology

AS136714 STAMPEDE-AS Stampede Communications Pvt. Ltd.

Unclassified APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS136714: 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
AS9583Sify LimitedUnclassifiedIPv4178
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv4 IPv6131
AS55410Vodafone Idea LtdMobileIPv4 IPv6119
AS9498BHARTI Airtel Ltd.MobileIPv459

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS134352ARIDE OCEAN INFOWAY PRIVATE LIMITEDUnclassifiedIPv4120
AS137680Tyche Digital Network Private LimitedUnclassifiedIPv4118

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9583Sify LimitedUnclassifiedIPv4306
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv4 IPv6239
AS134352ARIDE OCEAN INFOWAY PRIVATE LIMITEDUnclassifiedIPv4120
AS55410Vodafone Idea LtdMobileIPv4 IPv6119
AS137680Tyche Digital Network Private LimitedUnclassifiedIPv4118
AS9498BHARTI Airtel Ltd.MobileIPv461

Provenance

Where this comes from

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