Summary

  • The DIAMOND catalog at almazcloud.network sells five priced products, with Cloud Connect from 499 USD/month per physical 10G port and a claimed direct physical peering connection to Yandex, Sberbank and Rostelecom [https://almazcloud.network/].
  • The RIPE aut-num for AS210328, last modified 2026-08-21, names a single routing counterpart, AS48693, while its sponsoring organisation remains ORG-DNJ1-RIPE [https://whois.ipip.net/AS210328].
  • AS48693 (NTSERVICE-AS, Rices Privately owned enterprise, UA) is itself a small transit network with three upstreams and four downstreams, of which AS210328 is one [https://records.ping.pe/peers/AS48693].
  • The organisation object ORG-ZA238-RIPE (AO ALMAZ, OGRN 1196501003357) references maintainers belonging to other operators, including DN-MNT, the maintainer of Digital Network — the operator behind the sponsor LIR [https://nerd.cesnet.cz/nerd/org/ripe:ORG-DNJ1-RIPE].
  • No public customer, procurement or delivery record connects AO ALMAZ to any delivered cloud service.

The operator's own catalog is the most detailed public document about the business behind almazcloud.network. It presents the DIAMOND brand — "ALMAZ" in Russian — 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, a no-BGP GRE tunnel from 99 USD per month per 100Mbps, a corporate cloud VPN from 9 USD per month per user, and cloud reselling from 99 USD per month per connected cloud [https://almazcloud.network/]. The flagship product's central promise is connectivity: "direct physical peering connection to Yandex, Sberbank, ROSTELECOM, Selected and some other well known cloud providers". The same page offers to announce a customer's own AS or prefix "to our uplink providers" — wording consistent with a transit-reselling model rather than an operated cloud fabric.

The registry tells a narrower story. The RIPE aut-num object for AS210328 carries as-name ALMAZ, organisation ORG-ZA238-RIPE, and — since the 21 August 2026 edit — a routing policy naming exactly one counterpart: import "from AS48693 accept ANY", export "to AS48693 announce AS210328" [https://whois.ipip.net/AS210328]. The sponsoring organisation remains ORG-DNJ1-RIPE, unchanged through the edit [https://whois.ipip.net/AS210328]. The organisation object ORG-ZA238-RIPE is named AO ALMAZ, country RU, registration number 1196501003357, org-type OTHER, last modified 2026-05-13 [https://whois.ipip.net/AS210328]. Its mnt-ref list is the most revealing single line in the file: it names DN-MNT — the maintainer object of Digital Network, the operator behind the sponsor LIR — alongside FREENET-MNT and RETN-MNT, the maintainer of a large European transit operator [https://nerd.cesnet.cz/nerd/org/ripe:ORG-DNJ1-RIPE].

That linkage raises the first structural question. The sponsor LIR ORG-DNJ1-RIPE is associated with AS12695, a Russian hosting and ISP operator whose published services include channel and traffic products [https://tech.msm.ru/services/kanaly-i-trafik/]. If AO ALMAZ were an integrated member of that group, its network would plausibly depend on AS12695 for upstream connectivity. Yet AS12695 does not appear among AS210328's observed neighbours in any routing view retrieved for this report [https://ipgeolocation.io/browse/asn/AS210328] [https://bgp.he.net/AS210328]. The 2021 version of the aut-num named AS12695 as the routing counterpart; the August 2026 edit replaced it with AS48693 [https://whois.ipip.net/AS210328] [https://robtex.com/en/as-numbers/AS210328]. No public contract, sponsorship agreement or corporate filing documents the relationship between AO ALMAZ and Digital Network. The maintainership reference shows an administrative connection; it does not show who controls what.

The replacement counterpart deepens the question. AS48693 (NTSERVICE-AS, Rices Privately owned enterprise, UA, roughly 2,560 IPv4 addresses) is reported with three upstreams — AS59514 DARNYTSIA-NET, AS209155 onehostplanet, AS208846 ATOM3 — no lateral peers, and four downstreams, of which AS210328 ALMAZ appears with the smallest observation count [https://records.ping.pe/peers/AS48693]. In plain terms: the only network formally named as AS210328's routing partner is itself a small transit reseller, and AS210328 appears on its customer side of the ledger. A network whose flagship product promises direct physical interconnection to three of Russia's largest companies is, on the evidence of its own registry and routing records, a downstream customer of a Ukrainian transit network with three upstreams.

The observed routing footprint is small and, in parts, mismatched to the organisation that announces it. Hurricane Electric's toolkit reports AS210328 with three IPv4 prefixes, two announced, zero IPv6, two RPKI-valid origins and 512 IPv4 addresses originated [https://bgp.he.net/AS210328]. The prefixes carry third-party registrant descriptions: 77.91.65.0/24 is described as IP-FI-FotonTel (Foton Telecom CJSC), while 185.136.15.0/24 and 185.218.138.0/24 are described as Vlad-Cojuhari [https://ipgeolocation.io/browse/asn/AS210328] [https://bgp.he.net/AS210328]. ping.pe reports RPKI VALID for the first two prefixes and NOT-FOUND for the third [https://records.ping.pe/210328]. None of these names appears in the AO ALMAZ organisation chain, and the report did not locate any document connecting them to the operator. The registration-level attribution to AO ALMAZ and the prefix-level attribution to unrelated registrant names coexist in public data without explanation.

The neighbour set is equally inconsistent across observers. IPGeolocation lists AS202425 (IP Volume inc), AS201814 (MEVSPACE sp. z o.o.) and AS48693 in both its peers and upstreams tables [https://ipgeolocation.io/browse/asn/AS210328], while ping.pe reports no peers and no downstreams at all for AS210328 [https://records.ping.pe/210328] and Hurricane Electric observes three transit-type neighbours [https://bgp.he.net/AS210328]. These are vantage-point and time-window differences, but their combined effect is consistent: no routing observer shows AS210328 with a lateral peer of its own, and none shows it connected to Yandex, Sberbank or Rostelecom.

The PeeringDB record (net 19111) is operator-entered and lists 10-20Gbps capacity [https://www.peeringdb.com/net/19111] — a figure difficult to reconcile with a 512-address originated footprint and no observed peering sessions. Operator-entered directory data is self-attestation, not measurement, and in this case it is the only public source that describes scale beyond the routing table.

Finally, the delivery side is empty in every direction this report could search. No customer, procurement, regulatory or litigation record connects AO ALMAZ to any delivered service. No control plane, API documentation, status page or deployment footprint under almazcloud.network hostnames was located. DNS, certificate-transparency and reverse-DNS evidence was not obtained in this pass, so the mapping between almazcloud.network hostnames and AS210328's prefixes remains untested — an evidence boundary, not a settled conclusion.

What the dependency layer adds to prior BTW coverage — which examined the identity chain link by link and found no bridging document [https://btw.media/en/as210328-august-2026-registry-edit] — is a structural reading: the network is administratively attached to a sponsor LIR operating a different ASN, references that sponsor's maintainer and a third-party transit maintainer in its org object, and routes through a single small Ukrainian transit counterpart formalised only in August 2026. Each element is individually verifiable; together they describe a resale-shaped topology with no observable cloud infrastructure behind it.

Sources