LAYER3 INTEL
Get started
Sign in
Data as of Nov 13, 2026

95.64.141.0/24

3 residential-proxy exits · 30 days

MTS PJSC

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

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Always-on exits
1
33% of its exits
Providers
17
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

325 observations

Proxy providers listing exits

  • 9Proxy
  • BottingTools
  • BuyingProxy
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Evomi
  • GSocks
  • Geonode
  • IPFly
  • IPPeak
  • InfiniteProxies
  • Oxylabs
  • ProxyGeo
  • PuraRoute
  • RealProxy

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.141.0/24256Customers_P2P_2021_74_WAN_NETMTS PJSCASSIGNED PADec 9, 2021abuse@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

AnnouncementRouting historyRPKI & IRRWhois & abuse
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