DICO-NET

BGP inherited
Cluster stats
Netblocks6
All fragments 25 blocks across 11 clusters
Cluster ID210175183
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
92.79.60.168/29 DICO-NET RIPE ASSIGNED PA ● low
145.253.109.0/29 DICO-NET RIPE ASSIGNED PA ● low
145.253.109.8/29 DICO-NET RIPE ASSIGNED PA ● low
176.95.41.72/29 DICO-NET RIPE ASSIGNED PA ● low
176.95.52.88/29 DICO-NET RIPE ASSIGNED PA ● low
195.50.143.144/29 DICO-NET RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “DICO” — 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 11 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 (6 of 6)
No discrepancies found among checked blocks.

NIC Handles

ARCOR-MNT DUMY-RIPE DUMY-RIPE