Data as of Nov 19, 2026

85.174.238.0/24

30 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
30
12% of its addresses · 30 days
Providers
30
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

147 observations

Proxy providers listing exits

  • AETHYN_ELITE
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • HASDATA
  • IPFly
  • IPPeak
  • Infatica
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • SOTAPROXY
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
85.174.224.0/20
since Jul 2013
AS25490Residential141
3 always on
PJSC Rostelecom
85.172.0.0/14
since Sep 2018
AS12389Residential39,610
3,231 always on
PJSC Rostelecom

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
85.172.0.0/14262,144RU-RTK-20041222PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PADec 22, 2004abuse@rt.ru
└ 85.174.224.0/204,096Macroregional_SouthOJSC Rostelecom Macroregional Branch SouthASSIGNED PAJun 18, 2008abuse@rt.ru
via RU-RTK-20041222

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

85.174.232.0/21

Routing history

Pattern
Stable
First seen
Oct 2025
Current origin since
Oct 2025 · 1.1 yr
Origin networks
1