Data as of Nov 20, 2026

89.190.238.0/24

17 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
17
6.6% of its addresses · 30 days
Providers
47
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

763 observations

Proxy providers listing exits

  • AETHYN_ELITE
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CliProxy
  • DataImpulse
  • EVOPROXY
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • KindProxy
  • LemonLabs
  • LemonPrime
  • MangoProxy
  • NextProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • PROXIWARE_ECO
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • SOTAPROXY
  • Shifter
  • SwiftProxy
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
89.190.224.0/19
since Dec 2021
AS12389Residential657
1 always on
PJSC Rostelecom

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
89.190.224.0/198,192RU-RTK-20060614PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAJun 14, 2006abuse@rt.ru
└ 89.190.224.0/204,096BALTNET-NETADSL dynamic poolASSIGNED PAJun 9, 2023abuse@rt.ru
via RU-RTK-20060614

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

89.190.224.0/20

Routing history

Pattern
Stable
First seen
Feb 2020
Current origin since
Feb 2020 · 6.8 yr
Origin networks
1