Data as of Nov 3, 2026
95.64.128.0/18
108 residential-proxy exits · 30 daysMTS PJSC
Residential-proxy exits
Proxy exits
108
0.66% of its addresses · 30 days
Always-on exits
6
5.6% of its exits
Spread
51 of 64
/24s with at least one exit
Providers
88
selling exits here
Oct 4, 2026 – Nov 2, 2026
Exits seen per day
6.5K observations
/24s with the most always-on exits
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 9Proxy
- Ake.net
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BottingTools
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- CoreProxy
- DataImpulse
- Datarama
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FastProxy
- FlashProxy
- FlexyProxies
- FloppyData
- GSocks
- GeekProxy
- Geonix
- Geonode
- GhostConnect
- GonzoProxy
- HideProxy
- IPFly
- IPOasis
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- Kookey
- LemonLabs
- LudaxProxy
- MangoProxy
- MarsProxies
- MoMoProxy
- NSocks
- NextProxy
- NiuProxy
- NodeProxy
- NovaProxy
- Novada
- Oxylabs
- PSBProxy
- PrivateProxy
- Proxies.fo
- ProxiesVision
- Proxio
- Proxiware
- Proxy-Cheap
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyRack
- ProxyStyler
- ProxyWing
- Proxying
- Proxyma
- PuraRoute
- RainProxy
- RealProxy
- ResiProxies
- RoamProxy
- RolaProxy
- Shifter
- Smartproxy
- SpyderProxy
- StrikeProxy
- SwiftProxy
- Thordata
- ThunderProxy
- TrustProxy
- VProxy
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
- YumiProxy
Registrations in this block
The registry's network records over this block, widest first, each under its parent.
| Range | Addresses | Netname | Holder | Type | Created | Abuse contact |
|---|---|---|---|---|---|---|
| 95.64.128.0/17 | 32,768 | RU-MTU-20090424 | MTS PJSC (ORG-ZM1-RIPE) · RU | ALLOCATED PA | Sep 3, 2021 | [email protected] |
| └ 95.64.128.0/18 | 16,384 | mksbalashihi | PJSC MTS | SUB-ALLOCATED PA | Oct 4, 2021 | [email protected] via RU-MTU-20090424 |
| └ 95.64.128.0/24 | 256 | Customers_P2P_2021_61_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 8, 2021 | [email protected] via mksbalashihi |
| └ 95.64.129.0/24 | 256 | Customers_P2P_2021_62_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 8, 2021 | [email protected] via mksbalashihi |
| └ 95.64.130.0/24 | 256 | Customers_P2P_2021_63_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 8, 2021 | [email protected] via mksbalashihi |
| └ 95.64.131.0/24 | 256 | Customers_P2P_2021_64_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 8, 2021 | [email protected] via mksbalashihi |
| └ 95.64.132.0/24 | 256 | Customers_P2P_2021_65_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 8, 2021 | [email protected] via mksbalashihi |
| └ 95.64.133.0/24 | 256 | Customers_P2P_2021_66_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 8, 2021 | [email protected] via mksbalashihi |
| └ 95.64.134.0/24 | 256 | Customers_P2P_2021_67_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 8, 2021 | [email protected] via mksbalashihi |
| └ 95.64.135.0/24 | 256 | Customers_P2P_2021_68_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 8, 2021 | [email protected] via mksbalashihi |
| └ 95.64.136.0/24 | 256 | Customers_P2P_2021_69_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 8, 2021 | [email protected] via mksbalashihi |
| └ 95.64.137.0/24 | 256 | Customers_P2P_2021_70_WAN_NET | MTS PJSC | ASSIGNED PA | Nov 8, 2021 | [email protected] via mksbalashihi |
| └ 95.64.138.0/24 | 256 | Customers_P2P_2021_71_WAN_NET | MTS PJSC | ASSIGNED PA | Dec 9, 2021 | [email protected] via mksbalashihi |
| └ 95.64.139.0/24 | 256 | Customers_P2P_2021_72_WAN_NET | MTS PJSC | ASSIGNED PA | Dec 9, 2021 | [email protected] via mksbalashihi |
| └ 95.64.140.0/24 | 256 | Customers_P2P_2021_73_WAN_NET | MTS PJSC | ASSIGNED PA | Dec 9, 2021 | [email protected] via mksbalashihi |
| └ 95.64.141.0/24 | 256 | Customers_P2P_2021_74_WAN_NET | MTS PJSC | ASSIGNED PA | Dec 9, 2021 | [email protected] via mksbalashihi |
| └ 95.64.142.0/24 | 256 | Customers_P2P_2021_75_WAN_NET | MTS PJSC | ASSIGNED PA | Dec 9, 2021 | [email protected] via mksbalashihi |
| └ 95.64.143.0/24 | 256 | Customers_P2P_2021_76_WAN_NET | MTS PJSC | ASSIGNED PA | Dec 9, 2021 | [email protected] via mksbalashihi |
| └ 95.64.144.0/24 | 256 | Customers_P2P_2022_00_WAN_NET | MTS PJSC | ASSIGNED PA | Jan 14, 2022 | [email protected] via mksbalashihi |
| └ 95.64.145.0/24 | 256 | Customers_P2P_2022_01_WAN_NET | MTS PJSC | ASSIGNED PA | Jan 14, 2022 | [email protected] via mksbalashihi |
| └ 95.64.146.0/24 | 256 | Customers_P2P_2022_02_WAN_NET | MTS PJSC | ASSIGNED PA | Jan 14, 2022 | [email protected] via mksbalashihi |
| └ 95.64.147.0/24 | 256 | Customers_P2P_2022_03_WAN_NET | MTS PJSC | ASSIGNED PA | Jan 14, 2022 | [email protected] via mksbalashihi |
| └ 95.64.148.0/24 | 256 | Customers_P2P_2022_04_WAN_NET | MTS PJSC | ASSIGNED PA | Jan 14, 2022 | [email protected] via mksbalashihi |
| └ 95.64.149.0/24 | 256 | Customers_P2P_2022_05_WAN_NET | MTS PJSC | ASSIGNED PA | Jan 14, 2022 | [email protected] via mksbalashihi |
| └ 95.64.150.0/24 | 256 | Customers_P2P_2022_06_WAN_NET | MTS PJSC | ASSIGNED PA | Jan 14, 2022 | [email protected] via mksbalashihi |
| └ 95.64.151.0/24 | 256 | Customers_P2P_2022_07_WAN_NET | MTS PJSC | ASSIGNED PA | Jan 14, 2022 | [email protected] via mksbalashihi |
| └ 95.64.152.0/24 | 256 | Customers_P2P_2022_08_WAN_NET | MTS PJSC | ASSIGNED PA | Mar 14, 2022 | [email protected] via mksbalashihi |
| └ 95.64.153.0/24 | 256 | Customers_P2P_2022_09_WAN_NET | MTS PJSC | ASSIGNED PA | Mar 14, 2022 | [email protected] via mksbalashihi |
| └ 95.64.154.0/24 | 256 | Customers_P2P_2022_10_WAN_NET | MTS PJSC | ASSIGNED PA | Mar 14, 2022 | [email protected] via mksbalashihi |
| └ 95.64.155.0/24 | 256 | Customers_P2P_2022_11_WAN_NET | MTS PJSC | ASSIGNED PA | Mar 14, 2022 | [email protected] via mksbalashihi |
| └ 95.64.156.0/24 | 256 | Customers_P2P_2022_12_WAN_NET | MTS PJSC | ASSIGNED PA | Mar 14, 2022 | [email protected] via mksbalashihi |
| └ 95.64.157.0/24 | 256 | Customers_P2P_2022_13_WAN_NET | MTS PJSC | ASSIGNED PA | Mar 14, 2022 | [email protected] via mksbalashihi |
| └ 95.64.158.0/24 | 256 | Customers_P2P_2022_14_WAN_NET | MTS PJSC | ASSIGNED PA | Mar 14, 2022 | [email protected] via mksbalashihi |
| └ 95.64.159.0/24 | 256 | Customers_P2P_2022_15_WAN_NET | MTS PJSC | ASSIGNED PA | Mar 14, 2022 | [email protected] via mksbalashihi |
| └ 95.64.160.0/24 | 256 | Customers_P2P_2022_16_WAN_NET | MTS PJSC | ASSIGNED PA | Mar 14, 2022 | [email protected] via mksbalashihi |
| └ 95.64.161.0/24 | 256 | Customers_P2P_2022_17_WAN_NET | MTS PJSC | ASSIGNED PA | Mar 14, 2022 | [email protected] via mksbalashihi |
| └ 95.64.162.0/24 | 256 | Customers_P2P_2022_18_WAN_NET | MTS PJSC | ASSIGNED PA | May 5, 2022 | [email protected] via mksbalashihi |
| └ 95.64.163.0/24 | 256 | Customers_P2P_2022_19_WAN_NET | MTS PJSC | ASSIGNED PA | May 5, 2022 | [email protected] via mksbalashihi |
| └ 95.64.164.0/24 | 256 | Customers_P2P_2022_20_WAN_NET | MTS PJSC | ASSIGNED PA | May 5, 2022 | [email protected] via mksbalashihi |
| └ 95.64.165.0/24 | 256 | Customers_P2P_2022_21_WAN_NET | MTS PJSC | ASSIGNED PA | May 5, 2022 | [email protected] via mksbalashihi |
| └ 95.64.166.0/24 | 256 | Customers_P2P_2022_22_WAN_NET | MTS PJSC | ASSIGNED PA | May 5, 2022 | [email protected] via mksbalashihi |
| └ 95.64.167.0/24 | 256 | Customers_P2P_2022_23_WAN_NET | MTS PJSC | ASSIGNED PA | May 5, 2022 | [email protected] via mksbalashihi |
| └ 95.64.168.0/24 | 256 | Customers_P2P_2022_24_WAN_NET | MTS PJSC | ASSIGNED PA | May 5, 2022 | [email protected] via mksbalashihi |
| └ 95.64.169.0/24 | 256 | Customers_P2P_2022_25_WAN_NET | MTS PJSC | ASSIGNED PA | May 5, 2022 | [email protected] via mksbalashihi |
| └ 95.64.170.0/24 | 256 | Customers_P2P_2022_26_WAN_NET | MTS PJSC | ASSIGNED PA | May 5, 2022 | [email protected] via mksbalashihi |
| └ 95.64.171.0/24 | 256 | Customers_P2P_2022_27_WAN_NET | MTS PJSC | ASSIGNED PA | May 5, 2022 | [email protected] via mksbalashihi |
| └ 95.64.172.0/24 | 256 | Customers_P2P_2022_28_WAN_NET | MTS PJSC | ASSIGNED PA | May 5, 2022 | [email protected] via mksbalashihi |
| └ 95.64.173.0/24 | 256 | Customers_P2P_2022_29_WAN_NET | MTS PJSC | ASSIGNED PA | Jun 20, 2022 | [email protected] via mksbalashihi |
| └ 95.64.174.0/24 | 256 | Customers_P2P_2022_30_WAN_NET | MTS PJSC | ASSIGNED PA | Jun 20, 2022 | [email protected] via mksbalashihi |
| └ 95.64.175.0/24 | 256 | Customers_P2P_2022_31_WAN_NET | MTS PJSC | ASSIGNED PA | Jun 20, 2022 | [email protected] via mksbalashihi |
| └ 95.64.176.0/24 | 256 | Customers_P2P_2022_32_WAN_NET | MTS PJSC | ASSIGNED PA | Jun 20, 2022 | [email protected] via mksbalashihi |
| └ 95.64.177.0/24 | 256 | Customers_P2P_2022_33_WAN_NET | MTS PJSC | ASSIGNED PA | Jun 20, 2022 | [email protected] via mksbalashihi |
| └ 95.64.178.0/24 | 256 | Customers_P2P_2022_34_WAN_NET | MTS PJSC | ASSIGNED PA | Jun 20, 2022 | [email protected] via mksbalashihi |
| └ 95.64.179.0/24 | 256 | Customers_P2P_2022_35_WAN_NET | MTS PJSC | ASSIGNED PA | Jun 20, 2022 | [email protected] via mksbalashihi |
| └ 95.64.180.0/24 | 256 | Customers_P2P_2022_36_WAN_NET | MTS PJSC | ASSIGNED PA | Jun 20, 2022 | [email protected] via mksbalashihi |
| └ 95.64.181.0/24 | 256 | Customers_P2P_2022_37_WAN_NET | MTS PJSC | ASSIGNED PA | Jun 20, 2022 | [email protected] via mksbalashihi |
| └ 95.64.182.0/24 | 256 | Customers_P2P_2022_38_WAN_NET | MTS PJSC | ASSIGNED PA | Aug 8, 2022 | [email protected] via mksbalashihi |
| └ 95.64.183.0/24 | 256 | Customers_P2P_2022_39_WAN_NET | MTS PJSC | ASSIGNED PA | Aug 8, 2022 | [email protected] via mksbalashihi |
| └ 95.64.184.0/24 | 256 | Customers_P2P_2022_40_WAN_NET | MTS PJSC | ASSIGNED PA | Aug 8, 2022 | [email protected] via mksbalashihi |
| └ 95.64.185.0/24 | 256 | Customers_P2P_2022_41_WAN_NET | MTS PJSC | ASSIGNED PA | Aug 8, 2022 | [email protected] via mksbalashihi |
| └ 95.64.186.0/24 | 256 | Customers_P2P_2022_42_WAN_NET | MTS PJSC | ASSIGNED PA | Aug 8, 2022 | [email protected] via mksbalashihi |
| └ 95.64.187.0/24 | 256 | Customers_P2P_2022_43_WAN_NET | MTS PJSC | ASSIGNED PA | Aug 8, 2022 | [email protected] via mksbalashihi |
| └ 95.64.188.0/24 | 256 | Customers_P2P_2022_44_WAN_NET | MTS PJSC | ASSIGNED PA | Aug 8, 2022 | [email protected] via mksbalashihi |
| └ 95.64.189.0/24 | 256 | Customers_P2P_2022_45_WAN_NET | MTS PJSC | ASSIGNED PA | Aug 8, 2022 | [email protected] via mksbalashihi |
| └ 95.64.190.0/24 | 256 | Customers_P2P_2022_46_WAN_NET | MTS PJSC | ASSIGNED PA | Aug 8, 2022 | [email protected] via mksbalashihi |
| └ 95.64.191.0/24 | 256 | Customers_P2P_2022_47_WAN_NET | MTS PJSC | ASSIGNED PA | Aug 8, 2022 | [email protected] via mksbalashihi |
A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.
Network & registry
Announced by
Covering announcement 95.64.128.0/17
- Prefix
- 95.64.128.0/17
- Announced by
- AS8359 MTS PJSC
- Type
- Mobile
- Proxy exits
- 180
- Always-on exits
- 11
- RPKI
- No RPKI
- Netname
- RU-MTU-20090424
- Registrant
- MTS PJSC
- RIR
- RIPE NCC
Origin network
AS8359
RU
- Name
- MTS PJSC
- Type
- Internet provider
- Registered
- Jun 26, 1997
- Domain
- mts.ru
- Website
- ir.mts.ru/
- Industry
- Internet Service Provider (ISP)
- Spamhaus ASN-DROP
- not listed
Routing timeline
Who has announced 95.64.128.0/17
95.64.128.0/17
Routing history
- Pattern
- Stable
- First seen
- Jun 2009
- Current origin since
- Oct 2021 · 5.1 yr
- Origin networks
- 2
- Last change of origin
- Oct 2021
Recorded history
History
- Handoffs
- 1
Whois
Registration for this announcement
- Range
- 95.64.128.0/17
- Netname
- RU-MTU-20090424
- Registrant
- MTS PJSC
- Registrant country
- RU
- Organization
- MTS PJSC (ORG-ZM1-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Sep 3, 2021
- Updated
- Sep 3, 2021
- Maintainer
- MTU-NOC
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Apr 24, 2009
- Status
- assigned
Report abuse
Abuse contact
- [email protected]
- Name
- MTU Abuse-c Bender
- Handle
- MAB8359-RIPE