DEDIPOWER-DEDICATED-3A7C

BGP inherited
Cluster stats
Netblocks8
All fragments 851 blocks across 404 clusters
Cluster ID209198203
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

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

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
81.29.66.152/29 DEDIPOWER-DEDICATED-3A7C RIPE ASSIGNED PA ● low
89.151.73.0/26 DEDIPOWER-DEDICATED-3A7C RIPE ASSIGNED PA ● low
89.151.90.0/28 DEDIPOWER-DEDICATED-3A7C RIPE ASSIGNED PA ● low
89.151.108.16/29 DEDIPOWER-DEDICATED-3A7C RIPE ASSIGNED PA ● low
89.151.108.48/28 DEDIPOWER-DEDICATED-3A7C RIPE ASSIGNED PA ● low
89.151.108.96/29 DEDIPOWER-DEDICATED-3A7C RIPE ASSIGNED PA ● low
89.151.108.160/29 DEDIPOWER-DEDICATED-3A7C RIPE ASSIGNED PA ● low
89.151.115.64/28 DEDIPOWER-DEDICATED-3A7C RIPE ASSIGNED PA ● low

Possibly related to this organisation

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

NIC Handles

DEDIPOWER-MNT DUMY-RIPE DUMY-RIPE