MCM

BGP inherited
Cluster stats
Netblocks7 · 354 IPv4 addresses
Registered in Belgium (1) · Switzerland (1) · India (1) · MT (1) · Netherlands (1) · Russia (1)
All fragments 42 blocks across 21 clusters
Cluster ID208831876
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 14 shared RIR contact/maintainer handles
Registry names 4 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
210.212.147.136/29 MCM APNIC ASSIGNED NON-PORTABLE ● high
62.5.187.0/26 MCM RIPE ASSIGNED PA ● low
194.7.183.160/28 MCM-NET RIPE ASSIGNED PA ● low
194.158.41.176/29 mcm RIPE ASSIGNED PA ● low
195.15.2.72/29 MCM-NET RIPE ASSIGNED PA ● low
195.108.209.0/24 MCM RIPE ASSIGNED PA ● low
2a00:2381:9b::/48 MCM RIPE AGGREGATED-BY-LIR ● low

Network trust

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

These blocks are registered to MCM 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:2381:9b::/48 /48 authorized for AS2856 — British Telecommunications Limited

NIC Handles

AB1061-AP AS2822-MNT BTNET-MNT CDN1-AP DUMY-RIPE DUMY-RIPE GO-MNTNR MAINT-IN-DOT MTU-NOC NC83-AP NLNET-MNT PM550-AP +2 more