asn.dev

Observed topology

AS12727 VIALIS Colmar, France

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS12727: 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 IPv6251
AS6939Hurricane Electric LLCTransitIPv4 IPv6239
AS15557SFR SAResidentialIPv433
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv629
AS24482SG.GSHostingIPv4 IPv68
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv68
AS37721Virtual Technologies & SolutionsResidentialIPv46
AS9002RETN LimitedUnclassifiedIPv64
AS25091IP-Max SAUnclassifiedIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS208574Communaute de Communes du Pays de BitcheUnclassifiedIPv4 IPv6140
AS208719Vialis SEMUnclassifiedIPv4 IPv6102

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6381
AS174Cogent Communications, LLCTransitIPv4 IPv6301
AS208574Communaute de Communes du Pays de BitcheUnclassifiedIPv4 IPv6140
AS208719Vialis SEMUnclassifiedIPv4 IPv6102
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv648
AS15557SFR SAResidentialIPv4 IPv647
AS24482SG.GSHostingIPv4 IPv612
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv612
AS37721Virtual Technologies & SolutionsResidentialIPv48
AS9002RETN LimitedUnclassifiedIPv67

All 14 adjacent →

Provenance

Where this comes from

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