asn.dev

Observed topology

AS214344 Hanxun-Xu Hanxun Xu

Unclassified RIPE

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

Transit

Upstream networks

All 14

Networks observed carrying traffic for AS214344: 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 LLCTransitIPv6206
AS216211CYBERVERSE LLCHostingIPv4 IPv6203
AS63473HostHatch, LLCUnclassifiedIPv4 IPv6154
AS52025ParadoxNetworks LimitedUnclassifiedIPv6149
AS34927iFog GmbHHostingIPv669
AS37989DCS1 Pte. Ltd.HostingIPv4 IPv613
AS58057Securebit AGUnclassifiedIPv612
AS205794JINZE YANGUnclassifiedIPv611
AS47272HYEHOST LLCHostingIPv610
AS357084b42 UGUnclassifiedIPv69

All 14 upstreams →

Transit

Downstream networks

inferred

Networks for which AS214344 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 14

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv6206
AS216211CYBERVERSE LLCHostingIPv4 IPv6203
AS63473HostHatch, LLCUnclassifiedIPv4 IPv6154
AS52025ParadoxNetworks LimitedUnclassifiedIPv6149
AS34927iFog GmbHHostingIPv669
AS37989DCS1 Pte. Ltd.HostingIPv4 IPv613
AS58057Securebit AGUnclassifiedIPv612
AS205794JINZE YANGUnclassifiedIPv611
AS47272HYEHOST LLCHostingIPv610
AS357084b42 UGUnclassifiedIPv69

All 14 adjacent →

Provenance

Where this comes from

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