Data as of Nov 19, 2026

89.250.160.0/20

1,018 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
1,018
25% of its addresses · 30 days
Always-on exits
638
63% of its exits
Spread
6 of 16
/24s with at least one exit
Providers
64
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

1.5M observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • CoreProxy
  • DataImpulse
  • Decodo
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • Geonode
  • GoProxies
  • GonzoProxy
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LightningProxies
  • LudaxProxy
  • MagneticProxy
  • MarsProxies
  • Maskify
  • NSocks
  • NextProxy
  • NodeMaven
  • NovProxy
  • Oxylabs
  • PacketStream
  • Proxies.fo
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • RoamProxy
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • TrueProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • Webshare
  • ZENPROXY_PREMIUM

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
89.250.160.0/22
since Apr 2016
AS12389Residential1PJSC Rostelecom
89.250.164.0/23
since Apr 2016
AS12389ResidentialPJSC Rostelecom
89.250.166.0/23
since Aug 2016
AS12389Residential500
320 always on
PJSC Rostelecom
89.250.171.0/24
since Apr 2016
AS12389ResidentialPJSC Rostelecom
89.250.174.0/23
since Apr 2017
AS12389Residential497
318 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
└ 89.250.168.0/23512MRF-VOLGA-UL-DYNPOOL-25-03-2013-1Dyn. address space for broadband usersASSIGNED PAApr 27, 2017abuse@rt.ru
via RU-RTK-20060814
└ 89.250.170.0/24256RU-RTKunknownASSIGNED PAJul 22, 2025abuse@rt.ru
via RU-RTK-20060814
└ 89.250.171.0/24256STS-NETOJSC Rostelecom, Ulianovsk branchASSIGNED PAApr 27, 2017abuse@rt.ru
via RU-RTK-20060814
└ 89.250.172.0/221,024MRF-VOLGA-UL-DYNPOOL-25-03-2013-2Dyn. address space for broadband usersASSIGNED 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

Who has announced this prefix

Summary

Routing history

Pattern
Reactivated
First seen
May 2008
Current origin since
Nov 2023 · 3.0 yr
Origin networks
3
Last change of origin
Nov 2023
Recorded history

History

Handoffs
2