asn.dev

Observed topology

AS57119 NAITWAYS-AS NAITWAYS SAS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS57119: 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
AS29075IELO-LIAZO SERVICES SASUnclassifiedIPv4 IPv6377
AS30781Free Pro SASHostingIPv4 IPv6100
AS6939Hurricane Electric LLCTransitIPv458
AS174Cogent Communications, LLCTransitIPv445
AS24482SG.GSHostingIPv4 IPv69
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv68
AS37721Virtual Technologies & SolutionsResidentialIPv46
AS35661VIRTUA SYSTEMS SASUnclassifiedIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS30919Expertise France SASUnclassifiedIPv4236
AS201188BJT Partners SASUnclassifiedIPv410

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS29075IELO-LIAZO SERVICES SASUnclassifiedIPv4 IPv6505
AS30919Expertise France SASUnclassifiedIPv4236
AS30781Free Pro SASHostingIPv4 IPv6176
AS6939Hurricane Electric LLCTransitIPv486
AS174Cogent Communications, LLCTransitIPv445
AS24482SG.GSHostingIPv4 IPv613
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv613
AS37721Virtual Technologies & SolutionsResidentialIPv411
AS201188BJT Partners SASUnclassifiedIPv410
AS35661VIRTUA SYSTEMS SASUnclassifiedIPv62

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.