OPERBAZA.ORG · OPEN-SOURCE INTELLIGENCE & SANCTIONS COMPLIANCE REGISTRY · VERIFIED PRIMARY REGISTRIES & DOCUMENTARY ARCHIVES
OPERBAZA.ORG OSINT / COMPLIANCE REGISTRY

Cross-Registry Open-Source Intelligence Synthesis System (OSINT Data Fusion): linking disparate Russian and Ukrainian state registries, botfarm graphs, GEOINT, and sanctions databases into a single chain of evidence

Synthesis Formula (How disparate open data yields new analytical quality)
01 · VPK & SANCTIONS ANATOMY [/vpk]
→ Precision Targeting & Sanctions Blind Spots
02 · RF MILITARY LOGISTICS, POWS & RESIDENCY [/z]
→ Deconstructing Cover Stories, RF Forces Financing & FSB Networks
03 · MOLES IN EDR & IPSO PROOF OF INTENT (ART. 111 CCU) [/edr]
→ Exposing Sleeper Assets & Deliberate Coordination with the Enemy
UA EN
OSINT BLIND SPOTS 9 MIN READ 2026-11-05 · M-13
← All Tradecraft & Op-Eds (/en/methods)

Amsterdam's BGP Router for Iskanders and Rostec: How RIPE NCC (KvK 40539632) Dismisses 90.12% of Sanctions Alerts and Signs RPKI ROAs for Russian VPK and Occupied Melitopol Telecom

On 22 October 2026, the Amsterdam-based Regional Internet Registry RIPE NCC (Stationsplein 11, KvK 40539632) published its Q4 2026 Quarterly Sanctions Transparency Report (RIPE-868): out of 2,339 EU/OFAC sanctions alerts since April 2022, 2,108 (90.12%) were dismissed, and the Russian Federation accounts for a microscopic 0.32% (15,616 out of 4,850,688) of frozen IPv4 addresses. Using primary records from rest.db.ripe.net and live BGP/RPKI telemetry, we demonstrate how IT and telecom subsidiaries of EU-sanctioned Russian defense holdings (Rostec, Rosatom, Almaz-Antey, KTRV, UAC, USC, VGTRK, ANO Dialog, Zvezda, TsNIIMash) and occupied Melitopol telecom hold 35 ASNs and 117,024 unfrozen IPv4 addresses in Amsterdam valued at $2.22 million.

1. The Myth of the 'Sovereign Runet' and the Building at Stationsplein 11 in Amsterdam

Whenever Russian generals and Ministry of Digital Development officials boast on television about a 'sovereign, import-independent Runet', observers outside network engineering often imagine a master switch in Moscow. In reality, global packet routing between Russian defense conglomerates, missile design bureaus, state corporation data centers, and the outside world rests on the legal foundation of a single association incorporated under Dutch law (*Vereniging*) across from Amsterdam Central Station: Réseaux IP Européens Network Coordination Centre (RIPE NCC), Stationsplein 11, 1012 AB Amsterdam, Netherlands, Dutch Chamber of Commerce registration KvK 40539632 (RSIN 801699036; Managing Director: Hans Petter Holen; Chief Legal Officer: Athina Fragkouli).

Operating under the jurisdiction of the Kingdom of the Netherlands, RIPE NCC exercises a regional monopoly over:

As a Dutch legal entity, RIPE NCC is strictly bound by the Dutch Sanctions Act (Sanctiewet 1977), Article 2 of Council Regulation (EU) No 269/2014 (freezing all funds and economic resources belonging to, owned, held, or controlled by designated entities and their 50%+ subsidiaries), and Article 5n of Council Regulation (EU) No 833/2014 (prohibiting IT consultancy, cloud, and technical services to legal persons established in Russia).

2. Mathematical Verdict from RIPE NCC's Own Disclosure: Inside Document RIPE-868 (Q4 2026)

On 22 October 2026, RIPE NCC published its latest quarterly disclosure — RIPE-868: Quarterly Sanctions Transparency Report (Q4 2026) (URL: https://www.ripe.net/documents/4651/ripe-868.pdf, SHA-256: 0878f45e835fcc5d0a83be7fc503c6bbebbb60fd24ae5882e18738b35c84135e; preceding Q3 2026 edition published 23 July 2026: RIPE-864, SHA-256: 6ad502852539e7939abd27387365842262851a66690eec5c0e0fd2f0246b08b8).

The official figures in Table 1 and Table 2 of RIPE-868 (status as of 1 October 2026) expose a systemic compliance failure:

Why does Amsterdam's screening pipeline dismiss 90.12% of alerts? Because RIPE NCC screens Latin-transliterated organisation names largely for literal string matches against Annex I of Regulation (EU) No 269/2014, systematically failing to trace 50%+ ownership and control (EU Best Practices for the effective implementation of restrictive measures, paras. 62–68) across wholly-owned IT integrators, telecom subsidiaries, and dedicated LIR shields of sanctioned Russian defense holdings.

3. How Table 2 of RIPE-868 Mathematically Proves that Rostec, Rosatom, UAC, and VGTRK Pools Remain Unfrozen

Because Table 2 of RIPE-868 itemizes every single one of the 32 frozen or on-hold Russian entries by exact type (Member vs. End User), IPv4 count, IPv6 count, and ASN count, cross-referencing RIPE-868 against live queries to rest.db.ripe.net and stat.ripe.net as of 5 November 2026 yields mathematical proof of non-freezing:

4. Cryptographic RPKI ROAs Signed by RIPE NCC Root: TsNIIMash Missile Institute, Russian MoD Broadcaster Zvezda, and Occupied Melitopol Telecom

Querying stat.ripe.net/data/rpki-validation reveals that RIPE NCC's own cryptographic root authority (TA: RIPE NCC RPKI Root) actively signs valid RPKI ROA certificates for sanctioned Russian military and occupation infrastructure:

The complete bilingual compliance matrix of all 18 Russian VPK and Z-infrastructure clusters (32 RIPE org-ids, 35 ASNs, 117,024 IPv4 addresses valued at $2,219,956) and competent Dutch/EU enforcement channels (FIOD fiod.infodesk@belastingdienst.nl, Dutch Ministry of Finance sancties@minfin.nl, Ministry of Economic Affairs meldpuntsancties@minezk.nl, RDI info@rdi.nl, and European Commission DG FISMA) is published in /en/sanctions-gap#ripe-ipv4-matrix.

Profiled Targets
76
[RED: 54] · [BLUE: 22] · [NBU #65: 47]
ROC / FSB Network (EDR + FNS)
74 / 26
74 active UA EDRPOU · Rosatom · SBU
Certified Bots (UID)
1839
FB homoglyphs, 615-UIDs, YT ru-RU
RU Defense Plants (VPK)
202
9 weapon chains · 369 execs unsanctioned
Investigations
37
PsyOps & network forensics
Matrix Nodes / Edges
201 / 151
Botfarm amplification & RU state media