Data as of Nov 22, 2026

195.34.233.4/30

No anonymizer space · no proxy exits in 30 days

PJSC Rostelecom

Announcement
RPKI valid
Announced by
Type
Business
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
2
50% of its addresses · listed by providers
Providers
37
selling exits here

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • AETHYN_ELITE
  • BUYPERSONALPROXY
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • Datarama
  • Evomi
  • Geonode
  • GhostConnect
  • GonzoProxy
  • Infatica
  • InfiniteProxies
  • LudaxProxy
  • MangoProxy
  • NSocks
  • NodeMaven
  • NovaProxy
  • PROXYLANE
  • PROXYON
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • RainProxy
  • SOTAPROXY
  • Shifter
  • Smartproxy
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
195.34.224.0/20
since May 2005
AS8570Residential33
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.233.4/304LIP-STEK-1-NETJSC StekASSIGNED PAMar 28, 2008abuse@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