Data as of Nov 13, 2026

80.64.96.0/20

25 residential-proxy exits · 30 days

CJSC Rascom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Internet provider
77% of it

Residential-proxy exits

Proxy exits
25
0.61% of its addresses · 30 days
Always-on exits
3
12% of its exits
Spread
4 of 16
/24s with at least one exit
Providers
57
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

3.2K observations
  • Business
  • Internet provider

/24s with the most always-on exits

/24Always-on exitsProxy exits
80.64.101.0/2425
80.64.104.0/2412
80.64.106.0/24016
80.64.105.0/2402

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LemonLabs
  • LemonPrime
  • MangoProxy
  • Maskify
  • NSocks
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • PrivateProxy
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • StrikeProxy
  • Thordata
  • VantageProxies
  • VitalData
  • VitalExclusive

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
80.64.96.0/204,096RU-RASCOM-20010510CJSC Rascom (ORG-CR2-RIPE) · RUALLOCATED PADec 11, 2001abuse@rascom.ru
└ 80.64.96.0/221,024RASCOM-INETCJSC RascomASSIGNED PA—abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.100.0/24256RASCOM-INETCJSC RascomASSIGNED PAMar 9, 2006abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.101.0/24256RASCOM-INETCJSC RascomASSIGNED PAMar 9, 2006abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.102.0/24256RASCOM-INETCJSC RascomASSIGNED PAMar 9, 2006abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.103.0/24256RASCOM-INETCJSC RascomASSIGNED PAMay 17, 2005abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.104.0/2664AMBAR-SERVICEAmbar Service, Ltd.ASSIGNED PAJun 14, 2002abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.104.64/298NET-VOSKHODCustoms and cargo companyASSIGNED PAFeb 19, 2018abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.104.72/298LINXDC-MOW-VIRTU-NET283unknownASSIGNED PAMay 31, 2018abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.104.80/2816RU-GWG-20180221"Global Web Group" LLCASSIGNED PAFeb 21, 2018abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.104.96/2816RASCOM-INETCJSC RascomASSIGNED PAJul 15, 2014abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.104.112/2816LINXDC-MOW-CORAL-AL4869unknownASSIGNED PAFeb 28, 2018abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.104.128/298MSK-IX-NETunknownASSIGNED PAApr 28, 2021abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.104.136/298GZS-NETgazprom-spacesystems.ruASSIGNED PAJun 25, 2025abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.104.144/298LINXDC-MOW-BEST-LLC-AL547unknownASSIGNED PASep 5, 2017abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.104.152/298NET-VOSKHODCustoms and cargo companyASSIGNED PAJun 29, 2018abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.104.160/298LINXDC-CLOUD-MOWunknownASSIGNED PASep 5, 2017abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.104.168/298LINXDC-CLOUD-MOWunknownASSIGNED PASep 5, 2017abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.104.176/2816FERDINANDOLLC FerdinandoASSIGNED PANov 30, 2004abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.104.192/298ZELAXZelaxPlus JSCASSIGNED PADec 22, 2004abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.104.200/298STORMWALL-TUNNELSStormWallASSIGNED PANov 29, 2016abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.104.216/298ASCOM-NETAscomASSIGNED PAApr 25, 2017abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.104.224/2732LINXDC-AT-CONSULTING-DIA-620824unknownASSIGNED PASep 5, 2017abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.105.16/298RECKITT-BENCKISERRBPASSIGNED PANov 27, 2025abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.105.64/2664RttelRTTASSIGNED PAApr 27, 2016abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.105.128/2664ASCOM-NETAscomASSIGNED PAApr 20, 2017abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.105.192/2732SPIMEXCJSC SpimexASSIGNED PASep 6, 2022abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.105.224/2816RU-DOCKERDocker LTDASSIGNED PAMay 31, 2017abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.105.240/298LINXDC-NET-MOWunknownASSIGNED PASep 5, 2017abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.105.248/298RTTELSt.Petersburg, RTTELASSIGNED PAOct 27, 2021abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.106.0/298RU-NEXTREMUM-20230314Nextremum-RUASSIGNED PAMar 15, 2023abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.106.8/304LINXDC-MOW-RENE-NET1047unknownASSIGNED PAMar 23, 2018abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.106.12/312LINXDC-MOW-RENE-NET1047unknownASSIGNED PAOct 3, 2022abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.106.16/298LINXDC-SPB-NET860Ul.Repischeva 20a, Saint Petersburg, Russia, 197375, LinxdatacenterASSIGNED PAFeb 28, 2018abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.106.48/2816AVOSENDRUSSIAN FEDERATION MoscowASSIGNED PANov 15, 2024abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.106.64/2816RU-GWG-20170731"Global Web Group" LLCASSIGNED PAJul 31, 2017abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.106.80/2816ASCOM-NETAscomASSIGNED PAFeb 5, 2015abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.106.112/2816FERDINANDOLLC FerdinandoASSIGNED PAMay 25, 2016abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.106.128/298LEKTON-SPB-NETLekton., St.Petersburg, RussiaASSIGNED PAJan 29, 2020abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.106.136/298okko-voipokko-voipASSIGNED PANov 11, 2020abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.106.144/2816ORG-SL1003-RIPESEGMENTO LtdASSIGNED PAOct 20, 2020abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.106.176/298PSND-SDunknownASSIGNED PAMar 31, 2022abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.106.184/298PSND-SDunknownASSIGNED PAMar 31, 2022abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.106.192/2816ARLIGHT-7-NETunknownASSIGNED PASep 12, 2022abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.106.216/298COM_3160ComfortelASSIGNED PAApr 20, 2023abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.107.0/2664net-26708unknownASSIGNED PAApr 18, 2024abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.107.128/2732EESNETRUSSIAN FEDERATION MoscowASSIGNED PADec 4, 2024abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.108.0/24256RASCOM-INETCJSC RascomASSIGNED PAMay 7, 2009abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.109.0/25128LEKTON-SPB-NETLekton., St.Petersburg, RussiaASSIGNED PAJul 27, 2018abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.109.128/2732LEKTON-SPB-NETLekton., St.Petersburg, RussiaASSIGNED PAJul 27, 2018abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.109.160/2816LEKTON-SPB-NETLekton., St.Petersburg, RussiaASSIGNED PAJul 27, 2018abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.109.176/298net-13899unknownASSIGNED PADec 27, 2018abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.109.192/2664ROKBA-INETJSC RokbaASSIGNED PASep 18, 2017abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.110.0/24256RASCOM-INETCJSC RascomASSIGNED PAJun 11, 2014abuse@rascom.ru
via RU-RASCOM-20010510
└ 80.64.111.0/24256RASCOM-INETCJSC RascomASSIGNED PAJun 11, 2014abuse@rascom.ru
via RU-RASCOM-20010510

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
Internet provider3,16277%22
Business93423%45

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1