asn.dev

Observed topology

AS20514 QBRANCH Axians AB

Hosting RIPE Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS20514: 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
AS42649Baffin Bay Networks ABUnclassifiedIPv4 IPv6208
AS1299Arelion Sweden ABTransitIPv459
AS8434Telenor Sverige ABResidentialIPv458

Transit

Downstream networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS8075Microsoft CorporationHostingIPv41,202
AS41943Vaddo Media Information IS ABUnclassifiedIPv4 IPv61,035
AS1299Arelion Sweden ABTransitIPv4101
AS8434Telenor Sverige ABResidentialIPv475
AS202053UpCloud LtdHostingIPv459
AS5763084 Grams ABResidentialIPv455
AS8674Netnod ABUnclassifiedIPv415
AS50572Nordlo Improve ABHostingIPv415
AS48579ELASTX ABHostingIPv411
AS2603NORDUnetEducationIPv410

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4926,185
AS8434Telenor Sverige ABResidentialIPv4141,633
AS42649Baffin Bay Networks ABUnclassifiedIPv4 IPv61,518
AS2603NORDUnetEducationIPv41,463
AS41943Vaddo Media Information IS ABUnclassifiedIPv4 IPv61,334
AS8075Microsoft CorporationHostingIPv41,282
AS5763084 Grams ABResidentialIPv4165
AS202053UpCloud LtdHostingIPv459
AS8674Netnod ABUnclassifiedIPv434
AS50572Nordlo Improve ABHostingIPv415

Provenance

Where this comes from

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