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

89.151.131.0/24

7 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
7
2.7% of its addresses · 30 days
Always-on exits
1
14% of its exits
Providers
46
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

189 observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • DataImpulse
  • EZProxies
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • GSocks
  • Geonix
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • KindProxy
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Novada
  • PSBProxy
  • PacketStream
  • PrivateByte
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • RoamProxy
  • RolaProxy
  • Shifter
  • SwiftProxy
  • VitalExclusive
  • VitalProxy

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
89.151.128.0/1816,384RU-RTK-20060418PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAApr 18, 2006abuse@rt.ru
└ 89.151.128.0/198,192CHTTSRUADSL users @ Chuvash RepublicASSIGNED PAOct 12, 2007abuse@rt.ru
via RU-RTK-20060418

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

Who has announced 89.151.128.0/18

89.151.128.0/18

Routing history

Pattern
Stable
First seen
May 2006
Current origin since
May 2016 · 11 yr
Origin networks
3
Last change of origin
May 2016
Recorded history

History

Handoffs
2