asn.dev

Observed topology

AS12996 DOMENESHOP Domeneshop AS

Hosting RIPE

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

Transit

Upstream networks

All 16

Networks observed carrying traffic for AS12996: 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 IPv6455
AS6939Hurricane Electric LLCTransitIPv4 IPv6392
AS174Cogent Communications, LLCTransitIPv4 IPv6256
AS3356Level 3 Parent, LLCTransitIPv4 IPv6241
AS40676Psychz NetworksHostingIPv4 IPv643
AS24482SG.GSHostingIPv4 IPv626
AS50304Blix Solutions ASUnclassifiedIPv4 IPv626
AS34927iFog GmbHHostingIPv4 IPv625
AS57381Daniel HusandUnclassifiedIPv4 IPv624
AS12389PJSC RostelecomResidentialIPv417

All 16 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS208045Domeneshop ASUnclassifiedIPv4 IPv613

Adjacency

Adjacent networks

All 17

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6455
AS6939Hurricane Electric LLCTransitIPv4 IPv6398
AS174Cogent Communications, LLCTransitIPv4 IPv6256
AS3356Level 3 Parent, LLCTransitIPv4 IPv6241
AS40676Psychz NetworksHostingIPv4 IPv643
AS50304Blix Solutions ASUnclassifiedIPv4 IPv628
AS34927iFog GmbHHostingIPv4 IPv627
AS24482SG.GSHostingIPv4 IPv626
AS57381Daniel HusandUnclassifiedIPv4 IPv626
AS49788Nexthop ASUnclassifiedIPv418

All 17 adjacent →

Provenance

Where this comes from

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