DDG-2

BGP inherited
Cluster stats
Netblocks9
All fragments 10 blocks across 2 clusters
Cluster ID209559024
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
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-07-19

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
46.61.138.16/28 DDG-2 RIPE ASSIGNED PA ● low
46.61.138.64/28 DDG-2 RIPE ASSIGNED PA ● low
46.61.138.152/29 DDG-2 RIPE ASSIGNED PA ● low
95.167.2.28/30 DDG-2 RIPE ASSIGNED PA ● low
95.167.2.32/30 DDG-2 RIPE ASSIGNED PA ● low
95.167.2.188/30 DDG-2 RIPE ASSIGNED PA ● low
95.167.2.192/30 DDG-2 RIPE ASSIGNED PA ● low
95.167.9.24/29 DDG-2 RIPE ASSIGNED PA ● low
188.128.96.176/30 DDG-2 RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “DDG 2” — 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.

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (9 of 9)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE ROSTELECOM-MNT