Summary

  • almazcloud.network advertises five priced products, headlined by Cloud Connect from 499 USD/month per physical 10G port with a claimed direct physical peering connection to Yandex, Sberbank, Rostelecom and other well-known providers. https://almazcloud.network/
  • Every independently observable routing record examined on 30 September 2026 describes AS210328 as transit-only, with three upstreams (AS202425 IP Volume inc, AS201814 MEVSPACE, AS48693 Rices) and zero observed peers or downstreams. https://bgp.he.net/AS210328 https://ipregistry.co/AS210328 https://records.ping.pe/210328
  • IPinfo alone classifies the same autonomous system as Inactive with zero addresses — a mirror-divergence that turns any pre-purchase lookup into a choice between contradictory snapshots. https://ipinfo.io/AS210328
  • The abuse role published in the RIPE record states that replies are given only to emails written in Russian, which narrows the practical complaint path for the international market the price list targets. https://whois.ipip.net/AS210328

The autonomous system behind almazcloud.network is registered in the RIPE region to AO ALMAZ (ORG-ZA238-RIPE, registration number 1196501003357), with the network named ALMAZ and the routing policy last modified on 21 August 2026 at 04:38:32 UTC to name AS48693 as its counterpart. https://whois.ipip.net/AS210328 That edit and the network's stale third-party mirrors have already been examined in prior BTW coverage of the registry swap and the identity gap. https://btw.media/en/almazcloud-network-as210328-briefing https://btw.media/en/almazcloud-network-identity-verification This briefing asks a different question: what does the operator's own commercial catalog claim, and does the measurable footprint of the network support those claims?

The first-party price list https://almazcloud.network/ is the sole source for the product line: Cloud Connect from 499 USD/month per physical 10G port; BGP announcements from 99 USD/month per announced prefix; a no-BGP GRE tunnel from 99 USD/month per 100 Mbps; a corporate cloud VPN from 9 USD/month per user; and cloud reselling from 99 USD/month per connected cloud. Its headline mechanism is the claim of direct physical peering to Yandex, Sberbank, Rostelecom and other well-known providers — a claim that would be trivially visible in BGP data if it existed, because direct peering produces observed sessions.

The routing evidence does not show them. Hurricane Electric's toolkit attributes AS210328 to AO ALMAZ and reports three IPv4 prefixes originated, two announced, two RPKI-valid, 512 IPv4 addresses originated, and exactly three observed peers/upstreams: AS202425, AS201814 and AS48693. https://bgp.he.net/AS210328 Ipregistry classifies the AS as type Hosting and states explicitly that it has no direct peering agreements and no downstream networks, reaching the internet through transit AS48693 and AS202425; it also lists the IPv6 block 2001:67c:29c::/48 assigned to AO ALMAZ. https://ipregistry.co/AS210328 ping.pe shows the same three upstreams, no peers and no downstreams, with RPKI status VALID on 77.91.65.0/24 and 185.136.15.0/24 and NOT-FOUND — no covering ROA — on 185.218.138.0/24. https://records.ping.pe/210328 RIPEstat's own view, timestamped 30 September 2026 15:37:00, lists only two announced prefixes, omitting the third entirely and assigning 185.136.15.0/24 to Kazakhstan rather than Russia. https://stat.ripe.net/resource/AS210328

The divergence among databases is itself part of the finding. IPinfo classifies AS210328 as Inactive with zero IPv4 and IPv6 addresses, zero hosted domains and empty peer, upstream and downstream sections, last updated 2021-12-28 — a picture that contradicts every other source retrieved. https://ipinfo.io/AS210328 One intended source, bgp.tools' dedicated AS210328 record, could not be retrieved in this research pass; nothing from it is asserted here, and its content is disclosed as non-retrievable rather than omitted silently. https://bgp.tools/as/210328 On reputation, no Spamhaus SBL listing specific to AS210328 or almazcloud.network was identified in this pass; that is a bounded absence-of-listing observation, not a clearance. https://www.spamhaus.org/blocklists/spamhaus-blocklist/

The evidence boundary matters as much as the finding. The price list was inspected through a provider-reported search excerpt rather than a rendered page, so wording and prices may have changed; all aggregator values are snippet-indexed with unknown observation windows. What holds regardless is the structural logic: a direct physical peering relationship to named networks is the kind of claim that routing observation either confirms or leaves unsupported, and in every record retrieved it is unsupported. A buyer evaluating the 499 USD Cloud Connect product is therefore paying for an adjacency that no public routing source shows, while the abuse role in the registry limits replies to Russian-language correspondence. https://almazcloud.network/ https://whois.ipip.net/AS210328