Moscow Server Network

Data as of 2026-07-26

BGP inherited

Cluster stats

Netblocks	6 · 1,088 IPv4 addresses
IPv6	1 prefix (largest 2a01:620:1:2000::/52)
Registered in	United States (3) · Russia (2)
Cluster ID	213245345
Registry	RIPE
Customers	find customers using this network →

Evidence & provenance ?

Attribution	BGP parent (inherited)
Shared handles	clustered on 10 shared RIR contact/maintainer handles
Registry names	5 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

Footprint over time

6 weekly snapshots · JSON

6 -1 netblocks since 2026-07-05

2026-07-05 peak 7 2026-07-26

IP Ranges (6)

⬇ 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
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

IPv6 ranges (1)

CIDR
2a01:620:1:2000::/52

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 (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 ORG-AA2942-RIPE ORG-MS900-RIPE RATMIR-NOC ROSTELECOM-MNT lir-us-acedatacenter-1-MNT