MMSCE-NET

BGP inherited
Cluster stats
Netblocks10 · 5,830 IPv4 addresses
Cluster ID209545666
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 5 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
10 0 netblocks since 2026-07-05
2026-07-05 peak 10 2026-07-19

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
46.235.216.0/22 MMSCE-NET RIPE ASSIGNED PA ● low
46.235.220.0/22 MMSCE-NET RIPE SUB-ALLOCATED PA ● low
77.73.136.0/22 MMSCE-NET RIPE ASSIGNED PA ● low
77.73.141.0/25 MMSCE-NET RIPE ASSIGNED PA ● low
77.73.141.160 – 77.73.141.255 MMSCE-NET RIPE ASSIGNED PA ● low
77.73.142.0/24 MMSCE-NET RIPE ASSIGNED PA ● low
77.73.143.16 – 77.73.143.255 MMSCE-NET RIPE ASSIGNED PA ● low
109.68.168.0/23 MMSCE-NET RIPE SUB-ALLOCATED PA ● low
109.68.170.0/23 MMSCE-NET RIPE SUB-ALLOCATED PA ● low
109.68.172.0/22 MMSCE-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 (10 of 10)
Possible discrepancies (7)

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

46.235.216.0/22 /22 authorized for AS12389 — PJSC Rostelecom
77.73.136.0/22 /22 authorized for AS12389 — PJSC Rostelecom
109.68.172.0/22 /22 authorized for AS12389 — PJSC Rostelecom
46.235.220.0/22 /22 authorized for AS12389 — PJSC Rostelecom
109.68.168.0/23 /23 authorized for AS12389 — PJSC Rostelecom
109.68.170.0/23 /23 authorized for AS12389 — PJSC Rostelecom
77.73.142.0/24 /24 authorized for AS12389 — PJSC Rostelecom

NIC Handles

AS8997-MNT DUMY-RIPE DUMY-RIPE M2C-MNT ROSTELECOM-MNT