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

217.65.80.0/20

24 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
24
0.59% of its addresses · 30 days
Always-on exits
2
8.3% of its exits
Spread
11 of 16
/24s with at least one exit
Providers
74
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

6.1K observations
  • Residential
  • Hosting

/24s with the most always-on exits

/24Always-on exitsProxy exits
217.65.84.0/2412
217.65.87.0/2412
217.65.85.0/2404
217.65.91.0/2404
217.65.80.0/2402
217.65.81.0/2402
217.65.82.0/2402
217.65.88.0/2402
217.65.89.0/2402
217.65.83.0/2401
217.65.86.0/2401

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonix
  • GloryCloud
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPMUSK
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LemonLabs
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NextProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PrivateByte
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • RolaProxy
  • Shifter
  • Smartproxy
  • StrikeProxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • TrueProxies
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • YumiProxy
  • ZENPROXY_LITE

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
217.65.80.0/204,096RU-RTK-20030620PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAJun 20, 2003abuse@rt.ru
└ 217.65.80.0/23512NOVOCOMJSC Rostelecom regional branch "Siberia"ASSIGNED PAJul 24, 2003abuse@rt.ru
via RU-RTK-20030620
└ 217.65.82.0/23512NOVOCOMJSC Rostelecom regional branch "Siberia"ASSIGNED PASep 22, 2010abuse@rt.ru
via RU-RTK-20030620
└ 217.65.84.0/24256NOVOCOMJSC Rostelecom regional branch "Siberia"ASSIGNED PAMay 11, 2011abuse@rt.ru
via RU-RTK-20030620
└ 217.65.86.0/24256NOVOCOM-HOSTINGNovocom hosting centerASSIGNED PAMay 8, 2009abuse@rt.ru
via RU-RTK-20030620
└ 217.65.87.0/24256NOVOCOMJSC Rostelecom regional branch "Siberia"ASSIGNED PAAug 19, 2008abuse@rt.ru
via RU-RTK-20030620
└ 217.65.88.0/221,024ROSTELECOMNETJSC Rostelecom LIRASSIGNED PAMay 17, 2013abuse@rt.ru
via RU-RTK-20030620
└ 217.65.92.0/24256NOVOCOMJSC Rostelecom regional branch "Siberia"ASSIGNED PAFeb 14, 2006abuse@rt.ru
via RU-RTK-20030620
└ 217.65.95.0/24256NOVOCOMJSC Rostelecom regional branch "Siberia"ASSIGNED PAApr 27, 2011abuse@rt.ru
via RU-RTK-20030620

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

4,096 addresses
TypeAddressesShareRanges
Residential3,84094%2
Hosting2566.3%1

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2017 · 9.5 yr
Origin networks
3
Last change of origin
May 2017
Recorded history

History

Handoffs
2