Summary

  • The operator's catalogue makes five priced claims; independent routing evidence corroborates one framing of the network's cryptographic posture, contradicts its headline peering claim, and leaves its capacity figures unaddressed.
  • Two of three originated IPv4 /24 prefixes are announced with valid RPKI authorizations; the third is a multi-origin prefix whose only covering ROA was revoked on 24 August 2026.
  • Third-party registry mirrors disagree sharply about what this network is, and the disagreement is a data-quality problem about the mirrors, not a finding about the operator.

The operator's own website is the sole first-party source for its product line. It presents DIAMOND ("on rus. ALMAZ") as "a brand new progressive cloud services provider" and prices five products: CLOUD CONNECT from 499 USD per month per physical 10G port, BGP ANNOUNCEMENTS from 99 USD per month per announced prefix, NO-BGP GRE TUNNEL from 99 USD per month per 100Mbps, CORPORATE CLOUD VPN from 9 USD per month per user, and CLOUD RESELLING from 99 USD per month per connected cloud operator site. The page's headline offer is a "Direct physical peering connection to Yandex, Sberbank, ROSTELECOM, Selected and some other well known cloud providers." No capacity figures, facility list, customer count or traffic statistics appear anywhere on that page — a fact worth stating plainly, because the rest of this ledger is built from what other parties have published about the same network.

The observable footprint

Hurricane Electric's BGP toolkit attributes AS210328 to AO ALMAZ (RIPE region, allocated 27 December 2021) with three IPv4 prefixes originated, two announced, two RPKI-valid, zero IPv6, 512 IPv4 addresses and 717 observed AS paths Hurricane Electric. The embedded RIPE aut-num object — as-name ALMAZ, organisation ORG-ZA238-RIPE — was last modified at 04:38:32 UTC on 21 August 2026, switching the import policy to accept ANY from AS48693; the original December 2021 policy pointed at AS12695 Hurricane Electric. IPGeolocation's ASN mirror confirms the same 2026-08-21 modification and the organisation's registration number 1196501003357, and lists the same three autonomous systems — AS202425 (IP Volume inc), AS201814 (MEVSPACE sp. z o.o.) and AS48693 (Rices Privately owned enterprise) — as both peers and upstreams IPGeolocation.

Per-prefix validation is where the record splits. ping.pe lists the three prefixes under origin AS210328 and reports 77.91.65.0/24 as RPKI VALID, 185.136.15.0/24 as RPKI VALID, and 185.218.138.0/24 as RPKI NOT-FOUND ping.pe. The rpki-client validation console agrees structurally: exactly two ROA payloads are published for asID 210328 — 77.91.65.0/24 with maxlen 24 and 185.136.15.0/24 with maxlen 24, both in the RIPE repository — and no ROA payload for the third prefix under that AS ID rpki-client console.

The third prefix carries its own documented history. The only ROA that ever covered 185.218.138.0/24 was issued to a different origin, asID 205997, signed on 18 February 2026 with a nominal expiry of 1 July 2027 — and its certificate was revoked on 24 August 2026 at 05:53:28 UTC ROA object. That prefix is a multi-origin advertisement, announced by AS209630 (LLC VASH KREDIT BANK), AS205997 (Vlad Cojuhari) and AS210328 (AO ALMAZ), and its registrant of record, Vlad Cojuhari, is not the registrant of the origin AS210328 Hurricane Electric prefix page. IPinfo's range pages for the prefix still describe it as RPKI valid under AS205997, which the revoked certificate record contradicts IPinfo range page.

What independent data says about interconnection

Prior reporting on this network — assembled from ping.pe peer records and IPregistry data — described three upstreams (AS202425 seen 290 times, AS201814 seen 267 times, AS48693 seen once), and explicitly no observed peers and no observed downstreams, with no direct peering agreements in IPregistry's record BTW briefing. Hurricane Electric's neighbour table lists the same three ASes, all transit-type Hurricane Electric. Every one of those observations carries an observation window; none of them can be read as a permanent statement that the network "has no peers." They say: as observed, within these windows, on these vantage points, no lateral interconnection or downstream appeared.

PeeringDB record 19111 — ALMAZCLOUD, AO ALMAZ, long name "ALMAZ (DIAMOND) CLOUD NETWORK" — is the only facility-level capacity evidence in the public record, and it is operator-entered: self-reported zero IPv4 and zero IPv6 prefixes, 10–20Gbps of traffic, presence in three Moscow facilities (Berzarina Data Center, IXcellerate MOS1, Moscow M9), with fields last updated 27 July 2022 PeeringDB. Its self-reported prefix count of zero conflicts with the three originated /24s visible in routing data — an illustration of record drift inside a single operator-maintained source.

The mirror problem

Third-party registries do not agree on what this network is. IPinfo classifies AS210328 as "Inactive" with zero hosted domains and zero addresses, freezing the ASN at its December 2021 registration state IPinfo. IPTrace still mirrors the 2021 aut-num — as-name ALMAZCLOUD, AS12695 import policy, last modified 28 December 2021 — alongside the same three facility names IPTrace. The live RIPE object, last modified 21 August 2026, contradicts both. This staleness belongs to the mirrors as a data-quality finding: aggregator refresh incentives for small ASNs are weak, and the lag says nothing about the operator's conduct. But it does mean that a reader whose search lands on IPinfo or IPTrace first will form a materially wrong picture of an actively revised network.

Prior BTW coverage reconstructed the August 2026 sequence — the 21 August registry rewrite and the 24 August ROA revocation — and stated explicitly that first-party peering and capacity claims remained uncorroborated by any routing observation BTW RPKI window report.

The directory entry for this article's subject is maintained at BTW.

The ledger

Reading the catalogue against the record, claim by claim:

  • Direct physical peering to Yandex, Sberbank, Rostelecom (operator claim) — attributed contradiction. The operator's page asserts it operator site; three independent observation sources report upstream-only topology with no observed peers BTW briefing. Both sides are named; no verdict is rendered on intent.
  • Two of three prefixes RPKI-valid under AS210328 — corroborated. ping.pe's VALID/VALID/NOT-FOUND split, the two-ROA console listing and Hurricane Electric's counters agree ping.pe, rpki-client console.
  • The third prefix is usable for route-origin-validating customers — contradicted as of the record. Its only covering ROA was revoked on 24 August 2026, and any announcement of it is RPKI-invalid for enforcing networks ROA object.
  • 10–20Gbps traffic and three Moscow facilities — unaddressed. Self-declared in a PeeringDB record roughly four years old at observation time PeeringDB.
  • An operating, revised network posture — corroborated at the registry layer only: the live aut-num was modified 21 August 2026 IPGeolocation, even as mirrors call the network inactive IPinfo.

The record does not discriminate between benign explanations — small scale, aspirational marketing language, delayed aggregator refresh, peering arrangements invisible to public vantage points — and overstatement. All remain hypotheses. AO ALMAZ can close several of these questions claim-by-claim, by refreshing its PeeringDB record, by publishing any peering agreement evidence, or by re-establishing cryptographic coverage for the disputed prefix.