asn.dev

Observed topology

AS209650 ZHIYUAN-AS Zhiyuan Network

Upstreams 25 carry this network
Downstreams 0 this network carries
Adjacent (IPv4) 16
Adjacent (IPv6) 16

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS209650: 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
AS34927iFog GmbHHostingIPv4 IPv6100
AS20473The Constant Company, LLCHostingIPv4 IPv641
AS917Misaka Network, Inc.UnclassifiedIPv614
AS29632Netassist International EOODUnclassifiedIPv68
AS24482SG.GSHostingIPv4 IPv65
AS204092Association GRIFONUnclassifiedIPv4 IPv65
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv65
AS48185team.blue NVUnclassifiedIPv4 IPv65
AS57821Nonattached Network e.V.UnclassifiedIPv4 IPv65
AS33891Core-Backbone GmbHHostingIPv64
AS35487Misaka Network, Inc.UnclassifiedIPv64
AS58057Securebit AGUnclassifiedIPv63
AS38008Aperture Science LimitedUnclassifiedIPv42
AS23961Misaka Network, Inc.UnclassifiedIPv62
AS17639Converge ICT Solutions Inc.UnclassifiedIPv61
AS57463NetIX Communications JSCUnclassifiedIPv41
AS37721Virtual Technologies & SolutionsResidentialIPv41
AS34800Securebit AGUnclassifiedIPv41
AS212508Lowhosting services of Davide GennariUnclassifiedIPv41
AS6696VERIXI SAUnclassifiedIPv41
AS202365Omer GOLGELIUnclassifiedIPv41
AS20485Joint Stock Company TransTeleComUnclassifiedIPv41
AS34549meerfarbig GmbH & Co. KGHostingIPv61
AS153371BACK WAVES LIMITEDResidentialIPv61
AS37100SEACOM LimitedUnclassifiedIPv41

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.

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

32 shown

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

ASNetworkTypeFamiliesPaths seen
AS34927iFog GmbHHostingIPv4 IPv6100
AS20473The Constant Company, LLCHostingIPv4 IPv641
AS917Misaka Network, Inc.UnclassifiedIPv614
AS29632Netassist International EOODUnclassifiedIPv68
AS24482SG.GSHostingIPv4 IPv65
AS57821Nonattached Network e.V.UnclassifiedIPv4 IPv65
AS48185team.blue NVUnclassifiedIPv4 IPv65
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv65
AS204092Association GRIFONUnclassifiedIPv4 IPv65
AS35487Misaka Network, Inc.UnclassifiedIPv64
AS33891Core-Backbone GmbHHostingIPv64
AS58057Securebit AGUnclassifiedIPv63
AS23961Misaka Network, Inc.UnclassifiedIPv62
AS38008Aperture Science LimitedUnclassifiedIPv42
AS153371BACK WAVES LIMITEDResidentialIPv61
AS37100SEACOM LimitedUnclassifiedIPv41
AS20485Joint Stock Company TransTeleComUnclassifiedIPv41
AS6696VERIXI SAUnclassifiedIPv41
AS37721Virtual Technologies & SolutionsResidentialIPv41
AS202365Omer GOLGELIUnclassifiedIPv41
AS212508Lowhosting services of Davide GennariUnclassifiedIPv41
AS34800Securebit AGUnclassifiedIPv41
AS34549meerfarbig GmbH & Co. KGHostingIPv61
AS17639Converge ICT Solutions Inc.UnclassifiedIPv61
AS57463NetIX Communications JSCUnclassifiedIPv41

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.

Interconnection

Exchange presence

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS209650, largest fabric first. An exchange is shared switching where networks interconnect directly rather than paying a transit provider to carry traffic between them, so turning up at one is a deliberate choice about how this network wants to be reached. Each name opens that exchange's own page, with its peering LANs and every other network recorded on it. Recorded at 5 exchanges across 2 countries and 1 region.

ExchangeLocationTheir addressMember ports
Neutral Internet ExchangeAmsterdam, Netherlands193.239.118.220665
KleyReX Internet ExchangeFrankfurt, Germany193.189.83.67475
Speed Internet ExchangeDronten, Netherlands185.1.222.157292
DE-CIX DusseldorfDüsseldorf, Germany185.1.170.144226
Local Internet Exchange NetherlandsMeppel, Netherlands185.1.138.2957

Unlike the tables above, this is recorded rather than inferred. An address on a peering LAN is at that exchange by definition. Two carve-outs all the same. Member ports counts every participant at the exchange, not this network's ports, so read it as a size proxy. And an absent exchange means PCH has no record of it, not that the network is not there.

Provenance

Where this comes from

Derived from routing tables collected at 2026-08-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.02M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.

Exchange presence comes from a separate dataset: the directory collected 2026-08-09 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,164 recorded member ports, licensed CC BY-NC-SA 3.0.

PeeringDB is the better-known directory and is deliberately not the source here: its acceptable-use policy forbids the bulk storage this needs. The two answer different questions anyway. PeeringDB reports what an operator declares about itself; this reports what PCH has recorded.