Summary

  • Four public databases — Hurricane Electric's routing aggregator, PeeringDB, IPinfo and Qrator Radar — currently hand a prospective buyer four mutually exclusive pictures of AS210328, the RIPE autonomous system registered to AO ALMAZ and marketed through almazcloud.network under the DIAMOND brand.
  • Each divergence traces to a timestamp rather than to contested data: an aggregator current to late September 2026, a peering self-report last touched on 27 July 2022, a geolocation record frozen at 28 December 2021, and a routing-security window that closed on 25 September 2026.
  • The live registry and RPKI record supports a far smaller network than the vendor's price list implies: three originated IPv4 prefixes, two of them RPKI-valid, one disputed prefix announced under three origins, and a transit-only topology with no corroborated peering.

The four versions a buyer can retrieve

Hurricane Electric's ASN page is the most current of the group. It attributes AS210328 to AO ALMAZ with almazcloud.network as the company website and reports three IPv4 prefixes originated — 77.91.65.0/24, 185.136.15.0/24 and 185.218.138.0/24 — of which two are announced and RPKI-valid, totalling 512 originated IPv4 addresses, with three observed routing neighbours: AS202425, AS201814 and AS48693 Hurricane Electric's ASN page. The per-prefix view at ping.pe matches on the counts and sharpens the validation picture: 77.91.65.0/24 valid, 185.136.15.0/24 valid, 185.218.138.0/24 not found ping.pe.

PeeringDB disagrees in the opposite direction. Record 19111, registered to organization AO ALMAZ under the short name ALMAZCLOUD and the long name "ALMAZ (DIAMOND) CLOUD NETWORK", self-reports zero IPv4 prefixes and zero IPv6 prefixes alongside a claimed 10–20 Gbps of traffic, with the record fields last updated on 27 July 2022 and peering facility information dating to 2 January 2022 PeeringDB. A buyer who trusts this record concludes there is nothing to peer with.

IPinfo goes furthest of all. Its ASN record classifies AS210328 as Inactive, with zero IPv4 addresses, zero IPv6 addresses and zero hosted domains, in a record whose own update stamp reads 28 December 2021 — one day after the allocation IPinfo's ASN record. A buyer starting here concludes the network does not exist.

Qrator Radar observes from the other side of the disputed prefix. Its profile of AS205997 — Vlad Cojuhari, the competing origin — over the window from 25 June to 25 September 2026 shows zero active prefixes for that ASN, yet still lists 185.218.138.0/24 with unknown RPKI and route-object status at 1.40% propagation, and 185.136.15.0/24 as valid with 100% propagation Qrator Radar.

Two further mirrors widen the spread. iptrace.net still carries a 2021-era import/export policy naming AS12695 as the system's counterpart — a policy the registry itself has since replaced iptrace.net — and IPIP's whois viewer maintains its own record of the same ASN IPIP's whois record.

What the live record shows

Four anchored facts, each checkable against the registry and cryptographic layers:

  • Registration and policy. AS210328 is registered in RIPE to AO ALMAZ under organization org-za238-ripe, country RU, allocated on 27 December 2021, with almazcloud.network declared as the website; the same mirror's embedded registry objects show the aut-num importing from and exporting to AS48693 with a last-modified stamp of 21 August 2026 at 04:38:32 UTC IPGeolocation's AS210328 record. Hurricane Electric's page embeds the identical aut-num.
  • RPKI. The RIPE RPKI validator and the rpki-client console show exactly two current ROAs for the system, covering 77.91.65.0/24 and 185.136.15.0/24, each with a maximum prefix length of 24, according to RIPE's RPKI validator and the rpki-client console.
  • The disputed prefix. 185.218.138.0/24 is announced under three origins — AS209630 (LLC VASH KREDIT BANK), AS205997 (Vlad Cojuhari) and AS210328 (AO ALMAZ) — within the RIPE delegation 185.218.136.0/22 Hurricane Electric's prefix page. The only ROA that had covered it, issued to AS205997, was revoked on 24 August 2026, as BTW's reconstruction of the August sequence established from the ROA object still published in the repository BTW's report on the August sequence and the ROA object. IPinfo's prefix page nonetheless still labels the same prefix RPKI-valid under AS205997 IPinfo's prefix page.
  • Topology. Observed routing describes a transit-only network: three upstreams — AS202425, AS201814 and AS48693, which other mirrors name as IP Volume inc, MEVSPACE sp. z o.o. and Rices Privately owned enterprise — with no observed peers and no observed downstreams, as BTW's earlier briefing on the network documented BTW's 26 September briefing.

Where commerce meets the record

The vendor's own pages make the stakes concrete. The almazcloud.network site sells Cloud Connect from $499 per month per physical 10G port, BGP announcement services from $99 per month per prefix, no-BGP GRE tunnels from $99 per 100 Mbps, a corporate cloud VPN from $9 per user per month and cloud reselling from $99 per connected cloud, and advertises direct physical peering connections to Yandex, Sberbank and Rostelecom the almazcloud.network site. Not one of those peerings is corroborated by any routing observation in the evidence set. What the record does show is a network that reaches the rest of the internet through three transit providers and sells prefix announcements — including, on its own third prefix, an announcement that currently has no RPKI protection of its own.

One evidence boundary belongs in the open. Every snapshot behind this briefing arrived as a search-index excerpt with an unknown crawl window, so individual counters are dated observations rather than live queries. The durable finding is the divergence pattern itself: four databases, four timestamps, four versions of the same network — and a live registry layer that lets a careful reader reconcile all of them.