asn.dev

Observed topology

AS200936 GUO-AS Chengjie Guo

Unclassified RIPE Educational/Research

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS200936: 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 GmbHHostingIPv6106
AS38008Aperture Science LimitedUnclassifiedIPv637
AS53667FranTech SolutionsHostingIPv637
AS215467Skhron OUHostingIPv637
AS44324MoeDove LLCResidentialIPv636
AS8772Netassist International EOODUnclassifiedIPv633
AS53356Free Range Cloud Hosting Inc.HostingIPv633
AS7720Skywolf Technology LLCUnclassifiedIPv631
AS20473The Constant Company, LLCHostingIPv631
AS207108AH CLOUD LTDHostingIPv620

All 13 upstreams →

Transit

Downstream networks

inferred

Networks for which AS200936 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

All 13

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

ASNetworkTypeFamiliesPaths seen
AS34927iFog GmbHHostingIPv6106
AS38008Aperture Science LimitedUnclassifiedIPv637
AS53667FranTech SolutionsHostingIPv637
AS215467Skhron OUHostingIPv637
AS44324MoeDove LLCResidentialIPv636
AS8772Netassist International EOODUnclassifiedIPv633
AS53356Free Range Cloud Hosting Inc.HostingIPv633
AS7720Skywolf Technology LLCUnclassifiedIPv631
AS20473The Constant Company, LLCHostingIPv631
AS207108AH CLOUD LTDHostingIPv620

All 13 adjacent →

Provenance

Where this comes from

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