asn.dev

Observed topology

AS135760 SPEDNT-AS - Speednet Unique Network Pvt Ltd

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS135760: 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 LimitedUnclassifiedIPv4400
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv4 IPv6296
AS24482SG.GSHostingIPv4 IPv612

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS142233KOLKATA SUN BROADBAND PRIVATE LIMITEDUnclassifiedIPv4174
AS150014GLOBNET BROADBAND SERVICE PRIVATE LIMITEDUnclassifiedIPv4 IPv6150
AS153264Stormnet Connect Private LimitedUnclassifiedIPv4 IPv648

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9583Sify LimitedUnclassifiedIPv4629
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv4 IPv6429
AS142233KOLKATA SUN BROADBAND PRIVATE LIMITEDUnclassifiedIPv4174
AS150014GLOBNET BROADBAND SERVICE PRIVATE LIMITEDUnclassifiedIPv4 IPv6150
AS153264Stormnet Connect Private LimitedUnclassifiedIPv4 IPv648
AS24482SG.GSHostingIPv4 IPv622

Provenance

Where this comes from

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