asn.dev

Observed topology

AS132996 THREESAINFOWAY-AS Threesa Infoway Pvt.Ltd.

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS132996: 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,021
AS133296Web Werks India Pvt. Ltd.ResidentialIPv4735
AS24482SG.GSHostingIPv4 IPv637

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS151750K-anandraj Inet Solutions Private LimitedUnclassifiedIPv4 IPv6817
AS135728Threesa Infonet Private LimitedResidentialIPv4 IPv6400
AS135721NetworkUnclassifiedIPv4244
AS151753NETWAY INFOTECH PRIVATE LIMITEDUnclassifiedIPv4122

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9583Sify LimitedUnclassifiedIPv4 IPv62,004
AS133296Web Werks India Pvt. Ltd.ResidentialIPv4 IPv61,302
AS151750K-anandraj Inet Solutions Private LimitedUnclassifiedIPv4 IPv6817
AS135728Threesa Infonet Private LimitedResidentialIPv4 IPv6400
AS135721NetworkUnclassifiedIPv4244
AS151753NETWAY INFOTECH PRIVATE LIMITEDUnclassifiedIPv4122
AS24482SG.GSHostingIPv4 IPv670

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.