asn.dev

Observed topology

AS32943 WEB-OF-NEVADA-01

Hosting ARIN Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS32943: 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 IPv641
AS32097WholeSale Internet, Inc.HostingIPv440
AS9002RETN LimitedUnclassifiedIPv43
AS24482SG.GSHostingIPv4 IPv62
AS34927iFog GmbHHostingIPv4 IPv62
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv62
AS293ESnetUnclassifiedIPv41
AS3130RGnet OUUnclassifiedIPv41
AS7575Australian Academic and Research Network (AARNet)EducationIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS24381BGP.ExchangeHostingIPv4 IPv668

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv696
AS24381BGP.ExchangeHostingIPv4 IPv668
AS32097WholeSale Internet, Inc.HostingIPv446
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv66
AS9002RETN LimitedUnclassifiedIPv43
AS24482SG.GSHostingIPv4 IPv63
AS3130RGnet OUUnclassifiedIPv42
AS34927iFog GmbHHostingIPv4 IPv62
AS293ESnetUnclassifiedIPv41
AS7575Australian Academic and Research Network (AARNet)EducationIPv41

All 11 adjacent →

Provenance

Where this comes from

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