Data as of Nov 10, 2026

89.250.166.0/23

504 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
504
98% of its addresses · 30 days
Always-on exits
323
64% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
42
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

543K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
89.250.167.0/24163246
89.250.166.0/24160256

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • CoreProxy
  • DataImpulse
  • Decodo
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • GoProxies
  • GonzoProxy
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • MarsProxies
  • Maskify
  • NSocks
  • Oxylabs
  • PacketStream
  • PrivateProxy
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
89.250.160.0/20
since Nov 2023
AS12389Residential1,011
634 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
89.250.160.0/204,096RU-RTK-20060814PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAAug 14, 2006abuse@rt.ru
└ 89.250.160.0/212,048STS-NETOJSC Rostelecom, Ulianovsk branchASSIGNED PAApr 27, 2017abuse@rt.ru
via RU-RTK-20060814

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
Mar 2013
Current origin since
Aug 2016 · 10 yr
Origin networks
2
Last change of origin
Aug 2016
Recorded history

History

Handoffs
1