asn.dev

Observed topology

AS213113 KAMEL

Unclassified RIPE Non-Profit

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS213113: 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 IPv674
AS3399Obenet ABUnclassifiedIPv4 IPv653
AS24482SG.GSHostingIPv4 IPv63
AS20473The Constant Company, LLCHostingIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS57782Cynthia Maja RevstromUnclassifiedIPv4 IPv6139
AS203909Christian SvenssonUnclassifiedIPv4 IPv694
AS218683Alexander Malmstroem trading as AleMal Network ServicesUnclassifiedIPv637

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3399Obenet ABUnclassifiedIPv4 IPv6262
AS57782Cynthia Maja RevstromUnclassifiedIPv4 IPv6193
AS6939Hurricane Electric LLCTransitIPv4 IPv6184
AS203909Christian SvenssonUnclassifiedIPv4 IPv694
AS218683Alexander Malmstroem trading as AleMal Network ServicesUnclassifiedIPv637
AS24482SG.GSHostingIPv4 IPv66
AS20473The Constant Company, LLCHostingIPv64

Provenance

Where this comes from

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