Data as of Nov 16, 2026
95.64.128.0/18
87 residential-proxy exits · 30 daysMTS PJSC
Residential-proxy exits
Proxy exits
87
0.53% of its addresses · 30 days
Always-on exits
7
8.0% of its exits
Spread
48 of 64
/24s with at least one exit
Providers
113
selling exits here
Oct 17, 2026 – Nov 15, 2026
Exits seen per day
9.8K observations
/24s with the most always-on exits
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 911Proxy
- 9HTTP
- 9Proxy
- AETHYN_ELITE
- APROXY
- ASHBURNPROXIES
- Ake.net
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BottingTools
- BuyingProxy
- ByteProxies
- Byteful
- CROXY
- CatProxies
- CliProxy
- CoreProxy
- DataImpulse
- Datarama
- Decodo
- EVOPROXY
- EZProxies
- EnigmaProxy
- Evomi
- FLAMEPROXIES_BASIC
- FastProxy
- FlashProxy
- FlexyProxies
- FloppyData
- GEEKPROXY_TURBO
- GSocks
- GeekProxy
- Geonix
- Geonode
- GhostConnect
- GonzoProxy
- HPROXY
- HideProxy
- IPFly
- IPMUSK
- IPOasis
- IPPeak
- IPROCKET_PREMIUM
- IPRoyal
- Infatica
- InfiniteProxies
- Kookey
- LUMIPROXY
- LemonLabs
- LemonPrime
- LightningProxies
- LudaxProxy
- MangoProxy
- MarsProxies
- MoMoProxy
- NSocks
- NextProxy
- NiuProxy
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- PROXYON
- PROXYSALE
- PROXYSCRAPE
- PROXY_CC
- PSBProxy
- PrivateProxy
- Proxies.fo
- ProxiesVision
- Proxio
- Proxiware
- Proxy-Cheap
- Proxy-Seller
- Proxy302
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- ProxyStyler
- ProxyWing
- Proxyma
- PuraRoute
- Q2IP
- RH7Proxy
- RainProxy
- RapidProxy
- RealProxy
- ResiProxies
- RoamProxy
- SOTAPROXY
- SPYDERPROXY_BASIC
- Shifter
- Smartproxy
- SpyderProxy
- StrikeProxy
- SwiftProxy
- Thordata
- ThunderProxy
- TrustProxy
- VProxy
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
- ZENPROXY_PREMIUM
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 | abuse@ |
| └ 95.64.128.0/18 | 16,384 | mksbalashihi | PJSC MTS | SUB-ALLOCATED PA | Oct 4, 2021 | abuse@ via RU-MTU-20090424 |
| └ 95.64.128.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Nov 8, 2021 | abuse@ via mksbalashihi |
| └ 95.64.129.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Nov 8, 2021 | abuse@ via mksbalashihi |
| └ 95.64.130.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Nov 8, 2021 | abuse@ via mksbalashihi |
| └ 95.64.131.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Nov 8, 2021 | abuse@ via mksbalashihi |
| └ 95.64.132.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Nov 8, 2021 | abuse@ via mksbalashihi |
| └ 95.64.133.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Nov 8, 2021 | abuse@ via mksbalashihi |
| └ 95.64.134.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Nov 8, 2021 | abuse@ via mksbalashihi |
| └ 95.64.135.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Nov 8, 2021 | abuse@ via mksbalashihi |
| └ 95.64.136.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Nov 8, 2021 | abuse@ via mksbalashihi |
| └ 95.64.137.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Nov 8, 2021 | abuse@ via mksbalashihi |
| └ 95.64.138.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Dec 9, 2021 | abuse@ via mksbalashihi |
| └ 95.64.139.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Dec 9, 2021 | abuse@ via mksbalashihi |
| └ 95.64.140.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Dec 9, 2021 | abuse@ via mksbalashihi |
| └ 95.64.141.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Dec 9, 2021 | abuse@ via mksbalashihi |
| └ 95.64.142.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Dec 9, 2021 | abuse@ via mksbalashihi |
| └ 95.64.143.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Dec 9, 2021 | abuse@ via mksbalashihi |
| └ 95.64.144.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Jan 14, 2022 | abuse@ via mksbalashihi |
| └ 95.64.145.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Jan 14, 2022 | abuse@ via mksbalashihi |
| └ 95.64.146.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Jan 14, 2022 | abuse@ via mksbalashihi |
| └ 95.64.147.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Jan 14, 2022 | abuse@ via mksbalashihi |
| └ 95.64.148.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Jan 14, 2022 | abuse@ via mksbalashihi |
| └ 95.64.149.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Jan 14, 2022 | abuse@ via mksbalashihi |
| └ 95.64.150.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Jan 14, 2022 | abuse@ via mksbalashihi |
| └ 95.64.151.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Jan 14, 2022 | abuse@ via mksbalashihi |
| └ 95.64.152.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Mar 14, 2022 | abuse@ via mksbalashihi |
| └ 95.64.153.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Mar 14, 2022 | abuse@ via mksbalashihi |
| └ 95.64.154.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Mar 14, 2022 | abuse@ via mksbalashihi |
| └ 95.64.155.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Mar 14, 2022 | abuse@ via mksbalashihi |
| └ 95.64.156.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Mar 14, 2022 | abuse@ via mksbalashihi |
| └ 95.64.157.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Mar 14, 2022 | abuse@ via mksbalashihi |
| └ 95.64.158.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Mar 14, 2022 | abuse@ via mksbalashihi |
| └ 95.64.159.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Mar 14, 2022 | abuse@ via mksbalashihi |
| └ 95.64.160.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Mar 14, 2022 | abuse@ via mksbalashihi |
| └ 95.64.161.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Mar 14, 2022 | abuse@ via mksbalashihi |
| └ 95.64.162.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | May 5, 2022 | abuse@ via mksbalashihi |
| └ 95.64.163.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | May 5, 2022 | abuse@ via mksbalashihi |
| └ 95.64.164.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | May 5, 2022 | abuse@ via mksbalashihi |
| └ 95.64.165.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | May 5, 2022 | abuse@ via mksbalashihi |
| └ 95.64.166.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | May 5, 2022 | abuse@ via mksbalashihi |
| └ 95.64.167.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | May 5, 2022 | abuse@ via mksbalashihi |
| └ 95.64.168.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | May 5, 2022 | abuse@ via mksbalashihi |
| └ 95.64.169.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | May 5, 2022 | abuse@ via mksbalashihi |
| └ 95.64.170.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | May 5, 2022 | abuse@ via mksbalashihi |
| └ 95.64.171.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | May 5, 2022 | abuse@ via mksbalashihi |
| └ 95.64.172.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | May 5, 2022 | abuse@ via mksbalashihi |
| └ 95.64.173.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Jun 20, 2022 | abuse@ via mksbalashihi |
| └ 95.64.174.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Jun 20, 2022 | abuse@ via mksbalashihi |
| └ 95.64.175.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Jun 20, 2022 | abuse@ via mksbalashihi |
| └ 95.64.176.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Jun 20, 2022 | abuse@ via mksbalashihi |
| └ 95.64.177.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Jun 20, 2022 | abuse@ via mksbalashihi |
| └ 95.64.178.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Jun 20, 2022 | abuse@ via mksbalashihi |
| └ 95.64.179.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Jun 20, 2022 | abuse@ via mksbalashihi |
| └ 95.64.180.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Jun 20, 2022 | abuse@ via mksbalashihi |
| └ 95.64.181.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Jun 20, 2022 | abuse@ via mksbalashihi |
| └ 95.64.182.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Aug 8, 2022 | abuse@ via mksbalashihi |
| └ 95.64.183.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Aug 8, 2022 | abuse@ via mksbalashihi |
| └ 95.64.184.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Aug 8, 2022 | abuse@ via mksbalashihi |
| └ 95.64.185.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Aug 8, 2022 | abuse@ via mksbalashihi |
| └ 95.64.186.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Aug 8, 2022 | abuse@ via mksbalashihi |
| └ 95.64.187.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Aug 8, 2022 | abuse@ via mksbalashihi |
| └ 95.64.188.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Aug 8, 2022 | abuse@ via mksbalashihi |
| └ 95.64.189.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Aug 8, 2022 | abuse@ via mksbalashihi |
| └ 95.64.190.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Aug 8, 2022 | abuse@ via mksbalashihi |
| └ 95.64.191.0/24 | 256 | Customers_ | MTS PJSC | ASSIGNED PA | Aug 8, 2022 | abuse@ 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
- 153
- Always-on exits
- 10
- 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
- abuse@
mtu. ru - Name
- MTU Abuse-c Bender
- Handle
- MAB8359-RIPE