EKO-INSTAL

BGP inherited
Cluster stats
Netblocks9
All fragments 12 blocks across 3 clusters
Cluster ID211078665
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
80.48.1.160/30 EKO-INSTAL RIPE ASSIGNED PA ● low
80.51.235.216/29 EKO-INSTAL RIPE ASSIGNED PA ● low
195.117.41.200/30 EKO-INSTAL RIPE ASSIGNED PA ● low
195.117.138.32/29 EKO-INSTAL RIPE ASSIGNED PA ● low
195.205.16.196/30 EKO-INSTAL RIPE ASSIGNED PA ● low
195.205.28.104/29 EKO-INSTAL RIPE ASSIGNED PA ● low
213.25.115.28/30 EKO-INSTAL RIPE ASSIGNED PA ● low
213.76.148.88/29 EKO-INSTAL RIPE ASSIGNED PA ● low
213.77.36.64/29 EKO-INSTAL RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “EKO INSTAL” — 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: 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 TPNET