asn.dev

Observed topology

AS32881 SERVERNORTH

Hosting ARIN NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS32881: 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
AS5645TekSavvy Solutions, Inc.ResidentialIPv4156
AS11666Nexicom Inc.ResidentialIPv4133
AS6461Zayo BandwidthTransitIPv4100
AS10929eStruxture Data Centers Inc.HostingIPv459
AS6939Hurricane Electric LLCTransitIPv424
AS1403EBOXResidentialIPv4 IPv616
AS22652Videotron LteeResidentialIPv414
AS24482SG.GSHostingIPv47
AS36236NetActuate, IncHostingIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS399230Community Fibre Company, IncUnclassifiedIPv416

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS5645TekSavvy Solutions, Inc.ResidentialIPv4156
AS11666Nexicom Inc.ResidentialIPv4133
AS6461Zayo BandwidthTransitIPv4100
AS10929eStruxture Data Centers Inc.HostingIPv459
AS6939Hurricane Electric LLCTransitIPv438
AS1403EBOXResidentialIPv4 IPv618
AS399230Community Fibre Company, IncUnclassifiedIPv416
AS22652Videotron LteeResidentialIPv414
AS24482SG.GSHostingIPv47
AS36236NetActuate, IncHostingIPv61

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.