asn.dev

Observed topology

AS209710 LUMINE-AS SNRD NETWORKS LIMITED

Hosting RIPE

Upstreams 19 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 9
Adjacent (IPv6) 17
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 19

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 OUUnclassifiedIPv6135
AS52025ParadoxNetworks LimitedUnclassifiedIPv485
AS212895Johannes ErnstUnclassifiedIPv682
AS215638Cilix LimitedResidentialIPv667
AS216211CYBERVERSE LLCHostingIPv4 IPv653
AS14447Infinitron Internet LLCHostingIPv4 IPv635
AS16509Amazon.com, Inc.HostingIPv633
AS137409GSL Networks Pty LTDUnclassifiedIPv633
AS20473The Constant Company, LLCHostingIPv424
AS24482SG.GSHostingIPv68

All 19 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 KimUnclassifiedIPv674

Adjacency

Adjacent networks

All 23

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

ASNetworkTypeFamiliesPaths seen
AS11967Hop179 OUUnclassifiedIPv6135
AS52025ParadoxNetworks LimitedUnclassifiedIPv485
AS212895Johannes ErnstUnclassifiedIPv682
AS200983YoungSeo KimUnclassifiedIPv674
AS215638Cilix LimitedResidentialIPv667
AS6939Hurricane Electric LLCTransitIPv664
AS216211CYBERVERSE LLCHostingIPv4 IPv653
AS14447Infinitron Internet LLCHostingIPv4 IPv635
AS16509Amazon.com, Inc.HostingIPv633
AS137409GSL Networks Pty LTDUnclassifiedIPv633

All 23 adjacent →

Provenance

Where this comes from

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