Data as of Nov 20, 2026

81.90.235.0/24

2 residential-proxy exits · 30 days

RadioCom Ltd

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential
81% of it

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Providers
30
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

211 observations
  • Residential
  • Business

Proxy providers listing exits

  • 9HTTP
  • Ake.net
  • BartProxies
  • BestProxy
  • BirdProxies
  • Byteful
  • EnigmaProxy
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • GonzoProxy
  • HASDATA
  • Infatica
  • LemonBright
  • MangoProxy
  • NSTPROXY_LITE
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • SOTAPROXY
  • Shifter
  • ThunderProxy
  • VantageProxies
  • 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
81.90.224.0/204,096UA-RADIOCOM-20020710RadioCom Ltd (ORG-RL4-RIPE) · UAALLOCATED PAJul 10, 2002abuse@radiocom.net.ua
└ 81.90.235.24/304RADIOCOM-UAISP RadioComASSIGNED PAJul 4, 2015abuse@radiocom.net.ua
via UA-RADIOCOM-20020710
└ 81.90.235.32/304KRONOS-ZP-UAKronosASSIGNED PAApr 4, 2012abuse@radiocom.net.ua
via UA-RADIOCOM-20020710
└ 81.90.235.36/304MegapolisZaporozhyeASSIGNED PAMay 11, 2010abuse@radiocom.net.ua
via UA-RADIOCOM-20020710
└ 81.90.235.40/304ZNPZaporozhyeASSIGNED PAFeb 5, 2014abuse@radiocom.net.ua
via UA-RADIOCOM-20020710
└ 81.90.235.44/304COFFEELIFE-UAZaporozhyeASSIGNED PAApr 20, 2012abuse@radiocom.net.ua
via UA-RADIOCOM-20020710
└ 81.90.235.48/304UFARMA-LTD-UAUfarmaASSIGNED PAMay 12, 2015abuse@radiocom.net.ua
via UA-RADIOCOM-20020710
└ 81.90.235.68/304UFARMA-LTD-UAUfarmaASSIGNED PAOct 28, 2009abuse@radiocom.net.ua
via UA-RADIOCOM-20020710
└ 81.90.235.72/298IVCHENKO-PROGRESSIvchenko ProgressASSIGNED PAJan 17, 2012abuse@radiocom.net.ua
via UA-RADIOCOM-20020710
└ 81.90.235.80/304HAMSTER-ZP-UAHamsterASSIGNED PASep 22, 2010abuse@radiocom.net.ua
via UA-RADIOCOM-20020710
└ 81.90.235.84/304RADIOCOM-UAZaporozhzhyeASSIGNED PAJul 23, 2010abuse@radiocom.net.ua
via UA-RADIOCOM-20020710
└ 81.90.235.108/304UNIKON-UAUnikonASSIGNED PAOct 6, 2010abuse@radiocom.net.ua
via UA-RADIOCOM-20020710
└ 81.90.235.120/298MICROCOM-UAZaporozhyeASSIGNED PAJan 12, 2011abuse@radiocom.net.ua
via UA-RADIOCOM-20020710
└ 81.90.235.144/304RADIOCOM-UAISP RadioComASSIGNED PAJul 4, 2015abuse@radiocom.net.ua
via UA-RADIOCOM-20020710
└ 81.90.235.160/304RADIOCOM-UAISP RadioComASSIGNED PAJul 4, 2015abuse@radiocom.net.ua
via UA-RADIOCOM-20020710
└ 81.90.235.192/2732RADIOCOM-UAISP RadioComASSIGNED PAApr 20, 2011abuse@radiocom.net.ua
via UA-RADIOCOM-20020710
└ 81.90.235.248/304RADIOCOM-UAISP RadioComASSIGNED PAJul 4, 2015abuse@radiocom.net.ua
via UA-RADIOCOM-20020710

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
Residential20881%5
Business4819%10

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Dec 2009
Current origin since
Dec 2009 · 17 yr
Origin networks
1