Data as of Nov 20, 2026

95.64.214.0/24

2 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
2
0.78% of its addresses · 30 days
Providers
33
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

1.0K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BottingTools
  • BuyingProxy
  • Byteful
  • CatProxies
  • CoreProxy
  • DataImpulse
  • EnigmaProxy
  • Evomi
  • GeekProxy
  • GloryCloud
  • IPFly
  • IPRoyal
  • InfiniteProxies
  • KindProxy
  • Kookey
  • MarsProxies
  • Maskify
  • MoMoProxy
  • NovaProxy
  • Novada
  • PSBProxy
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • RolaProxy
  • SpyderProxy
  • TalorData
  • Thordata
  • TrustProxy
  • VProxy

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.192.0/198,192mksbalashihiMTS PJSCSUB-ALLOCATED PASep 26, 2022abuse@mtu.ru
via RU-MTU-20090424
└ 95.64.214.0/24256Customers_P2P_2023_01_WAN_NETMTS PJSCASSIGNED PAFeb 7, 2023abuse@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