Observed topology
AS42487 VIALIS-MOSELLE Located in Metz, France
Residential RIPE Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS42487: 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 |
|---|---|---|---|---|
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 283 |
| AS8218 | Zayo Infrastructure France SA | Unclassified | IPv4 IPv6 | 194 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 161 |
| AS29467 | LUXNETWORK S.A. | Unclassified | IPv4 IPv6 | 121 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 IPv6 | 79 |
| AS9002 | RETN Limited | Unclassified | IPv6 | 7 |
| AS50628 | Leonix Telecom SAS | Unclassified | IPv4 | 7 |
| AS34927 | iFog GmbH | Hosting | IPv4 | 2 |
| AS20766 | Association "Gitoyen" | Unclassified | IPv4 | 1 |
| AS24482 | SG.GS | Hosting | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS42487 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS204645 | REGIE MUNICIPALE D'ELECTRICITE DE CREUTZWALD | Unclassified | IPv4 IPv6 | 217 |
Adjacency
Adjacent networks
Every AS seen directly next to AS42487 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 340 |
| AS8218 | Zayo Infrastructure France SA | Unclassified | IPv4 IPv6 | 247 |
| AS204645 | REGIE MUNICIPALE D'ELECTRICITE DE CREUTZWALD | Unclassified | IPv4 IPv6 | 217 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 178 |
| AS29467 | LUXNETWORK S.A. | Unclassified | IPv4 IPv6 | 167 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 IPv6 | 117 |
| AS50628 | Leonix Telecom SAS | Unclassified | IPv4 | 10 |
| AS9002 | RETN Limited | Unclassified | IPv6 | 7 |
| AS34927 | iFog GmbH | Hosting | IPv4 | 5 |
| AS20766 | Association "Gitoyen" | Unclassified | IPv4 | 1 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-17 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.18M 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.