asn.dev

Observed topology

AS42487 VIALIS-MOSELLE Located in Metz, France

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 11

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.

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv6283
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv6194
AS6939Hurricane Electric LLCTransitIPv4 IPv6161
AS29467LUXNETWORK S.A.UnclassifiedIPv4 IPv6121
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv679
AS9002RETN LimitedUnclassifiedIPv67
AS50628Leonix Telecom SASUnclassifiedIPv47
AS34927iFog GmbHHostingIPv42
AS20766Association "Gitoyen"UnclassifiedIPv41
AS24482SG.GSHostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS204645REGIE MUNICIPALE D'ELECTRICITE DE CREUTZWALDUnclassifiedIPv4 IPv6217

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv6340
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv6247
AS204645REGIE MUNICIPALE D'ELECTRICITE DE CREUTZWALDUnclassifiedIPv4 IPv6217
AS6939Hurricane Electric LLCTransitIPv4 IPv6178
AS29467LUXNETWORK S.A.UnclassifiedIPv4 IPv6167
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6117
AS50628Leonix Telecom SASUnclassifiedIPv410
AS9002RETN LimitedUnclassifiedIPv67
AS34927iFog GmbHHostingIPv45
AS20766Association "Gitoyen"UnclassifiedIPv41

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.