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

85.173.112.0/24

23 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
85.173.96.0/19
RPKI valid
Announced by
AS43132
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
23
9.0% of its addresses · 30 days
Always-on exits
1
4.3% of its exits
Providers
38
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

1.2K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BartProxies
  • BestProxy
  • BottingTools
  • BuyingProxy
  • Byteful
  • CROXY
  • CatProxies
  • Datarama
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • Geonode
  • GhostConnect
  • GloryCloud
  • IPFly
  • IPMUSK
  • IPPeak
  • InfiniteProxies
  • LudaxProxy
  • NSocks
  • NovaProxy
  • PrivateProxy
  • ProxiesVision
  • Proxiware
  • ProxyGeo
  • PuraRoute
  • RainProxy
  • RapidProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
85.172.0.0/14
since Sep 2018
AS12389Residential39,298
3,146 always on
PJSC 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.96.0/198,192Macroregional_SouthKabbalktelecom (ORG-KBT2-RIPE) · RUASSIGNED PAMay 29, 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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

85.173.96.0/19

Routing history

Pattern
Stable
First seen
Oct 2009
Current origin since
Oct 2009 · 17 yr
Origin networks
1