asn.dev

Observed topology

AS133712 SPECTRACLOUD-AS - Spectra Technologies India Private Limited

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS133712: 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
AS9498BHARTI Airtel Ltd.MobileIPv41,298
AS59796StormWall s.r.o.UnclassifiedIPv4179
AS137085ANONET COMMUNICATIONS PVT LTDUnclassifiedIPv4 IPv677
AS55410Vodafone Idea LtdMobileIPv457
AS18229CtrlSHostingIPv437
AS43298Storm Networks LLCUnclassifiedIPv46

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS141825EXTREME COMPUTE TECHNOLOGIES PRIVATE LIMITEDUnclassifiedIPv4190

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9498BHARTI Airtel Ltd.MobileIPv41,488
AS141825EXTREME COMPUTE TECHNOLOGIES PRIVATE LIMITEDUnclassifiedIPv4190
AS59796StormWall s.r.o.UnclassifiedIPv4179
AS137085ANONET COMMUNICATIONS PVT LTDUnclassifiedIPv4 IPv677
AS55410Vodafone Idea LtdMobileIPv457
AS18229CtrlSHostingIPv437
AS43298Storm Networks LLCUnclassifiedIPv46

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.