asn.dev

Observed topology

AS200993 NYANET NyaNet

Hosting RIPE Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS200993: 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
AS61400Start2 LLCUnclassifiedIPv4 IPv695
AS35598INETCOM CARRIER LLCUnclassifiedIPv64
AS62255BiMajLink d.o.o.UnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS199133Yanislav BasiukHostingIPv4 IPv6429
AS218569Viktor NesmeianovUnclassifiedIPv4 IPv694
AS213461Igor Andreevich NemtsovUnclassifiedIPv4 IPv691

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS199133Yanislav BasiukHostingIPv4 IPv6533
AS62255BiMajLink d.o.o.UnclassifiedIPv4 IPv6439
AS35598INETCOM CARRIER LLCUnclassifiedIPv4 IPv6280
AS61400Start2 LLCUnclassifiedIPv4 IPv695
AS218569Viktor NesmeianovUnclassifiedIPv4 IPv694
AS213461Igor Andreevich NemtsovUnclassifiedIPv4 IPv691
AS6939Hurricane Electric LLCTransitIPv63
AS8359MTS PJSCMobileIPv41

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.