asn.dev

Observed topology

AS197817 NYCO-CLOUD-NETWORK

Unclassified APNIC

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS197817: 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 LLCTransitIPv6117
AS205369LI YIRANUnclassifiedIPv673
AS204211Shanghai Yingyun Network Technology Co., Ltd.UnclassifiedIPv4 IPv665
AS206069Cornseed LimitedResidentialIPv657
AS215172JIANYUELAB LTDResidentialIPv637
AS199310XIN BING XIANHostingIPv615
AS51087Bling Network LtdUnclassifiedIPv66
AS44324MoeDove LLCResidentialIPv65
AS24482SG.GSHostingIPv64
AS401753BIXCE IncUnclassifiedIPv64

All 11 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS219489Zhengda LiUnclassifiedIPv6101

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS206069Cornseed LimitedResidentialIPv6120
AS6939Hurricane Electric LLCTransitIPv6117
AS219489Zhengda LiUnclassifiedIPv6101
AS205369LI YIRANUnclassifiedIPv675
AS215172JIANYUELAB LTDResidentialIPv673
AS204211Shanghai Yingyun Network Technology Co., Ltd.UnclassifiedIPv4 IPv665
AS199310XIN BING XIANHostingIPv615
AS51087Bling Network LtdUnclassifiedIPv66
AS44324MoeDove LLCResidentialIPv65
AS24482SG.GSHostingIPv64

All 12 adjacent →

Provenance

Where this comes from

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