asn.dev

Observed topology

AS57829 IVER IVER NORGE AS

Unclassified RIPE

Upstreams 12 carry this network
Downstreams 4 this network carries
Adjacent (IPv4) 16
Adjacent (IPv6) 12
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

All 12

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
AS3356Level 3 Parent, LLCTransitIPv4 IPv61,343
AS1299Arelion Sweden ABTransitIPv4 IPv61,302
AS6939Hurricane Electric LLCTransitIPv4 IPv6541
AS33891Core-Backbone GmbHHostingIPv4118
AS1257Tele2 Sverige ABMobileIPv4 IPv665
AS24482SG.GSHostingIPv4 IPv665
AS42708Glesys Sweden ABUnclassifiedIPv4 IPv665
AS50304Blix Solutions ASUnclassifiedIPv4 IPv665
AS20764CJSC RASCOMUnclassifiedIPv459
AS12552GlobalConnect ABUnclassifiedIPv457

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
AS42695Cleura ABUnclassifiedIPv4 IPv6653
AS49409IVER NORGE ASResidentialIPv4 IPv6493
AS49419Iver Sverige ABUnclassifiedIPv4 IPv6334
AS59720Bofiber ASUnclassifiedIPv4 IPv672

Adjacency

Adjacent networks

All 17

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv62,000
AS3356Level 3 Parent, LLCTransitIPv4 IPv61,642
AS6939Hurricane Electric LLCTransitIPv4 IPv6744
AS42695Cleura ABUnclassifiedIPv4 IPv6722
AS49409IVER NORGE ASResidentialIPv4 IPv6493
AS49419Iver Sverige ABUnclassifiedIPv4 IPv6334
AS33891Core-Backbone GmbHHostingIPv4232
AS42708Glesys Sweden ABUnclassifiedIPv4 IPv6146
AS50304Blix Solutions ASUnclassifiedIPv4 IPv6144
AS12552GlobalConnect ABUnclassifiedIPv4113

Provenance

Where this comes from

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