KNA-RU-MOSCOW

Data as of 2026-09-06
BGP inherited
This organisation
Netblocks8 · 856 IPv4 addresses
Also registered under this name 9 netblocks across 2 separate records
Record ID237998323
RegistryRIPE
Customerssee who runs inside 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 · report an issue

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
81.177.30.160/29 KNA-RU-MOSCOW RIPE ASSIGNED PA ● low
81.177.31.224/29 KNA-RU-MOSCOW RIPE ASSIGNED PA ● low
213.24.35.0/24 KNA-RU-MOSCOW RIPE ASSIGNED PA ● low
213.24.45.216/29 KNA-RU-MOSCOW RIPE ASSIGNED PA ● low
213.24.74.0/24 KNA-RU-MOSCOW RIPE ASSIGNED PA ● low
213.24.167.64/26 KNA-RU-MOSCOW RIPE ASSIGNED PA ● low
213.24.167.128/25 KNA-RU-MOSCOW RIPE ASSIGNED PA ● low
213.24.238.128/25 KNA-RU-MOSCOW RIPE ASSIGNED PA ● low

Footprint over time

11 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-09-06

Network trust

what's this?
RPKI hygiene: C how networks compare →
75.0% of checked blocks have valid RPKI ROA coverage (6 of 8)
Possible discrepancies (2)

These blocks are registered to KNA-RU-MOSCOW but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

213.24.35.0/24 /24 authorized for AS12389 — PJSC Rostelecom
213.24.74.0/24 /24 authorized for AS12389 — PJSC Rostelecom

NIC Handles

AS8342-MNT DUMY-RIPE DUMY-RIPE