CUSTDC_CLIENT_ID_1814

BGP inherited
Cluster stats
Netblocks6
All fragments 7 blocks across 2 clusters
Cluster ID204832475
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

3 weekly snapshots · JSON
6 0 netblocks since 2026-07-12
2026-07-12 peak 6 2026-07-19

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
5.102.173.32/27 CUSTDC_CLIENT_ID_1814 RIPE ASSIGNED PA ● low
5.102.173.112/28 CUSTDC_CLIENT_ID_1814 RIPE ASSIGNED PA ● low
109.74.246.160/27 CUSTDC_CLIENT_ID_1814 RIPE ASSIGNED PA ● low
109.74.249.32/29 CUSTDC_CLIENT_ID_1814 RIPE ASSIGNED PA ● low
109.74.249.168/29 CUSTDC_CLIENT_ID_1814 RIPE ASSIGNED PA ● low
109.74.249.184/29 CUSTDC_CLIENT_ID_1814 RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “CUSTDC CLIENT ID” — 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.
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: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (6 of 6)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE MNT-CUSTODIAN