asn.dev

Observed topology

AS213641 AS213641 AS213641

Hosting RIPE

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

Transit

Upstream networks

All 17

Networks observed carrying traffic for AS213641: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv690
AS34927iFog GmbHHostingIPv4 IPv627
AS6461Zayo BandwidthTransitIPv4 IPv623
AS52025ParadoxNetworks LimitedUnclassifiedIPv423
AS8893Artfiles New Media GmbHHostingIPv4 IPv610
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv65
AS24482SG.GSHostingIPv4 IPv65
AS48185team.blue NVUnclassifiedIPv4 IPv65
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv65
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv65

All 17 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS218548WILHELM ALEXANDER SCHMIDTUnclassifiedIPv617

Adjacency

Adjacent networks

All 18

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6103
AS34927iFog GmbHHostingIPv4 IPv627
AS6461Zayo BandwidthTransitIPv4 IPv624
AS52025ParadoxNetworks LimitedUnclassifiedIPv423
AS218548WILHELM ALEXANDER SCHMIDTUnclassifiedIPv617
AS8893Artfiles New Media GmbHHostingIPv4 IPv610
AS24482SG.GSHostingIPv4 IPv66
AS401753BIXCE IncUnclassifiedIPv4 IPv66
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv65
AS48185team.blue NVUnclassifiedIPv4 IPv65

All 18 adjacent →

Provenance

Where this comes from

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