asn.dev

Observed topology

AS213151 CHRISELSEN

Hosting RIPE

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

Transit

Upstream networks

All 23

Networks observed carrying traffic for AS213151: 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
AS16509Amazon.com, Inc.HostingIPv6168
AS6939Hurricane Electric LLCTransitIPv4 IPv6144
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv648
AS14618Amazon.com, Inc.HostingIPv634
AS29632Netassist International EOODUnclassifiedIPv68
AS24482SG.GSHostingIPv4 IPv66
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv65
AS57821Nonattached Network e.V.UnclassifiedIPv4 IPv65
AS401753BIXCE IncUnclassifiedIPv4 IPv65
AS41051Openfactory GmbHUnclassifiedIPv64

All 23 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS12654Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv63

Adjacency

Adjacent networks

All 24

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

ASNetworkTypeFamiliesPaths seen
AS16509Amazon.com, Inc.HostingIPv6168
AS6939Hurricane Electric LLCTransitIPv4 IPv6144
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv648
AS14618Amazon.com, Inc.HostingIPv634
AS29632Netassist International EOODUnclassifiedIPv68
AS57821Nonattached Network e.V.UnclassifiedIPv4 IPv67
AS24482SG.GSHostingIPv4 IPv66
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv65
AS401753BIXCE IncUnclassifiedIPv4 IPv65
AS41051Openfactory GmbHUnclassifiedIPv64

All 24 adjacent →

Provenance

Where this comes from

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