Data as of Nov 20, 2026

85.175.60.0/23

4 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
4
0.78% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
18
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

418 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
85.175.60.0/2402
85.175.61.0/2401

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Datarama
  • Evomi
  • GonzoProxy
  • IPFly
  • Infatica
  • InfiniteProxies
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
85.172.0.0/14
since Sep 2018
AS12389Residential39,635
3,232 always on
PJSC Rostelecom

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.172.0.0/14262,144RU-RTK-20041222PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PADec 22, 2004abuse@rt.ru
└ 85.175.0.0/1665,536Rostelecom_netOJSC Rostelecom Macroregional Branch SouthSUB-ALLOCATED PAMar 28, 2022abuse@rt.ru
via RU-RTK-20041222
└ 85.175.60.0/24256Rostelecom_netunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via Rostelecom_net
└ 85.175.61.0/24256Rostelecom_netunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via Rostelecom_net

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

Summary

Routing history

Pattern
Stable
First seen
Aug 2020
Current origin since
Aug 2020 · 6.2 yr
Origin networks
1