asn.dev

Observed topology

AS51956 AS-QLOSRAB

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS51956: 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 IPv6635
AS6939Hurricane Electric LLCTransitIPv4 IPv6162
AS42708Glesys ABUnclassifiedIPv4 IPv6131
AS24482SG.GSHostingIPv4 IPv617
AS20764CJSC RASCOMUnclassifiedIPv416
AS50304Blix Solutions ASUnclassifiedIPv416
AS12552GlobalConnect ABUnclassifiedIPv413
AS8434Telenor Sverige ABResidentialIPv45
AS20473The Constant Company, LLCHostingIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS199821ITsjefen ASUnclassifiedIPv459
AS198549ECIT Solutions ABUnclassifiedIPv42

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6673
AS6939Hurricane Electric LLCTransitIPv4 IPv6171
AS42708Glesys ABUnclassifiedIPv4 IPv6140
AS199821ITsjefen ASUnclassifiedIPv459
AS24482SG.GSHostingIPv4 IPv618
AS20764CJSC RASCOMUnclassifiedIPv417
AS50304Blix Solutions ASUnclassifiedIPv417
AS12552GlobalConnect ABUnclassifiedIPv414
AS8434Telenor Sverige ABResidentialIPv46
AS198549ECIT Solutions ABUnclassifiedIPv42

All 11 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.