Data as of Nov 10, 2026

93.185.22.0/23

82 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
82
16% of its addresses · 30 days
Always-on exits
3
3.7% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
61
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

10K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
93.185.23.0/24343
93.185.22.0/24039

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BartProxies
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • HideProxy
  • IPFly
  • IPMUSK
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • Maskify
  • NSocks
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • VantageProxies
  • VitalExclusive
  • YumiProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
93.185.16.0/20
since Mar 2026
AS12389Residential604
13 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
93.185.16.0/204,096RU-RTK-20080604PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAJun 4, 2008abuse@rt.ru
└ 93.185.16.0/212,048LENOBL-ADSL-AVANGARD-NETOJSC "Rostelecom" Macroregional Branch North-WestASSIGNED PAJun 5, 2013abuse@rt.ru
via RU-RTK-20080604

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