asn.dev

Observed topology

AS30132 ISC-F-AS

Unclassified ARIN

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

Transit

Upstream networks

All 20

Networks observed carrying traffic for AS30132: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6172
AS1299Arelion Sweden ABTransitIPv4 IPv631
AS20562Broadband Hosting B.V.HostingIPv46
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv65
AS24482SG.GSHostingIPv4 IPv65
AS48185team.blue NVUnclassifiedIPv4 IPv65
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv65
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv65
AS204092Association GRIFONUnclassifiedIPv4 IPv65
AS29632Netassist International EOODUnclassifiedIPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS3557Internet Systems Consortium, Inc.UnclassifiedIPv4 IPv662

Adjacency

Adjacent networks

All 21

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6220
AS3557Internet Systems Consortium, Inc.UnclassifiedIPv4 IPv662
AS1299Arelion Sweden ABTransitIPv4 IPv638
AS12859BIT BVHostingIPv4 IPv610
AS20562Broadband Hosting B.V.HostingIPv46
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv65
AS24482SG.GSHostingIPv4 IPv65
AS48185team.blue NVUnclassifiedIPv4 IPv65
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv65
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv65

Provenance

Where this comes from

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