Data as of Nov 12, 2026

85.173.0.0/22

5 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
5
0.49% of its addresses · 30 days
Spread
2 of 4
/24s with at least one exit
Providers
28
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

482 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
85.173.1.0/2404
85.173.0.0/2401

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EZProxies
  • EnigmaProxy
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPPeak
  • Infatica
  • MangoProxy
  • NovaProxy
  • Novada
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VitalExclusive
  • VitalProxy

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
85.173.0.0/23
since May 2024
AS12389Residential5PJSC Rostelecom
85.173.3.0/24
since Mar 2024
AS44467ResidentialPJSC Rostelecom

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
85.172.0.0/14262,144RU-RTK-20041222PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PADec 22, 2004abuse@rt.ru
└ 85.173.0.0/198,192Macroregional_SouthOJSC Rostelecom Macroregional Branch SouthASSIGNED PAJul 13, 2007abuse@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

Who has announced 85.172.0.0/14

85.172.0.0/14

Routing history

Pattern
Stable
First seen
Sep 2018
Current origin since
Sep 2018 · 8.1 yr
Origin networks
1