KNA-RU-MOSCOW

BGP inherited

Cluster stats

Netblocks	8 · 848 IPv4 addresses
All fragments	9 blocks across 2 clusters
Cluster ID	209507743
Registry	RIPE
Customers	find 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

8 0 netblocks since 2026-07-05

2026-07-05 peak 8 2026-07-19

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

Possibly related to this organisation

what's this?

Same name family

Separately-registered clusters whose names share “KNA RU” — 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.

KNA-RU-STUPINO 1 blocks

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