Summary

  • On 21 August 2026 at 04:38:32 UTC, the RIPE aut-num object for AS210328 was last modified to name AS48693 as its routing-policy counterpart, replacing a 2021-era policy toward AS12695.
  • The edit changed only the policy lines. The sponsoring organisation on the object remained ORG-DNJ1-RIPE, and AS48693 itself is sponsored by a different LIR, ORG-LU47-RIPE — so the registry records no sponsorship transfer behind the swap.
  • Independent routing observations show no measurable change since the edit: three IPv4 prefixes originated, only two announced, 512 addresses, zero IPv6, and a transit-only topology with zero observed peers or downstreams.

The network registered in the RIPE region as AS210328 (as-name ALMAZ, org ORG-ZA238-RIPE) is marketed through the website almazcloud.network under the DIAMOND brand as a cloud services provider. Its aut-num object was created on 27 December 2021 and, apart from a single edit on 21 August 2026, has been nearly unchanged for almost five years. Two independent whois mirrors of RIPE output — whois.ipip.net and IPGeolocation.io — plus a Hurricane Electric page agree on the current content of that object: the import policy reads "from AS48693 accept ANY", the export policy reads "to AS48693 announce AS210328", the status is ASSIGNED, and the object still carries sponsoring-org ORG-DNJ1-RIPE (IPIP mirror, IPGeolocation mirror, Hurricane Electric).

The 2021 version of the same object, still served by some third-party databases, pointed at AS12695 instead. Robtex, for example, continues to serve a snapshot with as-name ALMAZCLOUD, a policy toward AS12695 and a last-modified timestamp of 28 December 2021 (Robtex). A buyer consulting one database therefore sees a different network than one consulting another.

The question that matters for a buyer is not which snapshot is current — it is what the August edit actually accomplished. The answer supported by the record is: one routing-relationship swap, and nothing else. The object's sponsoring organisation, ORG-DNJ1-RIPE (LLC Digital Network, org-type LIR), is the LIR that operates AS12695 itself — the very network named in the old policy (AS12695 record). The new counterpart, AS48693 (NTSERVICE-AS, Rices Privately owned enterprise, org ORG-RPOE1-RIPE), is sponsored by ORG-LU47-RIPE, a different LIR (AS48693 record). AS48693's own object lists a reciprocal policy toward AS210328 and was last modified on 15 September 2026.

So the registry records a mutual routing-policy declaration between two networks sponsored by two different LIRs, with no sponsorship or organisational change on the AS210328 side. That is consistent with a commercial transit or announcement arrangement between two independent operators — and inconsistent with any registry-level consolidation or capacity event.

The observable routing footprint confirms this reading. Hurricane Electric's toolkit records three IPv4 prefixes originated (77.91.65.0/24, 185.136.15.0/24, 185.218.138.0/24), only two of them announced, 512 originated IPv4 addresses, zero IPv6, and three observed BGP peers — all upstream-type relationships: AS202425, AS201814 and AS48693 (Hurricane Electric). RIPEstat's resource page, labelled as of 30 September 2026, lists two prefixes: 77.91.65.0/24 and 185.136.15.0/24 (RIPEstat). Nothing in these observations changed as a result of the edit; the topology remains transit-only, with zero observed peers or downstreams.

RPKI coverage tells a similar story of small, deliberate maintenance rather than growth. The two announced prefixes carry valid ROAs; the third, 185.218.138.0/24, is NOT-FOUND (ping.pe). Prior BTW reporting established that the ROA covering 185.136.15.0/24 has a not-before timestamp of 20 August 2026 — one day before the aut-num repoint — and that the only covering ROA for 185.218.138.0/24 (under asID 205997) was revoked on 24 August 2026 (BTW prior coverage). The four-day sequence — a ROA created, a policy repointed, an old ROA revoked — reads as coordinated registry housekeeping around a routing relationship, not as an infrastructure build-out.

Against this record stand the operator's own commercial claims. The almazcloud.network site markets Cloud Connect from $499 per month per 10G port, BGP announcements from $99 per month per prefix, a GRE tunnel from $99 per month per 100 Mbps, a cloud VPN from $9 per user, and cloud reselling from $99 per month — and claims a "direct physical peering connection to Yandex, Sberbank, ROSTELECOM" (operator site). No dated capacity, customer or growth figures appear in the retrieved content, and the claimed peerings are not corroborated by any public routing observation: zero observed peers means no collector anywhere sees those interconnects in BGP. Absence in public views is not proof that private interconnects do not exist, but it does mean a buyer cannot verify the claim from the routing system.

A third gap compounds the first two. Some third-party databases still describe the network as it was in 2021: Robtex serves the old AS12695 policy, and IPinfo is reported to label AS210328 "Inactive" with zero addresses. A buyer relying on a single database may conclude the network does not exist at all, or that its policy counterpart is a network that is no longer its counterparty. The primary RIPE sources that would settle the divergence directly — the REST aut-num object (RIPE REST), the RDAP record (RIPE RDAP) and the RIPEstat routing-status JSON (RIPEstat routing-status) — were not directly retrievable during the research pass for this article, so the registry and routing claims above rest on two independently corroborating mirrors and collector observations rather than on the primary endpoints themselves.

The overall picture at 30 September 2026: a live, maintained registry object that records exactly one change in almost five years — a routing-policy repoint to a network sponsored by a different LIR — with a stable, tiny routing footprint behind it, marketing claims that no public observation corroborates, and mirrors that disagree with each other about which decade they are describing.