M-Telecom Ltd.
Data as of 2026-08-16
BGP inherited
Cluster stats
| Netblocks | 10 · 1,034 IPv4 addresses |
| IPv6 | 2 prefixes (largest 2001:7f8:f2:e1:a5:21:4172:1/128) |
| Registered in | Russia (5) · China (2) · Germany (2) |
| Cluster ID | 222462204 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 12 shared RIR contact/maintainer handles |
| Registry names | 4 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
Footprint over time
8 weekly snapshots · JSON
11
0 netblocks since 2026-07-05
2026-07-05
peak 11
2026-08-16
IP Ranges (10)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 91.210.200.0/22 | M-Telecom Ltd. | BGP | ANNOUNCED | ● high |
| 91.210.200.0/24 | M-Telecom Ltd. | BGP | ANNOUNCED | ● high |
| 91.210.201.0/24 | M-Telecom Ltd. | BGP | ANNOUNCED | ● high |
| 91.210.203.0/24 | M-Telecom Ltd. | BGP | ANNOUNCED | ● high |
| 122.227.82.80/30 | M-TELECOM | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 122.227.82.100/30 | M-TELECOM | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 185.1.155.208/32 | M-TELECOM | PEERINGDB | ASSIGNED | ● high |
| 185.1.166.31/32 | M-TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:f2:e1:a5:21:4172:1/128 | M-TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2a0c:b641:701:0:a5:21:4172:1/128 | M-TELECOM | PEERINGDB | ASSIGNED | ● high |
IPv6 ranges (2)
Network trust
what's this?
RPKI hygiene: D
how networks compare →
45.5%
of checked blocks have valid RPKI ROA coverage
(5 of 11)
No discrepancies found among checked blocks.
NIC Handles
AC1602-AP
AS214172
AS48369
CQ11-AP
DUMY-RIPE
DUMY-RIPE
M-TELECOM-MNT
MAINT-CN-CHINANET-ZJ-QZ
MX913-AP
MX914-AP
ORG-ML587-RIPE
RIPE-NCC-END-MNT