Data as of Nov 16, 2026

85.234.28.0/24

3 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Providers
33
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

471 observations

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • Decodo
  • EnigmaProxy
  • Geonode
  • GonzoProxy
  • HydraProxy
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • MangoProxy
  • NextProxy
  • NodeMaven
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • Shifter
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_X
  • ThunderProxy
  • VitalExclusive
  • VitalProxy
  • Webshare

Registrations in this block

The registry's network records over this block, widest first, each 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.28.0/221,024INFO-LINKINFO-LINK CheboksaryASSIGNED PAJul 11, 2012abuse@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 85.234.28.0/22

85.234.28.0/22

Routing history

Pattern
Stable
First seen
Feb 2009
Current origin since
Feb 2009 · 18 yr
Origin networks
1