Country
—
ASN LANDING PAGE
RAYA-AS
Last updated · Apr 4, 2026
Country
—
Total prefixes
2061
IPv4 prefixes
2045
IPv6 prefixes
16
RAYA-AS currently shows 2061 prefixes and 35 upstream, downstream, or peer relationships. Larger prefix inventories often indicate broader network footprint, but they should still be read together with country and peering context.
ASN landing pages are more useful than a single IP page when you want cloud provider attribution, routing research, infrastructure comparison, or network topology analysis at the organization level.
RAYA-AS is currently associated with an unknown region. Country data is only a starting point; the more important signals are the organization name, website, prefix volume, and peering relationships that reveal whether the network behaves like a cloud platform, ISP, CDN, or enterprise backbone.
This page is currently showing live ASN data that can be used for peer, prefix, and network scale analysis. The most useful next step is usually to return to a related IP landing page, then compare that concrete address with this ASN profile and with broader topic pages for routing, cloud attribution, or WHOIS ownership analysis.
Detailed data for this ASN is not available right now.
AS36935
AS36935
—
AS36978
AS36978
—
AS329114
AS329114
—
AS20928
AS20928
—
AS25576
AS25576
—
AS25818
AS25818
—
AS328794
AS328794
—
AS30995
AS30995
—
AS8524
AS8524
—
AS34778
AS34778
—
AS328786
AS328786
—
AS33778
AS33778
—
AS328299
AS328299
—
AS37091
AS37091
—
AS53926
AS53926
—
AS36929
AS36929
—
AS37112
AS37112
—
AS37348
AS37348
—
AS37437
AS37437
—
AS328972
AS328972
—
AS31619
AS31619
—
AS37193
AS37193
—
AS328067
AS328067
—
AS329359
AS329359
—
AS329431
AS329431
—
AS214849
AS214849
—
AS25364
AS25364
—
AS31065
AS31065
—
AS329352
AS329352
—
AS6127
AS6127
—
AS36893
AS36893
—
AS328553
AS328553
—
| Prefix | Name | Country |
|---|---|---|
| 102.184.0.0/13 | AS24835 | — |
| 102.184.0.0/20 | AS24835 | — |
| 102.184.0.0/22 | AS24835 | — |
| 102.184.100.0/22 | AS24835 | — |
| 102.184.104.0/22 | AS24835 | — |
| 102.184.108.0/22 | AS24835 | — |
| 102.184.112.0/20 | AS24835 | — |
| 102.184.112.0/22 | AS24835 | — |
| 102.184.116.0/22 | AS24835 | — |
| 102.184.12.0/22 | AS24835 | — |
| 102.184.120.0/22 | AS24835 | — |
| 102.184.124.0/22 | AS24835 | — |
| 102.184.128.0/20 | AS24835 | — |
| 102.184.128.0/22 | AS24835 | — |
| 102.184.132.0/22 | AS24835 | — |
| 102.184.136.0/22 | AS24835 | — |
| 102.184.140.0/22 | AS24835 | — |
| 102.184.144.0/20 | AS24835 | — |
| 102.184.144.0/22 | AS24835 | — |
| 102.184.148.0/22 | AS24835 | — |
| 102.184.152.0/22 | AS24835 | — |
| 102.184.156.0/22 | AS24835 | — |
| 102.184.16.0/20 | AS24835 | — |
| 102.184.16.0/22 | AS24835 | — |
| 102.184.160.0/20 | AS24835 | — |
| 102.184.160.0/22 | AS24835 | — |
| 102.184.164.0/22 | AS24835 | — |
| 102.184.168.0/22 | AS24835 | — |
| 102.184.172.0/22 | AS24835 | — |
| 102.184.176.0/20 | AS24835 | — |
| 102.184.176.0/22 | AS24835 | — |
| 102.184.180.0/22 | AS24835 | — |
| 102.184.184.0/22 | AS24835 | — |
| 102.184.188.0/22 | AS24835 | — |
| 102.184.192.0/20 | AS24835 | — |
| 102.184.192.0/22 | AS24835 | — |
| 102.184.196.0/22 | AS24835 | — |
| 102.184.20.0/22 | AS24835 | — |
| 102.184.200.0/22 | AS24835 | — |
| 102.184.204.0/22 | AS24835 | — |
A strong reference ASN for Google DNS, Google Cloud, and global network footprint analysis.
Useful for analyzing CDN, Anycast, WAF, and large-scale edge network behavior.
Helpful when comparing Azure, enterprise backbone, and large-cloud routing patterns.
A useful ASN landing page for understanding AWS and large cloud-network ownership.
Continue from this ASN into the differences between WHOIS ownership and ASN ownership.
Continue from this ASN into route troubleshooting and network analysis.
Useful when you want to compare this ASN against larger cloud and edge networks.
Continue from the ASN page into WHOIS and ownership verification.
AS24835 is an autonomous system number used to identify an independently operated network. The current page associates it with RAYA-AS in an unknown region, which helps determine whether it behaves like a cloud provider, ISP, CDN, or enterprise backbone.
They help explain the scale, interconnection depth, and route structure of AS24835. Richer peering and upstream data often indicate broader network reach, but they should still be interpreted together with prefixes and related IP landing pages.
The best next step is usually to return to a concrete IP landing page to see how a specific address maps into AS24835, then continue into cloud, WHOIS, or routing topic pages to understand the network in a broader context.
Understand why WHOIS ownership and ASN ownership can differ, and how to combine both when deciding who really owns or operates an IP.
Use WHOIS, ASN, prefixes, and organization data to determine who ultimately owns an IP, range, or resolved domain target.
Learn what ASN, BGP routes, prefixes, upstreams, downstreams, and peers mean, then explore real ASN pages.
Compare large cloud and edge networks such as Google, Cloudflare, Microsoft, and Amazon through their ASN landing pages.