Data as of Nov 11, 2026

85.192.130.0/24

10 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
10
3.9% of its addresses · 30 days
Always-on exits
3
30% of its exits
Providers
42
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

4.2K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EZProxies
  • EnigmaProxy
  • FastProxy
  • Geonode
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • Kookey
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NodeMaven
  • NovaProxy
  • Novada
  • Oxylabs
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • YumiProxy
  • ZENPROXY_LITE

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
85.192.128.0/1816,384RU-RTK-20041215PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PADec 15, 2004abuse@rt.ru
└ 85.192.128.0 - 85.192.140.313,104ESOO-NETOJSC "VolgaTelecom" OrenburgASSIGNED PAMay 16, 2007abuse@rt.ru
via RU-RTK-20041215

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.192.128.0/18

85.192.128.0/18

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2016 · 10 yr
Origin networks
2
Last change of origin
May 2016
Recorded history

History

Handoffs
1