Summary

  • kz-novacloud-mnt appears as a maintainer on the aut-num AS214789 (as-name nova-cloud-kz, created 2024-05-31T07:40:06Z), on the organisation object ORG-NC138-RIPE — Nova Cloud LLP, registered in Almaty — and on the person object MV16118-RIPE (1, 2, 3).
  • The route object for 78.109.18.0/24, originated by AS214789, is maintained by mnt-kz-anna-1, created 2025-10-24T17:52:49Z — a maintainer outside the NovaCloud chain (4, 5).
  • The authoritative RIPE mntner object for kz-novacloud-mnt was not directly retrieved in this research; all maintainer findings come from third-party mirrors whose snapshot dates visibly differ (6).

In RIPE's registry model, a maintainer authorises the creation and modification of objects. Whoever controls the mnt-by credential controls whether an AS registration, an organisation record or a contact object can be altered. So for a cloud provider trading under a brand, the maintainer chain — not the brand — is the verifiable administrative identity.

The mirror evidence assembled here is consistent on the core structure. The aut-num AS214789 carries exactly two maintainers, the RIPE NCC's end-user maintainer and kz-novacloud-mnt (1, 3). The organisation object ORG-NC138-RIPE — Nova Cloud LLP, country KZ, registration number 240440015497, addressed on Mynbaeva street in Almaty — lists kz-novacloud-mnt in both mnt-by and mnt-ref, meaning the maintainer both is protected by and can authorise objects under that organisation (1). The person object MV16118-RIPE, Malinovsky Vladimir, created 2024-05-30T05:50:14Z and apparently never modified, is protected by the same maintainer (1).

The routing profile sharpens the picture. Independent views describe AS214789 as an origin-only stub: two upstreams (AS43994 SMARTNET-AS and AS35104 KTC-AS), zero downstreams, three originated IPv4 /24s totalling 768 addresses, no IPv6, and RPKI origin validation reported valid for all three prefixes (2, 3, 5). Independent AS rankings and Cloudflare's routing view match that profile (bgp.tools AS214789, Cloudflare Radar AS214789, ip.cc registry mirror). That is a small, real footprint — but the interesting finding is upstream of the routes.

The route object for 78.109.18.0/24, which AS214789 originates, is maintained by mnt-kz-anna-1 and was created on 2025-10-24, months after the AS itself (4). The same prefix carries a description naming a different entity, "Anna Revenko trading as Ip.Rent", while neighbouring prefixes on the same AS are described as "Nova Cloud LLP" and "Nova-Cloud" (5, 1). In registry terms this means authorisation to create or change the route object — the object that legitimises the announcement — sits with a maintainer credential that does not appear on the aut-num, the organisation or the person object.

Two caveats bound these conclusions. First, the underlying allocation for the block is a /23 allocated to a KZ recipient, and aggregator descriptions are derived labels, not authoritative attributions (4). Second, the mirrors themselves disagree on timestamps: the organisation object's last-modified date reads 2024-05-31 on one mirror, 2026-04-29 on another and 2026-05-13 on a third (1, 2). And the mntner object kz-novacloud-mnt itself — its authentication mechanism, its own creation date and its full protected-object set — was never directly retrieved, so the research only proves its linkage from the objects it protects (6).

The dossier for this maintainer object, including every source used here, is maintained at 7.