asn.dev

Observed topology

AS32002 RACKGENI

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS32002: 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 IPv6429
AS12129123.Net, Inc.HostingIPv4 IPv6221
AS174Cogent Communications, LLCTransitIPv4 IPv653
AS3257GTT Communications Inc.TransitIPv4 IPv632
AS20205Amplex Electric, Inc.ResidentialIPv43
AS34927iFog GmbHHostingIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS402212NicktronicIT LLCUnclassifiedIPv4 IPv6103
AS201726Andrew PalardyUnclassifiedIPv667
AS213607WORLD FIRST COMMUNICATION LTDUnclassifiedIPv465
AS401113RackGeniusUnclassifiedIPv637

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6605
AS12129123.Net, Inc.HostingIPv4 IPv6289
AS402212NicktronicIT LLCUnclassifiedIPv4 IPv6103
AS174Cogent Communications, LLCTransitIPv4 IPv669
AS201726Andrew PalardyUnclassifiedIPv667
AS213607WORLD FIRST COMMUNICATION LTDUnclassifiedIPv465
AS3257GTT Communications Inc.TransitIPv4 IPv643
AS401113RackGeniusUnclassifiedIPv637
AS20205Amplex Electric, Inc.ResidentialIPv44
AS34927iFog GmbHHostingIPv62

Provenance

Where this comes from

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