Data as of Nov 3, 2026
95.64.192.0/19
54 residential-proxy exits · 30 daysMTS PJSC
Residential-proxy exits
Proxy exits
54
0.66% of its addresses · 30 days
Always-on exits
5
9.3% of its exits
Spread
26 of 32
/24s with at least one exit
Providers
81
selling exits here
Oct 4, 2026 – Nov 2, 2026
Exits seen per day
12K observations
/24s with the most always-on exits
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 9Proxy
- Ake.net
- AnyIP
- B2Proxy
- BestProxy
- BirdProxies
- BottingTools
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CoreProxy
- DataImpulse
- Datarama
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FastProxy
- FlashProxy
- FloppyData
- GeekProxy
- Geonode
- GhostConnect
- GloryCloud
- HideProxy
- IPFly
- IPOasis
- IPPeak
- IPRoyal
- InfiniteProxies
- KindProxy
- Kookey
- LudaxProxy
- MarsProxies
- Maskify
- MoMoProxy
- NSocks
- NextProxy
- NiuProxy
- NodeMaven
- NovaProxy
- Novada
- Oxylabs
- PSBProxy
- PrivateProxy
- Proxies.fo
- ProxiesVision
- Proxio
- Proxiware
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyRack
- ProxyStyler
- ProxyWing
- Proxying
- PuraRoute
- RainProxy
- RapidProxy
- RealProxy
- ResiProxies
- RoamProxy
- RolaProxy
- Shifter
- Smartproxy
- SpyderProxy
- StrikeProxy
- SwiftProxy
- TalorData
- Thordata
- ThunderProxy
- TrueProxies
- TrustProxy
- VProxy
- VantageProxies
- VibeProxies
- VitalExclusive
- Webshare
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.192.0/19 | 8,192 | mksbalashihi | MTS PJSC | SUB-ALLOCATED PA | Sep 26, 2022 | [email protected] via RU-MTU-20090424 |
| └ 95.64.192.0/24 | 256 | Customers_P2P_2022_48_WAN_NET | MTS PJSC | ASSIGNED PA | Sep 26, 2022 | [email protected] via mksbalashihi |
| └ 95.64.193.0/24 | 256 | Customers_P2P_2022_49_WAN_NET | MTS PJSC | ASSIGNED PA | Sep 26, 2022 | [email protected] via mksbalashihi |
| └ 95.64.194.0/24 | 256 | Customers_P2P_2022_50_WAN_NET | MTS PJSC | ASSIGNED PA | Sep 26, 2022 | [email protected] via mksbalashihi |
| └ 95.64.195.0/24 | 256 | Customers_P2P_2022_51_WAN_NET | MTS PJSC | ASSIGNED PA | Sep 26, 2022 | [email protected] via mksbalashihi |
| └ 95.64.196.0/24 | 256 | Customers_P2P_2022_52_WAN_NET | MTS PJSC | ASSIGNED PA | Sep 26, 2022 | [email protected] via mksbalashihi |
| └ 95.64.197.0/24 | 256 | Customers_P2P_2022_53_WAN_NET | MTS PJSC | ASSIGNED PA | Sep 26, 2022 | [email protected] via mksbalashihi |
| └ 95.64.198.0/24 | 256 | Customers_P2P_2022_54_WAN_NET | MTS PJSC | ASSIGNED PA | Sep 26, 2022 | [email protected] via mksbalashihi |
| └ 95.64.199.0/24 | 256 | Customers_P2P_2022_55_WAN_NET | MTS PJSC | ASSIGNED PA | Sep 26, 2022 | [email protected] via mksbalashihi |
| └ 95.64.200.0/24 | 256 | Customers_P2P_2022_56_WAN_NET | MTS PJSC | ASSIGNED PA | Sep 26, 2022 | [email protected] via mksbalashihi |
| └ 95.64.201.0/24 | 256 | Customers_P2P_2022_57_WAN_NET | MTS PJSC | ASSIGNED PA | Sep 26, 2022 | [email protected] via mksbalashihi |
| └ 95.64.202.0/24 | 256 | Customers_P2P_2022_58_WAN_NET | MTS PJSC | ASSIGNED PA | Sep 26, 2022 | [email protected] via mksbalashihi |
| └ 95.64.203.0/24 | 256 | Customers_P2P_2022_59_WAN_NET | MTS PJSC | ASSIGNED PA | Sep 26, 2022 | [email protected] via mksbalashihi |
| └ 95.64.204.0/24 | 256 | Customers_P2P_2022_60_WAN_NET | MTS PJSC | ASSIGNED PA | Oct 12, 2023 | [email protected] via mksbalashihi |
| └ 95.64.205.0/24 | 256 | Customers_P2P_2022_61_WAN_NET | MTS PJSC | ASSIGNED PA | Oct 12, 2023 | [email protected] via mksbalashihi |
| └ 95.64.206.0/24 | 256 | Customers_P2P_2022_62_WAN_NET | MTS PJSC | ASSIGNED PA | Oct 12, 2023 | [email protected] via mksbalashihi |
| └ 95.64.207.0/24 | 256 | Customers_P2P_2022_63_WAN_NET | MTS PJSC | ASSIGNED PA | Oct 12, 2023 | [email protected] via mksbalashihi |
| └ 95.64.208.0/24 | 256 | Customers_P2P_2022_64_WAN_NET | MTS PJSC | ASSIGNED PA | Oct 12, 2023 | [email protected] via mksbalashihi |
| └ 95.64.209.0/24 | 256 | Customers_P2P_2022_65_WAN_NET | MTS PJSC | ASSIGNED PA | Oct 12, 2023 | [email protected] via mksbalashihi |
| └ 95.64.210.0/24 | 256 | Customers_P2P_2022_66_WAN_NET | MTS PJSC | ASSIGNED PA | Oct 12, 2023 | [email protected] via mksbalashihi |
| └ 95.64.211.0/24 | 256 | Customers_P2P_2022_67_WAN_NET | MTS PJSC | ASSIGNED PA | Oct 12, 2023 | [email protected] via mksbalashihi |
| └ 95.64.212.0/24 | 256 | Customers_P2P_2022_68_WAN_NET | MTS PJSC | ASSIGNED PA | Oct 12, 2023 | [email protected] via mksbalashihi |
| └ 95.64.213.0/24 | 256 | Customers_P2P_2022_69_WAN_NET | MTS PJSC | ASSIGNED PA | Oct 12, 2023 | [email protected] via mksbalashihi |
| └ 95.64.214.0/24 | 256 | Customers_P2P_2023_01_WAN_NET | MTS PJSC | ASSIGNED PA | Feb 7, 2023 | [email protected] via mksbalashihi |
| └ 95.64.215.0/24 | 256 | Customers_P2P_2023_02_WAN_NET | MTS PJSC | ASSIGNED PA | Feb 7, 2023 | [email protected] via mksbalashihi |
| └ 95.64.216.0/24 | 256 | Customers_P2P_2023_03_WAN_NET | MTS PJSC | ASSIGNED PA | Feb 7, 2023 | [email protected] via mksbalashihi |
| └ 95.64.217.0/24 | 256 | Customers_P2P_2023_04_WAN_NET | MTS PJSC | ASSIGNED PA | Feb 7, 2023 | [email protected] via mksbalashihi |
| └ 95.64.218.0/24 | 256 | Customers_P2P_2023_05_WAN_NET | MTS PJSC | ASSIGNED PA | Feb 7, 2023 | [email protected] via mksbalashihi |
| └ 95.64.219.0/24 | 256 | Customers_P2P_2023_06_WAN_NET | MTS PJSC | ASSIGNED PA | Feb 7, 2023 | [email protected] via mksbalashihi |
| └ 95.64.220.0/24 | 256 | Customers_P2P_2023_07_WAN_NET | MTS PJSC | ASSIGNED PA | Feb 7, 2023 | [email protected] via mksbalashihi |
| └ 95.64.221.0/24 | 256 | Customers_P2P_2023_08_WAN_NET | MTS PJSC | ASSIGNED PA | Feb 7, 2023 | [email protected] via mksbalashihi |
| └ 95.64.222.0/24 | 256 | Customers_P2P_2023_09_WAN_NET | MTS PJSC | ASSIGNED PA | Feb 7, 2023 | [email protected] via mksbalashihi |
| └ 95.64.223.0/24 | 256 | Customers_P2P_2023_10_WAN_NET | MTS PJSC | ASSIGNED PA | Feb 7, 2023 | [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