Data as of Nov 21, 2026

195.34.237.0/24

4 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
RPKI valid
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
32
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

1.7K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FlashProxy
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • GonzoProxy
  • IPOasis
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • SOTAPROXY
  • Shifter
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
195.34.224.0/20
since May 2005
AS8570Residential34
3 always on
PJSC Rostelecom
195.34.224.0/19
since May 2005
AS8570Residential98
11 always on
PJSC Rostelecom

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
195.34.224.0/198,192RU-RTK-971125PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PASep 25, 2002abuse@rt.ru
└ 195.34.237.0/24256LES-P2P-009-NETAddress block for point-to-point LL connections for LES CustomersASSIGNED PAMar 21, 2005abuse@rt.ru
via RU-RTK-971125

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

195.34.232.0/21

Routing history

Pattern
Stable
First seen
Jun 2006
Current origin since
Jun 2006 · 20 yr
Origin networks
1