Data as of Nov 18, 2026

85.172.184.0/21

23 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
23
1.1% of its addresses · 30 days
Always-on exits
6
26% of its exits
Spread
7 of 8
/24s with at least one exit
Providers
67
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

8.3K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9HTTP
  • Ake.net
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FlashProxy
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • GhostConnect
  • GonzoProxy
  • HASDATA
  • HideProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LightningProxies
  • MangoProxy
  • MarsProxies
  • NextProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYLANE
  • PROXYSCRAPE
  • Proxies.fo
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
85.172.0.0/14
since Sep 2018
AS12389Residential39,694
3,240 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.172.176.0/204,096Macroregional_SouthOJSC Rostelecom Macroregional Branch SouthASSIGNED PAJul 4, 2006abuse@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

Summary

Routing history

Pattern
Stable
First seen
Nov 2009
Current origin since
Nov 2024 · 2.0 yr
Origin networks
1