asn.dev

Observed topology

AS57829 IVER IVER NORGE AS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS57829: 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 IPv61,367
AS3356Level 3 Parent, LLCTransitIPv4 IPv61,343
AS6939Hurricane Electric LLCTransitIPv4 IPv6540
AS33891Core-Backbone GmbHHostingIPv4118
AS1257Tele2 Sverige ABMobileIPv4 IPv665
AS24482SG.GSHostingIPv4 IPv665
AS42708Glesys Sweden ABUnclassifiedIPv4 IPv665
AS12552GlobalConnect ABUnclassifiedIPv457
AS20473The Constant Company, LLCHostingIPv66
AS49788Nexthop ASUnclassifiedIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS49409IVER NORGE ASResidentialIPv4 IPv6489
AS49419Iver Sverige ABUnclassifiedIPv4 IPv6330
AS59720Bofiber ASUnclassifiedIPv4 IPv676
AS42695Cleura ABUnclassifiedIPv4 IPv663

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv61,661
AS3356Level 3 Parent, LLCTransitIPv4 IPv61,650
AS6939Hurricane Electric LLCTransitIPv4 IPv6732
AS49409IVER NORGE ASResidentialIPv4 IPv6489
AS49419Iver Sverige ABUnclassifiedIPv4 IPv6330
AS33891Core-Backbone GmbHHostingIPv4184
AS42708Glesys Sweden ABUnclassifiedIPv4 IPv698
AS24482SG.GSHostingIPv4 IPv688
AS59720Bofiber ASUnclassifiedIPv4 IPv686
AS1257Tele2 Sverige ABMobileIPv4 IPv685

All 15 adjacent →

Provenance

Where this comes from

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