asn.dev

Observed topology

AS976 CORENET

Residential ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS976: 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
AS18013ASLINE LIMITEDHostingIPv4 IPv6494
AS134176Cloudie LimitedUnclassifiedIPv4 IPv6380
AS40065CNSERVERS LLCHostingIPv441
AS917Misaka Network, Inc.UnclassifiedIPv632
AS9400CoreNET Inc.UnclassifiedIPv632

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS38324NetPilot LimitedResidentialIPv4354
AS133617NetPilot LimitedUnclassifiedIPv664
AS216173Guozhen LiuUnclassifiedIPv664
AS38323Meifeng Advertising Co., Ltd.UnclassifiedIPv632

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS18013ASLINE LIMITEDHostingIPv4 IPv61,040
AS134176Cloudie LimitedUnclassifiedIPv4 IPv6380
AS38324NetPilot LimitedResidentialIPv4354
AS9400CoreNET Inc.UnclassifiedIPv664
AS133617NetPilot LimitedUnclassifiedIPv664
AS216173Guozhen LiuUnclassifiedIPv664
AS40065CNSERVERS LLCHostingIPv441
AS917Misaka Network, Inc.UnclassifiedIPv632
AS38323Meifeng Advertising Co., Ltd.UnclassifiedIPv632

Provenance

Where this comes from

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