Data as of Nov 16, 2026

95.64.128.0/18

87 residential-proxy exits · 30 days

MTS PJSC

Announcement
No RPKI
Announced by
Type
Mobile
Risk
10 / 100 · Low
Shared address

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

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.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
95.64.128.0/1732,768RU-MTU-20090424MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PASep 3, 2021abuse@mtu.ru
└ 95.64.128.0/1816,384mksbalashihiPJSC MTSSUB-ALLOCATED PAOct 4, 2021abuse@mtu.ru
via RU-MTU-20090424
└ 95.64.128.0/24256Customers_P2P_2021_61_WAN_NETMTS PJSCASSIGNED PANov 8, 2021abuse@mtu.ru
via mksbalashihi
└ 95.64.129.0/24256Customers_P2P_2021_62_WAN_NETMTS PJSCASSIGNED PANov 8, 2021abuse@mtu.ru
via mksbalashihi
└ 95.64.130.0/24256Customers_P2P_2021_63_WAN_NETMTS PJSCASSIGNED PANov 8, 2021abuse@mtu.ru
via mksbalashihi
└ 95.64.131.0/24256Customers_P2P_2021_64_WAN_NETMTS PJSCASSIGNED PANov 8, 2021abuse@mtu.ru
via mksbalashihi
└ 95.64.132.0/24256Customers_P2P_2021_65_WAN_NETMTS PJSCASSIGNED PANov 8, 2021abuse@mtu.ru
via mksbalashihi
└ 95.64.133.0/24256Customers_P2P_2021_66_WAN_NETMTS PJSCASSIGNED PANov 8, 2021abuse@mtu.ru
via mksbalashihi
└ 95.64.134.0/24256Customers_P2P_2021_67_WAN_NETMTS PJSCASSIGNED PANov 8, 2021abuse@mtu.ru
via mksbalashihi
└ 95.64.135.0/24256Customers_P2P_2021_68_WAN_NETMTS PJSCASSIGNED PANov 8, 2021abuse@mtu.ru
via mksbalashihi
└ 95.64.136.0/24256Customers_P2P_2021_69_WAN_NETMTS PJSCASSIGNED PANov 8, 2021abuse@mtu.ru
via mksbalashihi
└ 95.64.137.0/24256Customers_P2P_2021_70_WAN_NETMTS PJSCASSIGNED PANov 8, 2021abuse@mtu.ru
via mksbalashihi
└ 95.64.138.0/24256Customers_P2P_2021_71_WAN_NETMTS PJSCASSIGNED PADec 9, 2021abuse@mtu.ru
via mksbalashihi
└ 95.64.139.0/24256Customers_P2P_2021_72_WAN_NETMTS PJSCASSIGNED PADec 9, 2021abuse@mtu.ru
via mksbalashihi
└ 95.64.140.0/24256Customers_P2P_2021_73_WAN_NETMTS PJSCASSIGNED PADec 9, 2021abuse@mtu.ru
via mksbalashihi
└ 95.64.141.0/24256Customers_P2P_2021_74_WAN_NETMTS PJSCASSIGNED PADec 9, 2021abuse@mtu.ru
via mksbalashihi
└ 95.64.142.0/24256Customers_P2P_2021_75_WAN_NETMTS PJSCASSIGNED PADec 9, 2021abuse@mtu.ru
via mksbalashihi
└ 95.64.143.0/24256Customers_P2P_2021_76_WAN_NETMTS PJSCASSIGNED PADec 9, 2021abuse@mtu.ru
via mksbalashihi
└ 95.64.144.0/24256Customers_P2P_2022_00_WAN_NETMTS PJSCASSIGNED PAJan 14, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.145.0/24256Customers_P2P_2022_01_WAN_NETMTS PJSCASSIGNED PAJan 14, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.146.0/24256Customers_P2P_2022_02_WAN_NETMTS PJSCASSIGNED PAJan 14, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.147.0/24256Customers_P2P_2022_03_WAN_NETMTS PJSCASSIGNED PAJan 14, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.148.0/24256Customers_P2P_2022_04_WAN_NETMTS PJSCASSIGNED PAJan 14, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.149.0/24256Customers_P2P_2022_05_WAN_NETMTS PJSCASSIGNED PAJan 14, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.150.0/24256Customers_P2P_2022_06_WAN_NETMTS PJSCASSIGNED PAJan 14, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.151.0/24256Customers_P2P_2022_07_WAN_NETMTS PJSCASSIGNED PAJan 14, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.152.0/24256Customers_P2P_2022_08_WAN_NETMTS PJSCASSIGNED PAMar 14, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.153.0/24256Customers_P2P_2022_09_WAN_NETMTS PJSCASSIGNED PAMar 14, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.154.0/24256Customers_P2P_2022_10_WAN_NETMTS PJSCASSIGNED PAMar 14, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.155.0/24256Customers_P2P_2022_11_WAN_NETMTS PJSCASSIGNED PAMar 14, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.156.0/24256Customers_P2P_2022_12_WAN_NETMTS PJSCASSIGNED PAMar 14, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.157.0/24256Customers_P2P_2022_13_WAN_NETMTS PJSCASSIGNED PAMar 14, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.158.0/24256Customers_P2P_2022_14_WAN_NETMTS PJSCASSIGNED PAMar 14, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.159.0/24256Customers_P2P_2022_15_WAN_NETMTS PJSCASSIGNED PAMar 14, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.160.0/24256Customers_P2P_2022_16_WAN_NETMTS PJSCASSIGNED PAMar 14, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.161.0/24256Customers_P2P_2022_17_WAN_NETMTS PJSCASSIGNED PAMar 14, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.162.0/24256Customers_P2P_2022_18_WAN_NETMTS PJSCASSIGNED PAMay 5, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.163.0/24256Customers_P2P_2022_19_WAN_NETMTS PJSCASSIGNED PAMay 5, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.164.0/24256Customers_P2P_2022_20_WAN_NETMTS PJSCASSIGNED PAMay 5, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.165.0/24256Customers_P2P_2022_21_WAN_NETMTS PJSCASSIGNED PAMay 5, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.166.0/24256Customers_P2P_2022_22_WAN_NETMTS PJSCASSIGNED PAMay 5, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.167.0/24256Customers_P2P_2022_23_WAN_NETMTS PJSCASSIGNED PAMay 5, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.168.0/24256Customers_P2P_2022_24_WAN_NETMTS PJSCASSIGNED PAMay 5, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.169.0/24256Customers_P2P_2022_25_WAN_NETMTS PJSCASSIGNED PAMay 5, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.170.0/24256Customers_P2P_2022_26_WAN_NETMTS PJSCASSIGNED PAMay 5, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.171.0/24256Customers_P2P_2022_27_WAN_NETMTS PJSCASSIGNED PAMay 5, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.172.0/24256Customers_P2P_2022_28_WAN_NETMTS PJSCASSIGNED PAMay 5, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.173.0/24256Customers_P2P_2022_29_WAN_NETMTS PJSCASSIGNED PAJun 20, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.174.0/24256Customers_P2P_2022_30_WAN_NETMTS PJSCASSIGNED PAJun 20, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.175.0/24256Customers_P2P_2022_31_WAN_NETMTS PJSCASSIGNED PAJun 20, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.176.0/24256Customers_P2P_2022_32_WAN_NETMTS PJSCASSIGNED PAJun 20, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.177.0/24256Customers_P2P_2022_33_WAN_NETMTS PJSCASSIGNED PAJun 20, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.178.0/24256Customers_P2P_2022_34_WAN_NETMTS PJSCASSIGNED PAJun 20, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.179.0/24256Customers_P2P_2022_35_WAN_NETMTS PJSCASSIGNED PAJun 20, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.180.0/24256Customers_P2P_2022_36_WAN_NETMTS PJSCASSIGNED PAJun 20, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.181.0/24256Customers_P2P_2022_37_WAN_NETMTS PJSCASSIGNED PAJun 20, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.182.0/24256Customers_P2P_2022_38_WAN_NETMTS PJSCASSIGNED PAAug 8, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.183.0/24256Customers_P2P_2022_39_WAN_NETMTS PJSCASSIGNED PAAug 8, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.184.0/24256Customers_P2P_2022_40_WAN_NETMTS PJSCASSIGNED PAAug 8, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.185.0/24256Customers_P2P_2022_41_WAN_NETMTS PJSCASSIGNED PAAug 8, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.186.0/24256Customers_P2P_2022_42_WAN_NETMTS PJSCASSIGNED PAAug 8, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.187.0/24256Customers_P2P_2022_43_WAN_NETMTS PJSCASSIGNED PAAug 8, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.188.0/24256Customers_P2P_2022_44_WAN_NETMTS PJSCASSIGNED PAAug 8, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.189.0/24256Customers_P2P_2022_45_WAN_NETMTS PJSCASSIGNED PAAug 8, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.190.0/24256Customers_P2P_2022_46_WAN_NETMTS PJSCASSIGNED PAAug 8, 2022abuse@mtu.ru
via mksbalashihi
└ 95.64.191.0/24256Customers_P2P_2022_47_WAN_NETMTS PJSCASSIGNED PAAug 8, 2022abuse@mtu.ru
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

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