asn.dev

Observed topology

AS51057 NEXXTRA

Residential RIPE

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

Transit

Upstream networks

All 17

Networks observed carrying traffic for AS51057: 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
AS1299Arelion Sweden ABTransitIPv4 IPv675
AS174Cogent Communications, LLCTransitIPv4 IPv628
AS6939Hurricane Electric LLCTransitIPv414
AS34549meerfarbig GmbH & Co. KGHostingIPv46
AS1836green.ch AGResidentialIPv42
AS6797GlobalConnect ABUnclassifiedIPv42
AS12779IT.Gate S.p.A.UnclassifiedIPv42
AS12859BIT BVHostingIPv42
AS20485Joint Stock Company TransTeleComUnclassifiedIPv42
AS24482SG.GSHostingIPv42

All 17 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 17

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv675
AS174Cogent Communications, LLCTransitIPv4 IPv628
AS6939Hurricane Electric LLCTransitIPv414
AS34549meerfarbig GmbH & Co. KGHostingIPv46
AS1836green.ch AGResidentialIPv42
AS6797GlobalConnect ABUnclassifiedIPv42
AS12779IT.Gate S.p.A.UnclassifiedIPv42
AS12859BIT BVHostingIPv42
AS20485Joint Stock Company TransTeleComUnclassifiedIPv42
AS24482SG.GSHostingIPv42

All 17 adjacent →

Provenance

Where this comes from

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