asn.dev

Observed topology

AS213409 LYNQIA Private Network Infrastructure

Hosting APNIC

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

Transit

Upstream networks

All 17

Networks observed carrying traffic for AS213409: 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
AS218569Viktor NesmeianovUnclassifiedIPv6150
AS6939Hurricane Electric LLCTransitIPv6100
AS29632Netassist International EOODUnclassifiedIPv682
AS8772NetAssist LLCUnclassifiedIPv667
AS357084b42 UGUnclassifiedIPv69
AS200132Peter-Paul Maria KurstjensUnclassifiedIPv68
AS214757Jakub KrsaUnclassifiedIPv67
AS400992ZhouyiSat CommunicationsUnclassifiedIPv67
AS24482SG.GSHostingIPv64
AS37989DCS1 Pte. Ltd.HostingIPv64

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 17

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

ASNetworkTypeFamiliesPaths seen
AS218569Viktor NesmeianovUnclassifiedIPv6150
AS6939Hurricane Electric LLCTransitIPv6100
AS29632Netassist International EOODUnclassifiedIPv682
AS8772NetAssist LLCUnclassifiedIPv667
AS357084b42 UGUnclassifiedIPv69
AS200132Peter-Paul Maria KurstjensUnclassifiedIPv68
AS214757Jakub KrsaUnclassifiedIPv67
AS400992ZhouyiSat CommunicationsUnclassifiedIPv67
AS24482SG.GSHostingIPv64
AS37989DCS1 Pte. Ltd.HostingIPv64

Provenance

Where this comes from

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