Dinamo-NET

BGP inherited
Cluster stats
Netblocks10
Registered in Turkey (7) · KZ (2) · Russia (1)
All fragments 22 blocks across 9 clusters
Cluster ID209223945
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

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

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
31.169.93.32/27 Dinamo-NET RIPE ASSIGNED PA ● low
31.169.93.64/27 Dinamo-NET RIPE ASSIGNED PA ● low
31.169.93.96/27 Dinamo-NET RIPE ASSIGNED PA ● low
31.169.93.128/27 Dinamo-NET RIPE ASSIGNED PA ● low
31.169.93.160/27 Dinamo-NET RIPE ASSIGNED PA ● low
31.169.93.192/27 Dinamo-NET RIPE ASSIGNED PA ● low
31.169.93.224/27 Dinamo-NET RIPE ASSIGNED PA ● low
85.90.120.112/29 Dinamo-NET RIPE ASSIGNED PA ● low
88.204.150.248/30 DINAMO RIPE ASSIGNED PA ● low
89.106.237.108/30 DINAMO RIPE ASSIGNED PA ● low

Possibly related to this organisation

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

NIC Handles

DUMY-RIPE DUMY-RIPE KNIC-MNT MNT-TELECOM-TZ NETFACTOR-MNT