asn.dev

Observed topology

AS202782 EverLink-AS Yaoheng Digital (Shanghai) Technology Co., Ltd.

Hosting RIPE Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS202782: 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 LLCTransitIPv662
AS3204xTom OUHostingIPv64
AS24482SG.GSHostingIPv62
AS34549meerfarbig GmbH & Co. KGHostingIPv62
AS56662Marcin GondekUnclassifiedIPv62
AS401753BIXCE IncUnclassifiedIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS199310XIN BING XIANHostingIPv4 IPv6180
AS60539Huicast Telecom LimitedUnclassifiedIPv459
AS44324MoeDove LLCResidentialIPv620

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS199310XIN BING XIANHostingIPv4 IPv6289
AS6939Hurricane Electric LLCTransitIPv4 IPv6267
AS3204xTom OUHostingIPv4 IPv6162
AS60539Huicast Telecom LimitedUnclassifiedIPv459
AS44324MoeDove LLCResidentialIPv652
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv622
AS24482SG.GSHostingIPv4 IPv67
AS401753BIXCE IncUnclassifiedIPv4 IPv67
AS56662Marcin GondekUnclassifiedIPv65
AS31500Global Network Management IncUnclassifiedIPv42

All 11 adjacent →

Provenance

Where this comes from

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