Data as of Nov 19, 2026

95.139.66.0/24

4 residential-proxy exits · 30 days

MTS PJSC

Announcement
this exact prefix
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
36
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

276 observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EVOPROXY
  • FLAMEPROXIES_BASIC
  • GEEKPROXY_FLEX
  • GSocks
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • Infatica
  • KindProxy
  • Kookey
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxy-Seller
  • ProxyEmpire
  • ProxyStyler
  • Proxyma
  • PuraRoute
  • RainProxy
  • SOTAPROXY
  • Shifter
  • VantageProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.139.0.0/17
since Feb 2023
AS8359Mobile3,898
512 always on
MTS PJSC

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, 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

Summary

Routing history

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