Country
—
ASN LANDING PAGE
CELYA - CELYA SAS
Last updated · Apr 4, 2026
Country
—
Total prefixes
23
IPv4 prefixes
18
IPv6 prefixes
5
CELYA - CELYA SAS currently shows 23 prefixes and 32 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.
CELYA - CELYA SAS 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.
Detailed data for this ASN is not available right now.
AS29075
AS29075
—
AS174
AS174
—
AS6939
AS6939
—
AS25091
AS25091
—
AS34019
AS34019
—
AS41327
AS41327
—
AS14840
AS14840
—
AS34177
AS34177
—
AS35280
AS35280
—
AS49451
AS49451
—
AS1828
AS1828
—
AS4455
AS4455
—
AS6696
AS6696
—
AS9009
AS9009
—
AS15547
AS15547
—
AS24482
AS24482
—
AS29049
AS29049
—
AS30972
AS30972
—
AS35600
AS35600
—
AS36236
AS36236
—
AS44097
AS44097
—
AS44530
AS44530
—
AS49028
AS49028
—
AS49544
AS49544
—
AS50628
AS50628
—
AS56987
AS56987
—
AS137409
AS137409
—
AS198150
AS198150
—
AS199524
AS199524
—
AS209823
AS209823
—
AS212483
AS212483
—
AS215596
AS215596
—
| Prefix | Name | Country |
|---|---|---|
| 185.122.100.0/22 | AS203596 | — |
| 185.122.100.0/24 | AS203596 | — |
| 185.122.102.0/24 | AS203596 | — |
| 185.122.103.0/24 | AS203596 | — |
| 185.14.176.0/24 | AS203596 | — |
| 185.14.178.0/24 | AS203596 | — |
| 185.222.88.0/22 | AS203596 | — |
| 185.222.89.0/24 | AS203596 | — |
| 185.222.90.0/24 | AS203596 | — |
| 185.222.91.0/24 | AS203596 | — |
| 193.108.216.0/24 | AS203596 | — |
| 193.109.0.0/24 | AS203596 | — |
| 193.109.1.0/24 | AS203596 | — |
| 193.109.2.0/24 | AS203596 | — |
| 193.109.3.0/24 | AS203596 | — |
| 2a06:a400:20::/44 | AS203596 | — |
| 2a06:a400:22::/48 | AS203596 | — |
| 2a06:a400:23::/48 | AS203596 | — |
| 2a06:a400::/29 | AS203596 | — |
| 2a06:a402::/32 | AS203596 | — |
| 91.213.223.0/24 | AS203596 | — |
| 91.216.15.0/24 | AS203596 | — |
| 91.216.39.0/24 | AS203596 | — |
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.
AS203596 is an autonomous system number used to identify an independently operated network. The current page associates it with CELYA - CELYA SAS 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 AS203596. 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 AS203596, 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.