Moscow Server Network
BGP inherited
Cluster stats
Netblocks7
All fragments 57 blocks across 33 clusters
Cluster ID192001125
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 11 shared RIR contact/maintainer handles
Registry names 6 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

2 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-06

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
31.77.232.0/24 Moscow Server Network RIPE SUB-ALLOCATED PA ● high
144.31.222.0/24 Moscow Server Network RIPE SUB-ALLOCATED PA ● high
13.143.134.0/24 ApexNodes RIPE LEGACY ● medium
82.198.190.144/29 Moscow-mfa-rs RIPE ASSIGNED PA ● low
89.207.41.0/24 MOSCOW-RATMIR4 RIPE ASSIGNED PA ● low
193.233.1.0/26 MOSCOW-BNS00-F0 RIPE ASSIGNED PA ● low
2a01:620:1:2000::/52 Moscow_IPv6 RIPE AGGREGATED-BY-LIR ● low

Network trust

what's this?
RPKI hygiene: C how networks compare →
71.4% of checked blocks have valid RPKI ROA coverage (5 of 7)
Possible discrepancies (4)

These blocks are registered to Moscow Server Network but cryptographically authorized for a different, unrelated network (2 distinct holders) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

2a01:620:1:2000::/52 /52 authorized for AS12389 — PJSC Rostelecom
144.31.222.0/24 /24 authorized for AS202831 — Ablaykhan Akylbekovich Sharimov
31.77.232.0/24 /24 authorized for AS202831 — Ablaykhan Akylbekovich Sharimov
13.143.134.0/24 /24 authorized for AS202831 — Ablaykhan Akylbekovich Sharimov

NIC Handles

AA41996-RIPE AS2895-MNT DUMY-RIPE DUMY-RIPE FREENET-MNT GLOBUS-MNT ORG-AA2942-RIPE ORG-MS900-RIPE RATMIR-NOC ROSTELECOM-MNT lir-us-acedatacenter-1-MNT