INSOSPA

BGP inherited
Cluster stats
Netblocks10
Cluster ID209047484
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
62.110.201.208/28 INSOSPA RIPE ASSIGNED PA ● low
82.190.206.0/29 INSOSPA RIPE ASSIGNED PA ● low
85.33.252.16/29 INSOSPA RIPE ASSIGNED PA ● low
88.35.148.88/29 INSOSPA RIPE ASSIGNED PA ● low
88.38.124.184/29 INSOSPA RIPE ASSIGNED PA ● low
88.44.196.56/29 INSOSPA RIPE ASSIGNED PA ● low
88.49.59.160/29 INSOSPA RIPE ASSIGNED PA ● low
88.58.107.112/29 INSOSPA RIPE ASSIGNED PA ● low
88.59.42.0/29 INSOSPA RIPE ASSIGNED PA ● low
94.92.189.40/29 INSOSPA 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