Data as of Nov 14, 2026

81.18.35.0/24

12 residential-proxy exits · 30 days

Radiobaylanys LLP

Announcement
this exact prefix
RPKI valid
Announced by
Type
Internet provider
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
12
4.7% of its addresses · 30 days
Providers
36
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

1.6K observations

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • APROXY
  • ASHBURNPROXIES
  • Ake.net
  • BestProxy
  • BirdProxies
  • ByteProxies
  • Byteful
  • CROXY
  • CliProxy
  • FastProxy
  • GSocks
  • IPPeak
  • Infatica
  • LUMIPROXY
  • LemonBright
  • LemonPrime
  • NSocks
  • NiuProxy
  • NodeProxy
  • PROXYSALE
  • PROXY_CC
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • QUANTICDATA
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
81.18.32.0/20
since Apr 2026
AS29046Internet provider120
6 always on
Radiobaylanys LLP

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.18.32.0/204,096KZ-RBK-20100210Radiobaylanys LLP (ORG-RL35-RIPE) · KZALLOCATED PAFeb 10, 2010regmaster@rbk.kz
└ 81.18.35.0/24256NET35-PVL-RBK-KZPavlodar NetworkASSIGNED PASep 16, 2013regmaster@rbk.kz
via KZ-RBK-20100210

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Oct 2013
Current origin since
Oct 2013 · 13 yr
Origin networks
1