CIREX

Data as of 2026-09-13
BGP inherited
This organisation
Netblocks4 · 776 IPv4 addresses
Also registered under this name 6 netblocks across 3 separate records
Record ID241139140
RegistryRIPE
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 6 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (4)

⬇ export CSV
CIDR Org name Registry Status Confidence
212.67.16.0/24 CIREX RIPE ASSIGNED PA ● high
212.67.18.0/24 CIREX RIPE ASSIGNED PA ● high
212.67.19.0/24 CIREX RIPE ASSIGNED PA ● high
81.12.213.8/29 cirex RIPE ASSIGNED PA ● low

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (4 of 4)
Possible discrepancies (3)

These blocks are registered to CIREX but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

212.67.16.0/24 /24 authorized for AS199599 — Telecom-Birzha, LLC
212.67.18.0/24 /24 authorized for AS199599 — Telecom-Birzha, LLC
212.67.19.0/24 /24 authorized for AS199599 — Telecom-Birzha, LLC

NIC Handles

AR16601-RIPE AS12302-MNT CIREX-MNT DUMY-RIPE DUMY-RIPE IPMAGNAT-MNT