asn.dev

Observed topology

AS132335 LEAPSWITCH-IN-AS-AP LEAPSWITCH NETWORKS PRIVATE LIMITED

Hosting DROP-listed space APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS132335: 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
AS133296Web Werks India Pvt. Ltd.ResidentialIPv4 IPv61,482
AS13335Cloudflare, Inc.HostingIPv41,339
AS146943Tier 4 Cloud ServicesHostingIPv4 IPv6183
AS208367CSpace Hostings OUResidentialIPv4116
AS15085Immedion, LLCHostingIPv460
AS24482SG.GSHostingIPv44

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS213550Jon RadelUnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS133296Web Werks India Pvt. Ltd.ResidentialIPv4 IPv61,483
AS13335Cloudflare, Inc.HostingIPv41,339
AS146943Tier 4 Cloud ServicesHostingIPv4 IPv6183
AS208367CSpace Hostings OUResidentialIPv4116
AS15085Immedion, LLCHostingIPv460
AS24482SG.GSHostingIPv44
AS213550Jon RadelUnclassifiedIPv41

Provenance

Where this comes from

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