asn.dev

Observed topology

AS32181 ASN-GIGENET - GigeNET

Hosting ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS32181: 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
AS6461Zayo BandwidthTransitIPv4 IPv6752
AS174Cogent Communications, LLCTransitIPv4 IPv6583
AS6939Hurricane Electric LLCTransitIPv4 IPv6433
AS3257GTT Communications Inc.TransitIPv4 IPv6306
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv6304
AS24482SG.GSHostingIPv4 IPv636
AS852TELUS Communications Inc.ResidentialIPv4 IPv620
AS37721Virtual Technologies & SolutionsResidentialIPv413

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS23522GigeNETHostingIPv4458
AS204957ROUTE 95 LLCUnclassifiedIPv4 IPv6147
AS25720Honeycomb Internet ServicesHostingIPv4114
AS395558Garden State Computing LLCUnclassifiedIPv458

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv4 IPv61,014
AS174Cogent Communications, LLCTransitIPv4 IPv6760
AS6939Hurricane Electric LLCTransitIPv4 IPv6545
AS23522GigeNETHostingIPv4458
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv6413
AS3257GTT Communications Inc.TransitIPv4 IPv6396
AS204957ROUTE 95 LLCUnclassifiedIPv4 IPv6147
AS25720Honeycomb Internet ServicesHostingIPv4114
AS395558Garden State Computing LLCUnclassifiedIPv458
AS24482SG.GSHostingIPv4 IPv650

All 12 adjacent →

Provenance

Where this comes from

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