Data as of Nov 11, 2026

85.93.60.0/24

248 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Internet provider
Risk
0 / 100 · Low
Proxy exits nearby

Residential-proxy exits

Proxy exits
248
97% of its addresses · 30 days
Always-on exits
173
70% of its exits
Providers
38
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

303K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CoreProxy
  • DataImpulse
  • Decodo
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • GoProxies
  • GonzoProxy
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • Maskify
  • NSocks
  • Oxylabs
  • PacketStream
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
85.93.32.0/19
since Mar 2016
AS12389Residential1,134
722 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.93.32.0/198,192RU-RTK-20041207PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PADec 7, 2004abuse@rt.ru
└ 85.93.60.0/24256CAIT-BACKBONECAIT backbone net (core and distribution)ASSIGNED PAJun 8, 2006abuse@rt.ru
via RU-RTK-20041207

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
Mar 2017
Current origin since
Mar 2017 · 9.6 yr
Origin networks
1