Data as of Nov 16, 2026

85.234.9.0/24

8 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
8
3.1% of its addresses · 30 days
Providers
46
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

1.5K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CliProxy
  • Datarama
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonode
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • RolaProxy
  • Shifter
  • VantageProxies
  • VitalExclusive
  • VitalProxy

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.8.0/221,024INFO-LINKINFO-LINK CheboksaryASSIGNED PAJul 12, 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.8.0/22

85.234.8.0/22

Routing history

Pattern
Stable
First seen
Nov 2008
Current origin since
Nov 2008 · 18 yr
Origin networks
1