Clouvider IP Ranges
Clouvider Limited is a UK hosting and IP transit operator, RIPE organisation ORG-CL248-RIPE with company registration number 08750969, and AS62240 is its aut-num, created on 12 December 2013 and titled Clouvider - Global ASN. The object is unusually talkative: its remarks publish a geofeed URL, a looking glass at as62240.net, a status page at clouviderstatus.net, a peering address at clouvider.net and a full traffic-engineering community list. A good deal of what the ASN originates is not Clouvider-allocated space at all, but ARIN records held by another company, a RIPE allocation held by a Moscow LIR, and a legacy block.
- Provider
- Clouvider
- Primary ASN
- AS62240
- Category
- Hosting
- Headquarters
- London, UK
- Announced IPv4 prefixes
- 1283
- Registry
- RIPE
Known IP ranges
These prefixes are currently announced to the global routing table by AS62240 (Clouvider Clouvider Limited). Prefix sets change over time - use WHOIS Lookup for the authoritative record on any specific address.
2.56.188.0/22
173.255.160.0/22
85.239.60.0/22
185.198.188.0/22
200.162.156.0/22
45.86.208.0/22
185.175.136.0/22
92.119.16.0/22
162.120.68.0/22
216.169.140.0/22
2a0f:93c0::/29
2a04:92c0::/29
2a06:bdc0::/29 (IPv6)
What does a Clouvider IP mean in a privacy test?
The useful thing about AS62240 is that the name attached to an address and the party operating the machine are frequently different, and Clouvider publishes enough to tell them apart. Its aut-num remarks name eight transit suppliers by ASN, from Level3 AS3356 through to Telecom Italia Sparkle AS6762, and its geofeed states where Clouvider itself places each block it claims. Two of the largest prefixes the ASN originates fall outside that: 216.169.140.0/22 is an ARIN customer reassignment inside 216.169.128.0/20, netname RBLHST, a direct allocation to Strong Technology, LLC of New York, and 173.255.160.0/22 is covered by ARIN records named NETPR-NYC-CV registered to the same company. A third, 85.239.60.0/22, sits inside the RIPE allocation 85.239.32.0/19, netname RU-LLCTELART-20050616, held by the Moscow LIR LLC Telart. So a lookup returning Clouvider tells you whose router announced the address, and on this ASN that is often not whose service answered.
The geofeed Clouvider publishes, and what it leaves out
Clouvider publishes an RFC 8805 geolocation feed and makes it discoverable the correct way, with the reference sitting on the registry objects themselves. The inetnum for 2.56.188.0/22 carries geofeed: https://clouvider.com/geoipfeed.csv, and the very first remark on the aut-num is the same URL, ahead of the looking glass and the status page. The file is plain CSV in the five-field form of prefix, ISO country, ISO region, city and postcode, so rows read 2.56.188.0/22,US,US-TX,Dallas,75207 and 194.127.172.0/23,NL,,Amsterdam,1012KZ, with the region field left empty on UK rows and a building postcode in its place, as in 103.214.44.0/23,GB,,Manchester,M15 6SY. Alongside it the aut-num documents a do-not-announce community per upstream and per exchange, 62240:61 for Cogent, 62240:67 for NTT and 62240:69 for AMS-IX peers among them, plus prepend communities 62240:411 and 62240:401 and a 62240:45xx range that tags where a route was learned.
What the feed does not cover is most of the routing table. It ran to 287 rows when read for this page, and the granularity is whatever Clouvider chose rather than the announcement boundary: the first row is a /22, many rows are /23 or /24, and the last row is an IPv6 block, 2a0c:19c0::/32,US,US-GA,Atlanta,30303. Neither 173.255.160.0/22 nor 216.169.140.0/22 appears in it at all, and for those the ARIN record is the only source. The feed spans fourteen country codes, and the tail of that list is unusual for a British host: alongside US, GB, NL and DE there are rows for MC, LI, JE, IM, ME, BA, BY, AM, MT and UZ, as in 185.169.235.0/24,UZ,UZ-TO,Tashkent,100187. Each of those placements is Clouvider's own statement about where a block is used rather than a database estimate, which is why a prefix missing from the file needs a different source rather than a guess.
Clouvider's own space against a third party's
Reverse DNS is no help on this network. Sampled addresses in 2.56.188.0/22, 85.239.60.0/22, 185.198.188.0/22, 45.86.208.0/22, 92.119.16.0/22, 162.120.68.0/22, 185.175.136.0/22, 200.162.156.0/22, 216.169.140.0/22 and 173.255.160.0/22 all returned no PTR record, so the naming-convention trick that works on a consumer ISP is unavailable here. The check that does work is the allocation record for the exact prefix, and even Clouvider's own blocks are not uniform. 2.56.188.0/22 is netname UK-CLOUVIDER-20190315 with status ALLOCATED PA, while 200.162.144.0/20 is plain UK-CLOUVIDER with status LEGACY, and both record a country of US behind the UK netname.
The second signal is what sits on the far side of the record. ARIN space announced here resolves to somebody else: 216.169.140.0/22 is a reassignment dated 11 September 2024 to a customer entity recorded as NETPR-ATL-CV at 250 Williams Street in Atlanta, inside Strong Technology's 216.169.128.0/20, whose abuse contact is at strongtechnology.net rather than at Clouvider. PeeringDB files AS62240 as content, global in scope, at 1 to 5 Tbps with an open peering policy and the IRR set RIPE::AS-CLOUVIDER, and the aut-num carries a separate transit-customers section after the community list. So the working distinction on this ASN is not operator against customer but Clouvider-allocated space against a transit customer's own registry record: an address the geofeed places in one of Clouvider's cities is most likely a machine in Clouvider space, and an address absent from the feed with an ARIN or legacy record behind it belongs to a separate company that only that record names.
Related tools
Frequently asked questions
What does a Clouvider address mean in a privacy test?
It means the address is announced by a hosting and transit operator, not that Clouvider runs the machine. On AS62240 that distinction is live: several of the largest prefixes it originates are registered to Strong Technology, LLC at ARIN or to LLC Telart at RIPE. Check the allocation record and Clouvider's geofeed for the exact prefix before attributing the address to anyone.
Does Clouvider publish a geofeed?
Yes. The URL clouvider.com/geoipfeed.csv is the first remark on the aut-num for AS62240 and is repeated as a geofeed attribute on inetnum objects such as 2.56.188.0/22. It is a plain CSV of prefix, country, region, city and postcode, 287 rows when read for this page, and it covers only part of what the ASN announces.
Why does a Clouvider address geolocate outside the UK?
Because that is where Clouvider says the block is used. Its own feed places the largest prefix, 2.56.188.0/22, in Dallas, and other rows in Phoenix, Ashburn, Amsterdam, Manchester and Tashkent. Registry country fields are no guide either: the legacy allocation 200.162.144.0/20 carries the netname UK-CLOUVIDER and records a country of US.
Is every address on AS62240 owned by Clouvider?
No, and it matters more here than on most hosting networks. 216.169.140.0/22 is an ARIN reassignment inside a direct allocation to Strong Technology, LLC, 173.255.160.0/22 is covered by ARIN records registered to the same company, and 85.239.60.0/22 falls inside a RIPE allocation to LLC Telart in Moscow. Check the record for the exact prefix rather than trusting the ASN name.
Can I identify a Clouvider machine from its hostname?
Not usually. Sampled addresses across ten of the largest prefixes on this ASN returned no reverse DNS record at all. The allocation record for the prefix, and whether the prefix appears in Clouvider's geofeed, are the two checks that actually distinguish Clouvider space from third-party space announced by the same ASN.