Data as of Nov 21, 2026

95.139.64.0/24

4 residential-proxy exits · 30 days

MTS PJSC

Announcement
No RPKI
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Always-on exits
1
25% of its exits
Providers
35
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

2.6K observations

Proxy providers listing exits

  • 911Proxy
  • 9HTTP
  • BestProxy
  • BlurPath
  • BottingTools
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • Evomi
  • GSocks
  • GloryCloud
  • IPFly
  • IPMUSK
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KindProxy
  • LUMIPROXY
  • MangoProxy
  • MoMoProxy
  • NSocks
  • NodeProxy
  • Novada
  • Oxylabs
  • PROXY_CC
  • Proxies.fo
  • Proxiware
  • Proxy4U
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.139.0.0/17
since Feb 2023
AS8359Mobile3,926
516 always on
MTS PJSC

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
95.139.0.0/1732,768RU-MTU-20090325MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAMar 25, 2009abuse@mtu.ru
└ 95.139.64.0/212,048Comstar-Astrakhan-NetAstrakhan Branch of Comstar-RegionsASSIGNED PAAug 23, 2012abuse@mtu.ru
via RU-MTU-20090325

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

Covering aggregate above, the prefix's own history below

95.139.64.0/23

Routing history

Pattern
Stable
First seen
Mar 2023
Current origin since
Mar 2023 · 3.7 yr
Origin networks
1