Data as of Nov 14, 2026

80.64.105.0/24

2 residential-proxy exits · 30 days

CJSC Rascom

Announcement
RPKI valid
Announced by
Type
Business
78% of it

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Providers
3
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

96 observations

Proxy providers listing exits

  • BottingTools
  • IPFly
  • PuraRoute

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.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

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
Business20078%7
Internet provider5622%2

Network & registry

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