asn.dev

Observed topology

AS209710 SNRD-AS SNRD Networks

Hosting RIPE Content

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

Transit

Upstream networks

All 18

Networks observed carrying traffic for AS209710: 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
AS11967Hop179 OUUnclassifiedIPv6158
AS52025ParadoxNetworks LimitedUnclassifiedIPv488
AS212895Johannes ErnstUnclassifiedIPv685
AS215638Cilix LimitedResidentialIPv653
AS216211CYBERVERSE LLCHostingIPv4 IPv652
AS14447Infinitron Internet LLCHostingIPv4 IPv637
AS16509Amazon.com, Inc.HostingIPv634
AS137409GSL Networks Pty LTDUnclassifiedIPv634
AS20473The Constant Company, LLCHostingIPv425
AS24482SG.GSHostingIPv68

All 18 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS200983YoungSeo KimUnclassifiedIPv676

Adjacency

Adjacent networks

All 22

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

ASNetworkTypeFamiliesPaths seen
AS11967Hop179 OUUnclassifiedIPv6158
AS52025ParadoxNetworks LimitedUnclassifiedIPv488
AS212895Johannes ErnstUnclassifiedIPv685
AS200983YoungSeo KimUnclassifiedIPv676
AS6939Hurricane Electric LLCTransitIPv666
AS215638Cilix LimitedResidentialIPv653
AS216211CYBERVERSE LLCHostingIPv4 IPv652
AS14447Infinitron Internet LLCHostingIPv4 IPv637
AS16509Amazon.com, Inc.HostingIPv634
AS137409GSL Networks Pty LTDUnclassifiedIPv634

All 22 adjacent →

Provenance

Where this comes from

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