Observed topology
AS2027 MilkyWan MilkyWan Association
Residential RIPE Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS2027: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS62000 | SERVERD SAS | Hosting | IPv4 IPv6 | 125 |
| AS35625 | Eurofiber France SAS | Hosting | IPv4 IPv6 | 94 |
| AS35280 | F5 Networks SARL | Hosting | IPv4 IPv6 | 51 |
| AS6696 | VERIXI SA | Unclassified | IPv4 IPv6 | 47 |
| AS60132 | Zoreole Group SARL | Hosting | IPv4 IPv6 | 29 |
| AS49434 | FBW NETWORKS SAS | Unclassified | IPv4 IPv6 | 27 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 8 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 8 |
| AS50628 | Leonix Telecom SAS | Unclassified | IPv4 IPv6 | 8 |
| AS204092 | Association GRIFON | Unclassified | IPv4 IPv6 | 8 |
Transit
Downstream networks
Networks for which AS2027 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS209097 | NETSYST SAS | Hosting | IPv4 IPv6 | 285 |
| AS206983 | Altilink SARL | Unclassified | IPv4 IPv6 | 205 |
| AS215097 | SYSTEM DYNAMICS SARL | Unclassified | IPv4 IPv6 | 123 |
| AS207372 | LUNEO Association | Unclassified | IPv4 IPv6 | 97 |
| AS214563 | CLAIS JONATHAN trading as Infranat | Unclassified | IPv4 IPv6 | 96 |
| AS201818 | InitRD SASU | Unclassified | IPv4 IPv6 | 75 |
| AS210851 | Nicolas Patouillard | Unclassified | IPv4 IPv6 | 74 |
| AS197551 | Ameos SARL | Hosting | IPv4 | 61 |
| AS200259 | association declaree | Unclassified | IPv4 IPv6 | 39 |
| AS212037 | Marc Provost | Unclassified | IPv6 | 36 |
Adjacency
Adjacent networks
Every AS seen directly next to AS2027 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS62000 | SERVERD SAS | Hosting | IPv4 IPv6 | 509 |
| AS35280 | F5 Networks SARL | Hosting | IPv4 IPv6 | 457 |
| AS209097 | NETSYST SAS | Hosting | IPv4 IPv6 | 347 |
| AS6696 | VERIXI SA | Unclassified | IPv4 IPv6 | 307 |
| AS35625 | Eurofiber France SAS | Hosting | IPv4 IPv6 | 214 |
| AS206983 | Altilink SARL | Unclassified | IPv4 IPv6 | 205 |
| AS60132 | Zoreole Group SARL | Hosting | IPv4 IPv6 | 179 |
| AS49434 | FBW NETWORKS SAS | Unclassified | IPv4 IPv6 | 142 |
| AS215097 | SYSTEM DYNAMICS SARL | Unclassified | IPv4 IPv6 | 123 |
| AS207372 | LUNEO Association | Unclassified | IPv4 IPv6 | 97 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-11 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 73.24M 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.