Mobile TeleSystems PJSC
Cluster stats
| Netblocks | 32 |
| All fragments | 267 blocks across 2 clusters |
| Cluster ID | 193381715 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 1 shared RIR contact/maintainer handle |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (32)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 80.81.192.78/32 | Mobile TeleSystems PJSC | PEERINGDB | ASSIGNED | ● high |
| 80.81.193.78/32 | Mobile TeleSystems PJSC | PEERINGDB | ASSIGNED | ● high |
| 80.249.209.188/32 | Mobile TeleSystems PJSC | PEERINGDB | ASSIGNED | ● high |
| 123.255.90.58/32 | Mobile TeleSystems PJSC | PEERINGDB | ASSIGNED | ● high |
| 193.110.226.66/32 | Mobile TeleSystems PJSC | PEERINGDB | ASSIGNED | ● high |
| 193.232.87.33/32 | Mobile TeleSystems PJSC | PEERINGDB | ASSIGNED | ● high |
| 193.232.140.40/32 | Mobile TeleSystems PJSC | PEERINGDB | ASSIGNED | ● high |
| 194.68.123.161/32 | Mobile TeleSystems PJSC | PEERINGDB | ASSIGNED | ● high |
| 194.68.128.161/32 | Mobile TeleSystems PJSC | PEERINGDB | ASSIGNED | ● high |
| 194.85.107.38/32 | Mobile TeleSystems PJSC | PEERINGDB | ASSIGNED | ● high |
| 195.66.224.218/32 | Mobile TeleSystems PJSC | PEERINGDB | ASSIGNED | ● high |
| 195.208.208.30/32 | Mobile TeleSystems PJSC | PEERINGDB | ASSIGNED | ● high |
| 198.32.118.80/32 | Mobile TeleSystems PJSC | PEERINGDB | ASSIGNED | ● high |
| 198.32.160.201/32 | Mobile TeleSystems PJSC | PEERINGDB | ASSIGNED | ● high |
| 206.82.104.18/32 | Mobile TeleSystems PJSC | PEERINGDB | ASSIGNED | ● high |
| 206.126.236.180/32 | Mobile TeleSystems PJSC | PEERINGDB | ASSIGNED | ● high |
| 2001:504:0:2::8359:1/128 | Mobile TeleSystems PJSC | PEERINGDB | ASSIGNED | ● high |
| 2001:504:1::a500:8359:1/128 | Mobile TeleSystems PJSC | PEERINGDB | ASSIGNED | ● high |
| 2001:504:f::50/128 | Mobile TeleSystems PJSC | PEERINGDB | ASSIGNED | ● high |
| 2001:504:36::20a7:0:1/128 | Mobile TeleSystems PJSC | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8::20a7:0:1/128 | Mobile TeleSystems PJSC | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8::20a7:0:2/128 | Mobile TeleSystems PJSC | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:1::a500:8359:1/128 | Mobile TeleSystems PJSC | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:4::20a7:1/128 | Mobile TeleSystems PJSC | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:7:a::8359:1/128 | Mobile TeleSystems PJSC | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:d:fe::161/128 | Mobile TeleSystems PJSC | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:d:ff::161/128 | Mobile TeleSystems PJSC | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:20:101::208:30/128 | Mobile TeleSystems PJSC | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:20:301::107:38/128 | Mobile TeleSystems PJSC | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:20:401::87:33/128 | Mobile TeleSystems PJSC | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:20:501::140:40/128 | Mobile TeleSystems PJSC | PEERINGDB | ASSIGNED | ● high |
| 2001:7fa:0:1::ca28:a03a/128 | Mobile TeleSystems PJSC | PEERINGDB | ASSIGNED | ● high |
Network trust
what's this?
RPKI hygiene: B
how networks compare →
81.2%
of checked blocks have valid RPKI ROA coverage
(26 of 32)
No discrepancies found among checked blocks.
NIC Handles
AS8359