asn.dev

Observed topology

AS216275 noerdnet Netnoerden ApS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS216275: 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
AS6797GlobalConnect ABUnclassifiedIPv4 IPv6181
AS31027GlobalConnect A/SUnclassifiedIPv4 IPv683

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS215541Peter KruseUnclassifiedIPv4 IPv6150
AS214980Hexi Group ApSUnclassifiedIPv4 IPv6123
AS211040MS 2001 ApsUnclassifiedIPv4116
AS62121Christian Ebsen ApSUnclassifiedIPv4 IPv691
AS61298Noah Kornelius SvanholmUnclassifiedIPv632
AS208391Christoffer HansenUnclassifiedIPv632
AS218707Christoffer GamrathUnclassifiedIPv632

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6797GlobalConnect ABUnclassifiedIPv4 IPv6666
AS31027GlobalConnect A/SUnclassifiedIPv4 IPv6206
AS214980Hexi Group ApSUnclassifiedIPv4 IPv6155
AS215541Peter KruseUnclassifiedIPv4 IPv6150
AS211040MS 2001 ApsUnclassifiedIPv4116
AS62121Christian Ebsen ApSUnclassifiedIPv4 IPv691
AS61298Noah Kornelius SvanholmUnclassifiedIPv632
AS208391Christoffer HansenUnclassifiedIPv632
AS218707Christoffer GamrathUnclassifiedIPv632

Provenance

Where this comes from

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