Data as of Nov 10, 2026

89.239.136.0/24

2 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Always-on exits
1
50% of its exits
Providers
22
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

2.0K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • FlashProxy
  • GonzoProxy
  • IPOasis
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • Shifter
  • VitalExclusive
  • VitalProxy

Registrations in this block

The registry's network records over this block, widest first, each 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.134.0 - 89.239.138.2551,280MVC-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.

Network & registry

Routing timeline

Who has announced 89.239.128.0/18

89.239.128.0/18

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