ENKA

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

Footprint over time

3 weekly snapshots · JSON
7 +1 netblocks since 2026-07-12
2026-07-12 peak 7 2026-07-19

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
88.204.226.152/30 ENKA RIPE ASSIGNED PA ● low
88.204.227.136/30 ENKA RIPE ASSIGNED PA ● low
88.204.227.176/28 ENKA RIPE ASSIGNED PA ● low
89.21.130.56/29 Enka-NET RIPE ASSIGNED PA ● low
195.89.93.112/29 ENKA RIPE ASSIGNED PA ● low
195.89.129.148/30 ENKA RIPE ASSIGNED PA ● low
213.194.82.112/28 NET-ENKA RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “ENKA” — 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 →
85.7% of checked blocks have valid RPKI ROA coverage (6 of 7)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE KNIC-MNT MNT-BORUSAN MNT-TELECOM-TZ VODAFONE-WORLDWIDE-MNTNER