almazcloud.network

At a glance

• Autonomous system numberLinked with AS210328, AS202425, AS201814, AS48693 +2High confidence
• Address blocks1 address block currently recordedHigh confidence

Basic information

• Display namealmazcloud.networkHigh confidence
• Directory categoryCompanyHigh confidence
• Last updatedJun 15, 2026High confidence

Locations

• Geography scopeUnited StatesHigh confidence
• ColocationUnited StatesMedium confidence
• Internet accessUnited StatesMedium confidence
• IP transitUnited StatesMedium confidence
• Peering and IXPsUnited StatesMedium confidence
• HostingUnited StatesMedium confidence

What it does

• ColocationUnited States, Colocation provider, almazcloud.network's public recordHigh confidence
• Internet accessUnited States, Internet access provider, almazcloud.network's public recordHigh confidence
• IP transitUnited States, IP transit provider, almazcloud.network's public recordHigh confidence
• Peering and IXPsUnited States, Peering or exchange entity, almazcloud.network's public recordHigh confidence
• HostingUnited States, Hosting provider, almazcloud.network's public recordHigh confidence

Network identity

• Autonomous system numberAS210328High confidence
• Autonomous system numberAS202425High confidence
• Autonomous system numberAS201814High confidence
• Autonomous system numberAS48693High confidence
• Autonomous system numberAS12695High confidence
• Autonomous system numberAS205997High confidence

IP address resources

Other network resources

• Data centeralmazcloud.network United States Colocation · United StatesHigh confidence
• Service platformalmazcloud.network United States Internet access · United StatesHigh confidence
• Service platformalmazcloud.network United States IP transit · United StatesHigh confidence
• Internet exchangealmazcloud.network United States peering/IXP · United StatesHigh confidence
• Service platformalmazcloud.network United States Hosting · United StatesHigh confidence

Registry and related records

• Editorial contextInside almazcloud.network's Corporate Substance: A Fish-Farm Registration Behind a Cloud Storefront, The operator behind AS210328 markets dollar-priced cloud interconnection under the DIAMOND brand. The registration number on its RIPE organisation object belongs to a two-person marine-fish-farming company in Yuzhno-Sakhalinsk. This report assembles the corporate ledger, the storefront and the routing record, and states precisely what the divergence does and does not prove.Medium confidence
• Editorial contextThe Self-Report Test: Auditing almazcloud.network's Identity Against AS210328, The DIAMOND-branded operator behind almazcloud.network describes itself as a 'brand new progressive cloud services provider' selling direct physical peering to Russia's largest networks. Every independently observable fact about its autonomous system describes something smaller, older and quieter. This report runs the operator's own claims against the public record — and finds divergence at every layer of the identity chain at once.Medium confidence
• Editorial contextRecord Hygiene or Real Movement? What AS210328's 2026 Ledger Edits Actually Changed, The operator behind almazcloud.network — the DIAMOND-branded network registered to AO ALMAZ, RIPE autonomous system AS210328 — has been quiet in the market but active in the ledger. Prior BTW coverage documented the split: registry objects and routing authorisations carry dated 2026 edits, while the commercial storefront and observable routing have barely moved since 2022. What no one has yet examined is the content of those edits. Three changes stand out: an organisation-object edit on 13 May 2026, an aut-num policy change on 21 August 2026, and a new ROA over 185.136.15.0/24 created 20 August 2026. The question this briefing answers is narrow and answerable: did any of this change what the network does, or only what the record says?Medium confidence
• Editorial contextThe Ledger and the Storefront: AS210328's 2026 Registry Edits Against a Network Frozen Since 2022, Every network runs on two clocks. One is administrative: the ledger of registry objects, routing policies and routing authorizations that says who may announce what, through whom, and when someone last touched the record. The other is commercial: the storefront of product pages, self-reported traffic levels and peering intentions that says what a network claims to sell. For most live operators, the two clocks tick together. For the DIAMOND-branded operation behind almazcloud.network — RIPE autonomous system AS210328, registered to an organisation named AO ALMAZ — the clocks have separated in an unusual and measurable way. The ledger shows dated edits through 2026; the storefront, and the routing table beneath it, show no movement since 2022.Medium confidence
• Editorial contextThe Operator That Isn't On Its Own Network: Testing almazcloud.network's Delivery Claims Against AS210328, The DIAMOND-branded cloud operator behind almazcloud.network sells priced products built on a single promise: direct physical connections to Russia's largest networks. Its own published footprint — the routing table, the RPKI state, the registry — tells a smaller story, and the operator's own services are nowhere to be found on the address space it sells. This report tests that gap from the delivery side, a question prior coverage of the registry, the dependency layer and the identity chain did not ask.Medium confidence
• Editorial contextBrokerage Disguised as Infrastructure: What almazcloud.network's Footprint Means for AI-Era Compute Buyers, A cloud brand selling dollar-priced interconnects, GPU-era resale and direct peering to Russia's largest networks can be tested against the routing table. For AS210328, the table says the product is trust, not capacity.Medium confidence
• Editorial contextThe Dependency Layer Behind almazcloud.network: A Sponsoring LIR, a Ukrainian Transit Counterpart and No Delivery Trail, Every product the DIAMOND-branded operator behind almazcloud.network sells is priced in dollars; every measurable fact about its network is priced in dependencies. This report follows the dependency chain from the RIPE registry to the routing table and asks what a buyer can actually verify.Medium confidence
• Editorial contextThe Identity Chain Nobody Closes: What Can Actually Be Verified About almazcloud.network, AS210328 and AO ALMAZ, Every public signal a buyer can check about the operation behind almazcloud.network is individually verifiable. The DIAMOND brand exists on a website. The domain resolves to an autonomous system, AS210328, registered in the RIPE region to an organisation named AO ALMAZ. The RIPE record names a sponsoring LIR, ORG-DNJ1-RIPE. A Russian corporate-registry aggregator links the OGRN number printed in the RIPE organisation object to a company called AO ALMAZ — in Yuzhno-Sakhalinsk, on the other side of the country from the Moscow interconnection facilities the operator's own PeeringDB record claims. What no retrieved public source provides is a single document that connects these links into one chain: no contract, no corporate filing, no payment trail, no customer, no delivery record. This report examines each link, identifies precisely what is missing to close them, and asks what a buyer can — and cannot — conclude as of 4 October 2026.Medium confidence

Source basis

• public registry sourcealmazcloud.network's public recordHigh confidence
• public webRIPEstat · Public network recordHigh confidence

How to read these connections

• Address compositionThe visible prefix footprint is IPv6-only with 1 announced prefixes.Medium confidence

Related research

• Primary articleInside almazcloud.network's Corporate Substance: A Fish-Farm Registration Behind a Cloud StorefrontHigh confidence
• Primary articleThe Self-Report Test: Auditing almazcloud.network's Identity Against AS210328High confidence
• Primary articleRecord Hygiene or Real Movement? What AS210328's 2026 Ledger Edits Actually ChangedHigh confidence
• Primary articleThe Ledger and the Storefront: AS210328's 2026 Registry Edits Against a Network Frozen Since 2022High confidence
• Primary articleThe Operator That Isn't On Its Own Network: Testing almazcloud.network's Delivery Claims Against AS210328High confidence
• Primary articleBrokerage Disguised as Infrastructure: What almazcloud.network's Footprint Means for AI-Era Compute BuyersHigh confidence
• Primary articleThe Dependency Layer Behind almazcloud.network: A Sponsoring LIR, a Ukrainian Transit Counterpart and No Delivery TrailHigh confidence
• Primary articleThe Identity Chain Nobody Closes: What Can Actually Be Verified About almazcloud.network, AS210328 and AO ALMAZHigh confidence
• Primary articleA Price List Built on Peering It Cannot Show: Auditing almazcloud.network's Commercial Catalog Against AS210328's Measured FootprintHigh confidence
• Primary articleThe Routing-Policy Swap Behind AS210328: What the August 2026 Registry Edit Changed — and What It Did NotHigh confidence
• Primary articleAS210328 After the August 2026 Registry Edit: What Changed, and What Still Cannot Be VerifiedHigh confidence
• Primary articleAS210328 Today: What the Live Record Shows — and Fails to Show — About AO ALMAZ's Cloud NetworkHigh confidence
• Primary articleThe Registry Says One Company, the Records Say Another: Inside AS210328's Identity GapHigh confidence
• Primary articleFour Databases, Four AlmazClouds: The Incompatible AS210328 a Buyer Meets in September 2026High confidence
• Primary articleThe Corroboration Ledger: What the Public Record Can — and Cannot — Confirm About almazcloud.networkHigh confidence
• Primary articleThe Four Days That Secured a Network: How AS210328 Acquired Its RPKI Cover in Late August 2026High confidence
• Primary articleAlmazCloud After the August Revisions: What AS210328's Current Record Shows — and What It Still Refuses to SettleHigh confidence
• Primary articleAlmazCloud's Commercial Story Meets the Routing Record: What AS210328 Can Actually SellHigh confidence
• Primary articleAlmazCloud's AS210328: What the Routing Record Now Shows — and What It Still Doesn'tHigh confidence
• Primary articleAlmazCloud’s AS210328: The Operating Chain Still Has to Be DemonstratedHigh confidence
• Primary articleAlmazCloud’s AS210328: The Operating Chain Still Has to Be DemonstratedHigh confidence
• Primary articleAlmazCloud’s AS210328: The Operating Footprint Still Has to Be ShownHigh confidence
• Primary articleAlmazCloud’s AS210328: The Operating Footprint Still Has to Be ShownHigh confidence
• Primary articleAlmazCloud’s AS210328: What the Public Record Can—and Cannot—VerifyHigh confidence
• Primary articleAS210328 After Registration: The Missing Link Between Network Identity and Cloud ServiceHigh confidence
• Primary articleAlmazCloud’s ASN Is Registered. What Can Be Shown as Operating?High confidence