asn.dev

Observed topology

AS224 UNINETT UNINETT, The Norwegian University & Research Network

Unclassified RIPE Educational/Research

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS224: 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
AS2603NORDUnetEducationIPv4 IPv61,033
AS50304Blix Solutions ASUnclassifiedIPv4 IPv621
AS56655Gigahost ASUnclassifiedIPv4 IPv621
AS42708Glesys ABUnclassifiedIPv4 IPv619
AS49788Nexthop ASUnclassifiedIPv417

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS58302Studentersamfundet i TrondhjemUnclassifiedIPv4 IPv6216
AS50270Nasjonal kommunikasjonsmyndighetUnclassifiedIPv4 IPv6180
AS59863Norsk Regnesentral STIUnclassifiedIPv461
AS60278Helse Vest IKT ASUnclassifiedIPv461
AS200693Kongsberg Satellite Services ASUnclassifiedIPv461

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS2603NORDUnetEducationIPv4 IPv61,576
AS58302Studentersamfundet i TrondhjemUnclassifiedIPv4 IPv6216
AS50270Nasjonal kommunikasjonsmyndighetUnclassifiedIPv4 IPv6180
AS59863Norsk Regnesentral STIUnclassifiedIPv461
AS60278Helse Vest IKT ASUnclassifiedIPv461
AS200693Kongsberg Satellite Services ASUnclassifiedIPv461
AS50304Blix Solutions ASUnclassifiedIPv4 IPv632
AS42708Glesys ABUnclassifiedIPv4 IPv630
AS56655Gigahost ASUnclassifiedIPv4 IPv629
AS49788Nexthop ASUnclassifiedIPv423

Provenance

Where this comes from

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