PROGETTOSPA

BGP inherited
Cluster stats
Netblocks10
Cluster ID208820936
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
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
80.16.120.216/29 PROGETTOSPA RIPE ASSIGNED PA ● low
80.16.122.68/30 PROGETTOSPA RIPE ASSIGNED PA ● low
80.18.158.192/28 PROGETTOSPA RIPE ASSIGNED PA ● low
80.18.167.240/29 PROGETTOSPA RIPE ASSIGNED PA ● low
80.22.162.40/29 PROGETTOSPA RIPE ASSIGNED PA ● low
85.32.175.160/29 PROGETTOSPA RIPE ASSIGNED PA ● low
85.32.175.176/29 PROGETTOSPA RIPE ASSIGNED PA ● low
85.32.243.216/29 PROGETTOSPA RIPE ASSIGNED PA ● low
88.34.159.40/29 PROGETTOSPA RIPE ASSIGNED PA ● low
217.141.101.52/30 PROGETTOSPA RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
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.

NIC Handles

DUMY-RIPE DUMY-RIPE INTERB-MNT