asn.dev

Observed topology

AS51929 ITM-SE Advania Sverige AB

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS51929: 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
AS57208Advania Sverige ABUnclassifiedIPv4516
AS8434Telenor Sverige ABResidentialIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS210905Hallefors KommunUnclassifiedIPv4 IPv689
AS42251Lindesbergs KommunUnclassifiedIPv4 IPv688
AS213188Nora KommunUnclassifiedIPv457
AS201087Suzuki Garphyttan ABUnclassifiedIPv4 IPv612
AS203471MicroData Skandinavien ABUnclassifiedIPv42

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS57208Advania Sverige ABUnclassifiedIPv4 IPv6764
AS210905Hallefors KommunUnclassifiedIPv4 IPv689
AS42251Lindesbergs KommunUnclassifiedIPv4 IPv688
AS213188Nora KommunUnclassifiedIPv457
AS201087Suzuki Garphyttan ABUnclassifiedIPv4 IPv612
AS203471MicroData Skandinavien ABUnclassifiedIPv42
AS8434Telenor Sverige ABResidentialIPv61

Provenance

Where this comes from

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