ASN LANDING PAGE

AS33930

CLOUD-TEMPLE Cloud Temple SAS

Last updated · Jul 20, 2026

Country

Total prefixes

8

IPv4 prefixes

6

IPv6 prefixes

2

ASN summary

How to read the scale of AS33930

CLOUD-TEMPLE Cloud Temple SAS currently reports 8 prefixes and 43 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?

CLOUD-TEMPLE Cloud Temple SAS 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 AS33930 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

AS33930 ASN lookupAS33930 BGPAS33930 peersAS33930 prefixesAS33930 upstreamsCLOUD-TEMPLE Cloud Temple SAS ASN

Upstreams

Detailed data for this ASN is not available right now.

Peers

Prefix inventory

PrefixNameCountry
185.56.204.0/22AS33930
194.6.240.0/24AS33930
2a02:668:9000::/36AS33930
2a02:668::/36AS33930
45.15.212.0/22AS33930
80.75.152.0/21AS33930
91.223.207.0/24AS33930
93.187.40.0/21AS33930

Related ASN pages

Related lookups and next steps

Frequently asked questions about this ASN page

What does AS33930 represent?

AS33930 is an autonomous system number. The current source associates it with CLOUD-TEMPLE Cloud Temple SAS 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 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?

Open a concrete IP page to check how the address maps into AS33930, then compare the prefix, source labels, and query time. Verify operator or service claims with the relevant registry or network operator.

Related topics