Data as of Nov 14, 2026

85.234.0.0/22

10 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
10
0.98% of its addresses · 30 days
Spread
3 of 4
/24s with at least one exit
Providers
40
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

1.2K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
85.234.3.0/2406
85.234.2.0/2403
85.234.1.0/2401

Proxy providers listing exits

  • 2Captcha
  • 911Proxy
  • ASHBURNPROXIES
  • Ake.net
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CROXY
  • CliProxy
  • DataImpulse
  • Decodo
  • GloryCloud
  • GonzoProxy
  • IPFly
  • Infatica
  • KindProxy
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

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
85.234.0.0/198,192RU-RTK-20050426PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAFeb 18, 2020abuse@rt.ru
└ 85.234.0.0/221,024INFO-LINKINFO-LINK CheboksaryASSIGNED PAApr 26, 2005abuse@rt.ru
via RU-RTK-20050426

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

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 21 yr
Origin networks
1