asn.dev

Observed topology

AS8523 BASEFARM-SE-ASN Orange Business Digital Sweden AB

Hosting RIPE Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS8523: 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 IPv6275
AS3257GTT Communications Inc.TransitIPv4 IPv635
AS25148Orange Business Digital Norway ASHostingIPv412
AS1257Tele2 Sverige ABMobileIPv4 IPv66
AS12552GlobalConnect ABUnclassifiedIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS25148Orange Business Digital Norway ASHostingIPv63

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6278
AS3257GTT Communications Inc.TransitIPv4 IPv635
AS25148Orange Business Digital Norway ASHostingIPv4 IPv615
AS1257Tele2 Sverige ABMobileIPv4 IPv66
AS12552GlobalConnect ABUnclassifiedIPv43

Provenance

Where this comes from

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