KEYNIT

BGP inherited
Cluster stats
Netblocks6
All fragments 15 blocks across 5 clusters
Cluster ID205275538
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

4 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-13

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
195.16.164.240/28 KEYNIT RIPE ASSIGNED PA ● low
212.73.199.128/28 KEYNIT RIPE ASSIGNED PA ● low
212.73.212.128/26 KEYNIT RIPE ASSIGNED PA ● low
212.73.212.192/26 KEYNIT RIPE ASSIGNED PA ● low
212.73.239.32/27 KEYNIT RIPE ASSIGNED PA ● low
212.73.246.224/27 KEYNIT RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “KEYNIT” — 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.
  • Bloc 1 via KEYNIT SAS sub-allocation
  • Bloc 2 via KEYNIT SAS sub-allocation

NIC Handles

DUMY-RIPE DUMY-RIPE LEVEL3-MNT QUZAUK