asn.dev

Observed topology

AS60983 LIOPEN-AS LIOPEN SARL

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS60983: 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
AS56987ABACLOUDA SASUnclassifiedIPv4 IPv6277
AS209255TELFAX COMMUNICATIONS SARLUnclassifiedIPv4 IPv643
AS201376Association AuvernIXUnclassifiedIPv424
AS43100France IX Services SASUUnclassifiedIPv44

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS199881Association Auvergne WirelessUnclassifiedIPv4 IPv6176
AS209385VELUMWARE SARLResidentialIPv4 IPv6122
AS202328ATELIER OLIVIER CHARNAY TELECOM SASUnclassifiedIPv4110
AS202663VOGANET SARLResidentialIPv4104
AS209255TELFAX COMMUNICATIONS SARLUnclassifiedIPv4 IPv65

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS56987ABACLOUDA SASUnclassifiedIPv4 IPv6683
AS199881Association Auvergne WirelessUnclassifiedIPv4 IPv6176
AS209255TELFAX COMMUNICATIONS SARLUnclassifiedIPv4 IPv6159
AS209385VELUMWARE SARLResidentialIPv4 IPv6122
AS202328ATELIER OLIVIER CHARNAY TELECOM SASUnclassifiedIPv4110
AS202663VOGANET SARLResidentialIPv4104
AS201376Association AuvernIXUnclassifiedIPv424
AS43100France IX Services SASUUnclassifiedIPv44
AS4200063002unnamedUnclassifiedIPv42
AS4200063001unnamedUnclassifiedIPv61

All 11 adjacent →

Provenance

Where this comes from

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