asn.dev

Observed topology

AS201217 radishcloud RADISHCLOUD TECHNOLOGY LLC

Hosting RIPE Network Services

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS201217: 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
AS51847Nearoute LimitedHostingIPv4 IPv61,429
AS6939Hurricane Electric LLCTransitIPv4 IPv6291
AS210000TwentyWAN MBHostingIPv4 IPv6250
AS52041Scaleblade, Ltd.UnclassifiedIPv6165
AS402782TAIPEI101UnclassifiedIPv4 IPv696
AS32595Liberally Network, LLCResidentialIPv447
AS24482SG.GSHostingIPv4 IPv69
AS38855Taiwan Digital Streaming Co.UnclassifiedIPv4 IPv69

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS32595Liberally Network, LLCResidentialIPv459
AS203314HATS NETWORK INC.ResidentialIPv620

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS51847Nearoute LimitedHostingIPv4 IPv61,508
AS6939Hurricane Electric LLCTransitIPv4 IPv6291
AS210000TwentyWAN MBHostingIPv4 IPv6250
AS52041Scaleblade, Ltd.UnclassifiedIPv6165
AS32595Liberally Network, LLCResidentialIPv4106
AS402782TAIPEI101UnclassifiedIPv4 IPv696
AS203314HATS NETWORK INC.ResidentialIPv620
AS24482SG.GSHostingIPv4 IPv69
AS38855Taiwan Digital Streaming Co.UnclassifiedIPv4 IPv69

Provenance

Where this comes from

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