NALOG

BGP inherited
Cluster stats
Netblocks7 · 569 IPv4 addresses
All fragments 14 blocks across 6 clusters
Cluster ID208928760
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-19

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
82.208.81.0/24 NALOG-NET RIPE ASSIGNED PA ● low
82.208.93.160/27 NALOG-NET RIPE ASSIGNED PA ● low
84.53.197.224/29 NALOG RIPE ASSIGNED PA ● low
84.53.197.232/29 NALOG RIPE ASSIGNED PA ● low
84.53.197.248/29 NALOG RIPE ASSIGNED PA ● low
84.53.210.136/29 NALOG RIPE ASSIGNED PA ● low
213.177.111.0/24 NALOG-NET RIPE ASSIGNED PA ● low

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (7 of 7)
Possible discrepancies (2)

These blocks are registered to NALOG 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.177.111.0/24 /24 authorized for AS12389 — PJSC Rostelecom
82.208.81.0/24 /24 authorized for AS12389 — PJSC Rostelecom

NIC Handles

DUMY-RIPE DUMY-RIPE ROSTELECOM-MNT