asn.dev

Observed topology

AS209097 NETSYST NETSYST SAS

Hosting RIPE

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS209097: 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
AS2027MilkyWan AssociationResidentialIPv4 IPv6324
AS35625Eurofiber France SASHostingIPv4 IPv6173
AS6939Hurricane Electric LLCTransitIPv4 IPv6144
AS62000SERVERD SASHostingIPv4 IPv6142
AS174Cogent Communications, LLCTransitIPv4 IPv687
AS1299Arelion Sweden ABTransitIPv4 IPv681
AS24482SG.GSHostingIPv4 IPv622
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv622
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv622
AS204092Association GRIFONUnclassifiedIPv4 IPv622

All 11 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS208166ShopyMind SASUnclassifiedIPv4 IPv6194

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS2027MilkyWan AssociationResidentialIPv4 IPv6392
AS208166ShopyMind SASUnclassifiedIPv4 IPv6194
AS35625Eurofiber France SASHostingIPv4 IPv6193
AS62000SERVERD SASHostingIPv4 IPv6174
AS6939Hurricane Electric LLCTransitIPv4 IPv6172
AS174Cogent Communications, LLCTransitIPv4 IPv6103
AS1299Arelion Sweden ABTransitIPv4 IPv695
AS24482SG.GSHostingIPv4 IPv626
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv626
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv626

All 12 adjacent →

Provenance

Where this comes from

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