Summary

  • Two distinct companies market services under the NovaCloud name: Nova Cloud LLP (AS214789, Almaty, Kazakhstan) and Tech Tide Portugal Unipessoal LDA (AS209874, Quarteira, Portugal). Neither RIPE object carries the handle novacloud-admin; the brand is a marketing layer above two legally unrelated registrations.
  • Observable routing is modest relative to marketed breadth: AS214789 originates 768 IPv4 addresses across three /24s with two Kazakh upstreams and no IPv6; AS209874 originates 17-22 IPv4 prefixes per divergent third-party views, roughly 4,352 IPv4 addresses, with three upstreams.
  • Nova Cloud LLP's commercial history includes a June 30, 2024 Memorandum of Understanding with IBA Group, dated Aug 1 (ibagroupit.com) and Aug 2 (EIN Presswire) in publication, naming CEO Doskhat Abdrassilov.
  • The routing evidence alone cannot confirm or deny that a functioning cloud service operates; it bounds what is observable today.

The question behind this briefing is simple: behind the NovaCloud name, is there a functioning cloud service or a dormant administrative artifact? The honest answer, from observable evidence, is that both operators are registered and actively routed but neither shows infrastructure at the scale its marketing implies.

AS214789: Nova Cloud LLP, Kazakhstan. Independent routing views agree on the essentials. bgp.he.net reports three IPv4 prefixes and zero IPv6 [[1]]; bgp.tools reports the same counts and names the prefixes 78.109.18.0/24, 91.147.110.0/24 and 194.164.115.0/24, attributed to Nova Cloud LLP [[2]]. CIDR Report independently tallies 768 IPv4 addresses (a /22.42 equivalent) across three prefixes, with two upstream adjacencies — AS43994 SMARTNET-AS and AS35104 KTC-AS — and zero downstreams [[3]]. IPinfo corroborates 768 IPv4 addresses and a May 31, 2024 allocation date [[4]]. The RIPE mirror at IPIP shows the organisation ORG-NC138-RIPE was created 2024-05-30 and the aut-num AS214789 (as-name nova-cloud-kz) created 2024-05-31 and last-modified 2024-07-02 [[5]]. SafeDeal, a Kazakhstan counterparties registry, records company 4820728 with BIN 240440015497 — matching ORG-NC138-RIPE's reg-nr — at Mynbaeva street 46, Almaty [[12]].

Two registry-level contradictions are visible on the same objects. HE labels 194.164.115.0/24 as 'Anna Revenko trading as Ip.Rent', while IPinfo and bgp.tools attribute the same /24 to Nova Cloud LLP [[1]][[4]][[2]]. And HE reports the AS214789 upstream set as AS35104 and AS43994, while the pasted aut-num import/export lines name AS41798 — a divergence between registry policy text and observed routing [[1]].

AS209874: Tech Tide Portugal, marketing the same brand. IPGeolocation reports AS209874's registered operator as Tech Tide Portugal Unipessoal LDA (ORG-MWUL2-RIPE, reg-nr 517354420, Quarteira, PT, as-name TECHTIDE), running novacloud-hosting.com, with aut-num created 2025-04-24 and last-modified 2026-02-26 [[6]]. Route counts diverge sharply across third-party views: HE reports 17 IPv4 and 17 IPv6 prefixes (34 total) [[7]]; bgp.tools reports 22 IPv4 and 16 IPv6 [[8]]; IPGeolocation reports 20 IPv4 and 17 IPv6 [[6]]; IPregistry reports 17 IPv4 and 22 IPv6 with 4,352 IPv4 addresses [[10]]. Upstream sets also disagree: HE lists AS49581, AS62403 and AS48314; bgp.tools lists AS203446, AS49581 and AS215787; IPGeolocation lists AS215787, AS62403 and AS49581; IPregistry lists AS48314, AS49581 and AS62403 [[7]][[8]][[6]][[10]]. The first-party site as209874.net markets the network as 'NovaCloud-Hosting Network', advertising IP transit across Europe with three PoPs in Germany and the Netherlands and self-declared upstreams AS62403, AS49581 and AS48314 [[9]] — a set that matches HE and IPregistry but not bgp.tools.

The novacloud-hosting.com imprint (a first-party legal notice) corroborates the Portugal identity: it binds the operator to Tech Tide Portugal Unipessoal LDA, register 517354420, at Rua Daniel Guerreiro Joao 4 4AB, 8125-598 Quarteira, Portugal [[11]].

The marketed service and its observable footprint. novacloud.kz markets a TIER II Almaty data centre with SLA 99.741%, VPS/VDS, IaaS, PaaS, SaaS and S3 storage on the ICDC platform, with first-party contact at Almaty, Khusainova street 281, BC Granit [[16]] — an address that differs from the RIPE-registered Mynbaeva street 46 [[12]]. The marketed services sit on infrastructure whose observable IPv4 footprint is 768 addresses — under three /22-equivalents — and whose observed upstreams are two Kazakh networks [[3]]. On the Portugal side, the marketed 'professional network infrastructure' across Europe rides on three upstreams and a prefix count that no two providers agree on [[7]][[8]][[6]][[10]].

Commercial history: the IBA Group MoU. IBA Group's own site dated Aug 1, 2024 reports a NOVA Cloud–IBA Group MoU signed June 30, 2024, announcing an ICDC-based cloud launch in Kazakhstan and naming Doskhat Abdrassilov as Nova Cloud CEO [[13]]. EIN Presswire distributed the same release on Aug 2, 2024, from a Prague dateline [[14]]. IBA Group's Kazakhstan site published the Russian-language version, again citing June 30, 2024 [[15]]. This MoU is the clearest commercial-history link: it anchors the Kazakhstan operator's ICDC platform partnership in a dated, named, first-party document chain.

Evidence table.

Question Observable answer Source
Is AS214789 registered? Yes — ORG-NC138-RIPE, BIN 240440015497 [[5]], [[12]]
What does AS214789 originate? 768 IPv4 across three /24s; no IPv6 [[1]], [[2]], [[3]], [[4]]
Who feeds AS214789? AS35104 and AS43994 [[1]], [[2]], [[3]]
Is AS209874 registered? Yes — ORG-MWUL2-RIPE, reg-nr 517354420 [[6]], [[11]]
What does AS209874 originate? 17-22 IPv4, 16-17 IPv6 per divergent views [[7]], [[8]], [[6]], [[10]]
Who feeds AS209874? Three upstreams; sets diverge by source [[7]], [[8]], [[6]], [[9]], [[10]]
Is there a commercial-history anchor? MoU June 30, 2024, with IBA Group [[13]], [[14]], [[15]]
Is there a marketed-datacenter claim? TIER II Almaty, SLA 99.741% [[16]]

What would distinguish an actively serving provider from a dormant artifact? Four observable markers: consistent prefix descriptions across third-party mirrors (currently contradicted on one /24), upstreams that match the registry's declared policy text (currently contradicted on AS214789), a customer-visible IPv6 presence for a marketed cloud (absent on the Kazakhstan side), and an address that matches the RIPE record (currently divergent on the Kazakhstan side). Today, both operators meet the minimum bar of being routed and registered; neither clears the higher bar that a functioning, scaled cloud service would imply. Sources: