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

85.173.160.0/22

5 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

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

Exits seen per day

206 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
85.173.163.0/2403
85.173.162.0/2402

Proxy providers listing exits

  • BirdProxies
  • Byteful
  • CatProxies
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FastProxy
  • GSocks
  • GhostConnect
  • HideProxy
  • IPFly
  • Infatica
  • InfiniteProxies
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • ProxiesVision
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • PuraRoute
  • Shifter
  • VantageProxies

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 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.173.160.0/198,192Macroregional_SouthunknownSUB-ALLOCATED PAAug 27, 2025abuse@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
Nov 2024
Current origin since
Nov 2024 · 2.0 yr
Origin networks
1