asn.dev

Observed topology

AS134331 SLSPL-AS - Smartlink Solutions Pvt. Ltd.

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS134331: 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 LimitedUnclassifiedIPv4 IPv61,154
AS9498BHARTI Airtel Ltd.MobileIPv4708
AS35280F5 Networks SARLHostingIPv4 IPv611

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS132761Smartlink Solutions Pvt. Ltd.UnclassifiedIPv4586
AS132935Arjun Broadband Private LimitedResidentialIPv4107
AS150080Corecard Software India Private LimitedUnclassifiedIPv46

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9583Sify LimitedUnclassifiedIPv4 IPv61,680
AS9498BHARTI Airtel Ltd.MobileIPv4940
AS132761Smartlink Solutions Pvt. Ltd.UnclassifiedIPv4649
AS132935Arjun Broadband Private LimitedResidentialIPv4107
AS35280F5 Networks SARLHostingIPv4 IPv615
AS150080Corecard Software India Private LimitedUnclassifiedIPv46

Provenance

Where this comes from

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