LAYER3 INTEL
Get started
Sign in
Data as of Nov 13, 2026

85.172.84.0/22

4 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
this exact prefix
RPKI valid
Announced by
AS25490
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
4
0.39% of its addresses · 30 days
Spread
3 of 4
/24s with at least one exit
Providers
27
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

693 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
85.172.86.0/2402
85.172.84.0/2401
85.172.87.0/2401

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlashProxy
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • MangoProxy
  • NodeMaven
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • Shifter
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
85.172.0.0/14
since Sep 2018
AS12389Residential39,081
2,989 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.80.0/212,048Macroregional_SouthOJSC Rostelecom Macroregional Branch SouthASSIGNED PASep 25, 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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Dec 2019
Current origin since
Dec 2019 · 6.9 yr
Origin networks
1