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

89.20.2.0/24

39 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

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

Exits seen per day

3.3K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • Ake.net
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • Proxio
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Thordata
  • VantageProxies
  • VitalExclusive

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
89.20.0.0/198,192RU-RTK-20060829PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAAug 29, 2006abuse@rt.ru
└ 89.20.0.0/204,096LENOBL-ADSL-AVANGARD-NETAddress for clients of Avangard-ADSLASSIGNED PAMar 30, 2016abuse@rt.ru
via RU-RTK-20060829

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.20.0.0/19

89.20.0.0/19

Routing history

Pattern
Rotating
First seen
Sep 2006
Current origin since
Apr 2024 · 2.5 yr
Origin networks
3
Last change of origin
Nov 2021
Recorded history

History

Handoffs
4