Condor

CONDOR
Registry
Cluster stats
Netblocks6
Registered in Belgium (1) · Germany (1) · United Kingdom (1) · Italy (1) · Netherlands (1) · Russia (1)
All fragments 42 blocks across 16 clusters
Cluster ID208886064
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 8 shared RIR contact/maintainer handles
Registry names 5 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-19

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.5.163.176/28 CONDOR RIPE ASSIGNED PA ● low
82.118.94.240/28 CONDOR RIPE ASSIGNED PA ● low
82.204.9.104/30 Condor-BV RIPE ASSIGNED PA ● low
156.54.52.141/32 CONDOR-SRL RIPE LEGACY ● low
195.144.70.48/29 Condor RIPE ASSIGNED PA ● low
212.144.84.176/28 CONDOR-NET RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “CONDOR” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.
Combined view of all 16 name-family clusters →
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

Network trust

what's this?
RPKI hygiene: C how networks compare →
50.0% of checked blocks have valid RPKI ROA coverage (3 of 6)
No discrepancies found among checked blocks.

NIC Handles

ARCOR-MNT CWAL-MNT DUMY-RIPE DUMY-RIPE EVONET-MNT FULCOM-MNT-RIPE MTU-NOC NL-BBNET-MNT