REK

BGP inherited
Cluster stats
Netblocks6
Registered in Russia (3) · KZ (1) · Netherlands (1)
All fragments 12 blocks across 7 clusters
Cluster ID209315564
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 7 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names 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
85.146.221.176/30 REK RIPE ASSIGNED PA ● low
88.204.242.128/29 REK RIPE ASSIGNED PA ● low
95.167.75.200/30 REK RIPE ASSIGNED PA ● low
109.161.57.240/29 REK RIPE ASSIGNED PA ● low
217.147.28.192/30 REK-NET RIPE ASSIGNED PA ● low
2a00:18c8:102e::/48 REK RIPE ASSIGNED ● low

Possibly related to this organisation

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

Network trust

what's this?
RPKI hygiene: B how networks compare →
83.3% of checked blocks have valid RPKI ROA coverage (5 of 6)
Possible discrepancies (1)

These blocks are registered to REK 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.

2a00:18c8:102e::/48 /48 authorized for AS33915 — Vodafone Libertel B.V.

NIC Handles

DUMY-RIPE DUMY-RIPE KNIC-MNT ROSTELECOM-MNT TEL-NET-MNT TNF-MNT YARTEL-MNT