CLNexus LTD

BGP inherited
Cluster stats
Netblocks9
Registered in AG (1) · United Kingdom (1)
All fragments 40 blocks across 32 clusters
Cluster ID208804611
RegistryPEERINGDB
Customersfind customers using 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

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
5.57.82.47/32 CLNexus PEERINGDB ASSIGNED ● high
178.18.237.34/32 CLNexus PEERINGDB ASSIGNED ● high
2001:504:125:e1::aafd/128 CLNexus PEERINGDB ASSIGNED ● high
2001:7f8:17::3:4594:1/128 CLNexus PEERINGDB ASSIGNED ● high
2001:7f8:ca:1:0:21:4420:1/128 CLNexus PEERINGDB ASSIGNED ● high
2a03:5f80:4:2::237:34/128 CLNexus PEERINGDB ASSIGNED ● high
2a06:9801:f1b::/48 CLNexus LTD RIPE ASSIGNED ● high
2a0e:8f01:1000:25::100/128 CLNexus PEERINGDB ASSIGNED ● high
2a14:7580:ec00::7/128 CLNexus PEERINGDB ASSIGNED ● high

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “CLNexus” — 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 32 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 →
55.6% of checked blocks have valid RPKI ROA coverage (5 of 9)
No discrepancies found among checked blocks.

NIC Handles

AS214420 DUMY-RIPE DUMY-RIPE LAGRANGE-AUTO-MNT LSRA2-RIPE ORG-CL852-RIPE