Country
—
ASN LANDING PAGE
AS201217
radishcloud RADISHCLOUD TECHNOLOGY LLC
Last updated · Jul 20, 2026
Total prefixes
53
IPv4 prefixes
7
IPv6 prefixes
46
ASN summary
How to read the scale of AS201217
radishcloud RADISHCLOUD TECHNOLOGY LLC currently reports 53 prefixes and 15 upstream, downstream, or peer relationships. These counts describe the current dataset; they do not by themselves prove network quality, reach, or service use.
What can an ASN page answer?
An ASN page shows the public organization label, country or region, BGP prefixes, and available peer and upstream relationships. It adds network context but cannot confirm a website host, physical facility, security status, or service quality.
How should you read the organization and region fields?
radishcloud RADISHCLOUD TECHNOLOGY LLC is currently associated with an unknown region. These values come from public network sources and are useful lookup clues; an organization label, registration region, and actual service location may differ.
How should you verify the AS201217 result?
The page shows ASN data returned by the current upstream query; interpret it with the update time. Open representative IP pages from the same network and compare prefixes, source labels, and query times. Verify operator or service claims with the relevant registry or network operator.
How to verify this ASN result
AS201217 ASN lookupAS201217 BGPAS201217 peersAS201217 prefixesAS201217 upstreamsradishcloud RADISHCLOUD TECHNOLOGY LLC ASN
Upstreams
Detailed data for this ASN is not available right now.
Downstreams
Peers
Prefix inventory
| Prefix | Name | Country |
|---|---|---|
| 103.220.218.0/24 | AS201217 | — |
| 160.22.157.0/24 | AS201217 | — |
| 206.237.116.0/24 | AS201217 | — |
| 206.237.119.0/24 | AS201217 | — |
| 210.79.151.0/24 | AS201217 | — |
| 23.172.200.0/24 | AS201217 | — |
| 2400:70e0:bae::/48 | AS201217 | — |
| 2602:f96c:f0::/44 | AS201217 | — |
| 2a06:a005:1c78::/48 | AS201217 | — |
| 2a0a:280:1700::/40 | AS201217 | — |
| 2a0a:280:1702::/48 | AS201217 | — |
| 2a0a:280:1705::/48 | AS201217 | — |
| 2a12:3fc2:ab74::/48 | AS201217 | — |
| 2a12:dd47:f00a::/48 | AS201217 | — |
| 2a13:a5c6:1000::/36 | AS201217 | — |
| 2a13:a5c6:101e::/48 | AS201217 | — |
| 2a13:a5c6:101f::/48 | AS201217 | — |
| 2a13:a5c6:1fff::/48 | AS201217 | — |
| 2a13:a5c6:2000::/36 | AS201217 | — |
| 2a13:a5c6:2f00::/40 | AS201217 | — |
| 2a13:a5c6:2f0f::/48 | AS201217 | — |
| 2a13:a5c6:3000::/36 | AS201217 | — |
| 2a13:a5c6:3100::/40 | AS201217 | — |
| 2a13:a5c6:3200::/40 | AS201217 | — |
| 2a13:a5c6:3a00::/40 | AS201217 | — |
| 2a13:a5c6:3b01::/48 | AS201217 | — |
| 2a13:a5c6:3b02::/48 | AS201217 | — |
| 2a13:a5c6:4000::/36 | AS201217 | — |
| 2a13:a5c6:40b1::/48 | AS201217 | — |
| 2a13:a5c6:4100::/40 | AS201217 | — |
| 2a13:a5c6:4101::/48 | AS201217 | — |
| 2a13:a5c6:4102::/48 | AS201217 | — |
| 2a13:a5c6:4103::/48 | AS201217 | — |
| 2a13:a5c6:4a09::/48 | AS201217 | — |
| 2a13:a5c6:4aa1::/48 | AS201217 | — |
| 2a13:a5c6:4aa2::/48 | AS201217 | — |
| 2a13:a5c6:4aa3::/48 | AS201217 | — |
| 2a13:a5c6:4aa4::/48 | AS201217 | — |
| 2a13:a5c6:5000::/36 | AS201217 | — |
| 2a13:a5c6:6100::/40 | AS201217 | — |
Related ASN pages
AS15169 · Google
Review Google network organization fields, prefixes, peers, upstreams, and downstreams.
AS13335 · Cloudflare
Review Cloudflare network organization fields, prefixes, peers, upstreams, and downstreams.
AS8075 · Microsoft
Review Microsoft network organization fields, prefixes, peers, upstreams, and downstreams.
AS16509 · Amazon
Review Amazon network organization fields, prefixes, peers, upstreams, and downstreams.
Related lookups and next steps
Frequently asked questions about this ASN page
What does AS201217 represent?
AS201217 is an autonomous system number. The current source associates it with radishcloud RADISHCLOUD TECHNOLOGY LLC and the region field an unknown region; those values add network context but do not prove a specific service, physical location, or quality level.
What are peers, upstreams, and prefixes useful for on the AS201217 page?
They help explain the scale, interconnection depth, and route structure of AS201217. Richer peering and upstream data often indicate broader network reach, but they should still be interpreted together with prefixes and related IP landing pages.
What should you do after reviewing AS201217?
Open a concrete IP page to check how the address maps into AS201217, then compare the prefix, source labels, and query time. Verify operator or service claims with the relevant registry or network operator.
Related topics
BGP and ASN Basics Guide
Use real IP and ASN pages to understand ASNs, BGP prefixes, peers, upstreams, and downstreams, including the limits of each snapshot.
Routing Troubleshooting and Network Analysis
Build troubleshooting context from an IP, BGP prefix, ASN, and public network relationships without treating static route data as a packet path.
Cloud Network and ASN Comparison
Compare representative cloud and edge networks by ASN, announced prefixes, peers, upstreams, and downstreams without inferring a specific host or customer workload.