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

80.64.104.0/24

2 residential-proxy exits · 30 days

CJSC Rascom

Announcement
80.64.96.0/20
RPKI valid
Announced by
AS20764
Type
Business
91% of it

Residential-proxy exits

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

Exits seen per day

601 observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • DataImpulse
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • Geonode
  • InfiniteProxies
  • Kookey
  • NovaProxy
  • Oxylabs
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • StrikeProxy
  • Thordata

Registrations in this block

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

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

256 addresses
TypeAddressesShareRanges
Business23291%16
Internet provider249.4%2

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced 80.64.96.0/20

80.64.96.0/20

Routing history

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