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

89.239.128.0/18

2,227 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
this exact prefix
RPKI valid
Announced by
AS12389
Type
Residential
98% of it

Residential-proxy exits

Proxy exits
2,227
14% of its addresses · 30 days
Always-on exits
29
1.3% of its exits
Spread
41 of 64
/24s with at least one exit
Providers
114
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

167K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
89.239.146.0/24568
89.239.151.0/24282
89.239.155.0/24276
89.239.145.0/24273
89.239.163.0/24269
89.239.160.0/24268
89.239.147.0/24265
89.239.165.0/24261
89.239.152.0/24177
89.239.148.0/24177
89.239.175.0/24175
89.239.173.0/24171
89.239.149.0/24170
89.239.159.0/24169
89.239.157.0/24163
89.239.169.0/24159
89.239.174.0/24155
89.239.136.0/2412
89.239.164.0/24080
89.239.158.0/24080
89.239.153.0/24075
89.239.168.0/24074
89.239.154.0/24072
89.239.162.0/24071

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • GeekProxy
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • HideProxy
  • HydraProxy
  • IPCola
  • IPFly
  • IPMUSK
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LUMIPROXY
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MagneticProxy
  • MangoProxy
  • Maskify
  • MoMoProxy
  • NSocks
  • NextProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYON
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PrivateByte
  • PrivateProxy
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyStyler
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • ResiProxies
  • RoamProxy
  • RolaProxy
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • StrikeProxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • TrueProxies
  • VProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • Webshare
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

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.239.128.0/1816,384RU-RTK-20070531PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAMay 31, 2007abuse@rt.ru
└ 89.239.128.0 - 89.239.130.255768MVC-NETRostelecomASSIGNED PAMay 4, 2017abuse@rt.ru
via RU-RTK-20070531
└ 89.239.131.0/24256MVC-NETRostelecomASSIGNED PAMay 4, 2017abuse@rt.ru
via RU-RTK-20070531
└ 89.239.132.0/24256MVC-NETRostelecomASSIGNED PAMay 4, 2017abuse@rt.ru
via RU-RTK-20070531
└ 89.239.133.0/24256TREASA-SIMBIRSKThe Ulyanovsk reg. Dept. of Treasury Russia, Ulianovsk, Goncharova 50/1ASSIGNED PAMay 4, 2017abuse@rt.ru
via RU-RTK-20070531
└ 89.239.134.0 - 89.239.138.2551,280MVC-NETRostelecomASSIGNED PAMay 4, 2017abuse@rt.ru
via RU-RTK-20070531
└ 89.239.139.0/24256ULVT-NETRostelecomASSIGNED PAMay 4, 2017abuse@rt.ru
via RU-RTK-20070531
└ 89.239.140.0/221,024MVC-NETRostelecomASSIGNED PAMay 4, 2017abuse@rt.ru
via RU-RTK-20070531
└ 89.239.144.0 - 89.239.175.2558,192MVC-NETRostelecomASSIGNED PAMay 4, 2017abuse@rt.ru
via RU-RTK-20070531
└ 89.239.176.0/212,048MVC-NETRostelecomASSIGNED PAMay 4, 2017abuse@rt.ru
via RU-RTK-20070531
└ 89.239.184.0 - 89.239.186.255768MVC-NETRostelecomASSIGNED PAMay 4, 2017abuse@rt.ru
via RU-RTK-20070531
└ 89.239.187.0/24256MVC-NETRostelecomASSIGNED PAMay 4, 2017abuse@rt.ru
via RU-RTK-20070531
└ 89.239.188.240/2816MEDIACONN-ULPrivate Network of Ulaynovsk branch # 3ASSIGNED PAMay 4, 2017abuse@rt.ru
via RU-RTK-20070531
└ 89.239.189.0/24256MVC-NETRostelecomASSIGNED PAMay 4, 2017abuse@rt.ru
via RU-RTK-20070531
└ 89.239.190.0/2816UVENUniversity Education Volga NetworkASSIGNED PAMay 4, 2017abuse@rt.ru
via RU-RTK-20070531
└ 89.239.190.16/2816AISGorodISPASSIGNED PAMay 4, 2017abuse@rt.ru
via RU-RTK-20070531
└ 89.239.190.48/2816MEDIACONN-ULPrivate Network of Ulaynovsk branch # 3ASSIGNED PAMay 4, 2017abuse@rt.ru
via RU-RTK-20070531
└ 89.239.190.64/2664NICENET-UL-MVC-MAXIPrivate Network of Ulaynovsk branchASSIGNED PAMay 4, 2017abuse@rt.ru
via RU-RTK-20070531
└ 89.239.190.128/25128SICUL-NETLLC "SIBINTEK" Ulyanovsk branchASSIGNED PAMay 4, 2017abuse@rt.ru
via RU-RTK-20070531
└ 89.239.191.0/24256ULVT-NETRostelecomASSIGNED PAMay 4, 2017abuse@rt.ru
via RU-RTK-20070531

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

16,384 addresses
TypeAddressesShareRanges
Residential16,12898%4
Business2561.6%6

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Jun 2007
Current origin since
Apr 2016 · 11 yr
Origin networks
2
Last change of origin
Apr 2016
Recorded history

History

Handoffs
1