Country
—
ASN LANDING PAGE
AS33930
CLOUD-TEMPLE - Cloud Temple SAS
Last updated · Apr 4, 2026
Total prefixes
8
IPv4 prefixes
6
IPv6 prefixes
2
ASN summary
How to read the scale of AS33930
CLOUD-TEMPLE - Cloud Temple SAS currently shows 8 prefixes and 43 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.
When is an ASN page most useful?
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.
How should you read the country, organization, and role of AS33930?
CLOUD-TEMPLE - Cloud Temple 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.
What should you inspect next after the AS33930 page?
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.
Search intents this ASN page helps cover
AS33930 ASN lookupAS33930 BGPAS33930 peersAS33930 prefixesAS33930 upstreamsCLOUD-TEMPLE - Cloud Temple SAS ASN
Upstreams
Detailed data for this ASN is not available right now.
Downstreams
Peers
AS35280
AS35280
—
AS6939
AS6939
—
AS20764
AS20764
—
AS34019
AS34019
—
AS6057
AS6057
—
AS8298
AS8298
—
AS12779
AS12779
—
AS25091
AS25091
—
AS34177
AS34177
—
AS41327
AS41327
—
AS9002
AS9002
—
AS1299
AS1299
—
AS14840
AS14840
—
AS1828
AS1828
—
AS2027
AS2027
—
AS4455
AS4455
—
AS6696
AS6696
—
AS6758
AS6758
—
AS9009
AS9009
—
AS13237
AS13237
—
AS15547
AS15547
—
AS16347
AS16347
—
AS24482
AS24482
—
AS25160
AS25160
—
AS29049
AS29049
—
AS29075
AS29075
—
AS30781
AS30781
—
AS33891
AS33891
—
AS34288
AS34288
—
AS35426
AS35426
—
AS35600
AS35600
—
AS36236
AS36236
—
AS37721
AS37721
—
AS39120
AS39120
—
AS39351
AS39351
—
AS44097
AS44097
—
AS49434
AS49434
—
AS49544
AS49544
—
AS50628
AS50628
—
AS51185
AS51185
—
Prefix inventory
| Prefix | Name | Country |
|---|---|---|
| 185.56.204.0/22 | AS33930 | — |
| 194.6.240.0/24 | AS33930 | — |
| 2a02:668:9000::/36 | AS33930 | — |
| 2a02:668::/36 | AS33930 | — |
| 45.15.212.0/22 | AS33930 | — |
| 80.75.152.0/21 | AS33930 | — |
| 91.223.207.0/24 | AS33930 | — |
| 93.187.40.0/21 | AS33930 | — |
Related ASN pages
AS15169 · Google
A strong reference ASN for Google DNS, Google Cloud, and global network footprint analysis.
AS13335 · Cloudflare
Useful for analyzing CDN, Anycast, WAF, and large-scale edge network behavior.
AS8075 · Microsoft
Helpful when comparing Azure, enterprise backbone, and large-cloud routing patterns.
AS16509 · Amazon
A useful ASN landing page for understanding AWS and large cloud-network ownership.
Related lookups and next steps
WHOIS vs ASN Ownership Guide
Continue from this ASN into the differences between WHOIS ownership and ASN ownership.
Routing Troubleshooting and Network Analysis
Continue from this ASN into route troubleshooting and network analysis.
Cloud Network and ASN Comparison
Useful when you want to compare this ASN against larger cloud and edge networks.
WHOIS and IP Ownership Guide
Continue from the ASN page into WHOIS and ownership verification.
Frequently asked questions about this ASN page
What does AS33930 represent?
AS33930 is an autonomous system number used to identify an independently operated network. The current page associates it with CLOUD-TEMPLE - Cloud Temple SAS in an unknown region, which helps determine whether it behaves like a cloud provider, ISP, CDN, or enterprise backbone.
What are peers, upstreams, and prefixes useful for on the AS33930 page?
They help explain the scale, interconnection depth, and route structure of AS33930. 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 AS33930?
The best next step is usually to return to a concrete IP landing page to see how a specific address maps into AS33930, then continue into cloud, WHOIS, or routing topic pages to understand the network in a broader context.
Related topics
WHOIS vs ASN Ownership Guide
Understand why WHOIS ownership and ASN ownership can differ, and how to combine both when deciding who really owns or operates an IP.
WHOIS and IP Ownership Guide
Use WHOIS, ASN, prefixes, and organization data to determine who ultimately owns an IP, range, or resolved domain target.
BGP and ASN Basics Guide
Learn what ASN, BGP routes, prefixes, upstreams, downstreams, and peers mean, then explore real ASN pages.
Cloud Network and ASN Comparison
Compare large cloud and edge networks such as Google, Cloudflare, Microsoft, and Amazon through their ASN landing pages.