asn.dev

Observed topology

AS10947 WERCS-NET

Residential ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS10947: 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 IPv6762
AS6461Zayo BandwidthTransitIPv4169
AS394883VISTABEAMResidentialIPv442
AS3130RGnet OUUnclassifiedIPv49
AS24482SG.GSHostingIPv4 IPv68
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv68
AS9002RETN LimitedUnclassifiedIPv47
AS19092Zayo BandwidthUnclassifiedIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS397672Wyoming Wireless InternetUnclassifiedIPv4 IPv6177
AS394066The Chugwater Telephone CompanyUnclassifiedIPv4130
AS63215Sound & Cellular, Inc.UnclassifiedIPv465
AS17016Elevation Improvement Systems, LLCUnclassifiedIPv462

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv61,089
AS6461Zayo BandwidthTransitIPv4254
AS397672Wyoming Wireless InternetUnclassifiedIPv4 IPv6177
AS394066The Chugwater Telephone CompanyUnclassifiedIPv4130
AS63215Sound & Cellular, Inc.UnclassifiedIPv465
AS17016Elevation Improvement Systems, LLCUnclassifiedIPv462
AS394883VISTABEAMResidentialIPv454
AS3130RGnet OUUnclassifiedIPv413
AS24482SG.GSHostingIPv4 IPv610
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv610

All 12 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.