Mobile TeleSystems JLLC
MTSBY
Cluster stats
| Netblocks | 25 |
| Cluster ID | 193414870 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 3 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (25)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 46.56.0.0/19 | MTSBY | RIPE | ASSIGNED PA | ● low |
| 46.56.32.0/19 | MTSBY | RIPE | ASSIGNED PA | ● low |
| 46.56.64.0/19 | MTSBY | RIPE | ASSIGNED PA | ● low |
| 46.56.96.0/19 | MTSBY | RIPE | ASSIGNED PA | ● low |
| 46.216.0.0/17 | MTSBY | RIPE | ASSIGNED PA | ● low |
| 46.216.128.0/17 | MTSBY | RIPE | ASSIGNED PA | ● low |
| 134.17.0.0/20 | MTSBY | RIPE | ASSIGNED PA | ● low |
| 134.17.16.0/20 | MTSBY | RIPE | ASSIGNED PA | ● low |
| 134.17.32.0/19 | MTSBY | RIPE | ASSIGNED PA | ● low |
| 134.17.64.0/20 | MTSBY | RIPE | ASSIGNED PA | ● low |
| 134.17.80.0/21 | MTSBY | RIPE | ASSIGNED PA | ● low |
| 134.17.88.0/21 | MTSBY | RIPE | ASSIGNED PA | ● low |
| 134.17.96.0/19 | MTSBY | RIPE | ASSIGNED PA | ● low |
| 134.17.128.0/19 | MTSBY | RIPE | ASSIGNED PA | ● low |
| 134.17.160.0/19 | MTSBY | RIPE | ASSIGNED PA | ● low |
| 134.17.192.0/19 | MTSBY | RIPE | ASSIGNED PA | ● low |
| 134.17.224.0/19 | MTSBY | RIPE | ASSIGNED PA | ● low |
| 176.60.0.0/18 | MTSBY | RIPE | ASSIGNED PA | ● low |
| 176.60.64.0/18 | MTSBY | RIPE | ASSIGNED PA | ● low |
| 176.60.128.0/18 | MTSBY | RIPE | ASSIGNED PA | ● low |
| 176.60.192.0/18 | MTSBY | RIPE | ASSIGNED PA | ● low |
| 178.168.128.0/18 | MTSBY | RIPE | ASSIGNED PA | ● low |
| 178.168.192.0/18 | MTSBY | RIPE | ASSIGNED PA | ● low |
| 185.20.112.0/23 | MTSBY | RIPE | ASSIGNED PA | ● low |
| 185.20.114.0/23 | MTSBY | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
72.0%
of checked blocks have valid RPKI ROA coverage
(18 of 25)
RPKI-inferred operator
Mobile TeleSystems JLLC
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
MTSBY-MNT