Data as of Nov 20, 2026

91.135.193.0/24

5 residential-proxy exits · 30 days

Radiobaylanys LLP

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

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Providers
25
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

564 observations

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • 9HTTP
  • APROXY
  • ASHBURNPROXIES
  • BestProxy
  • Byteful
  • CROXY
  • FastProxy
  • GEEKPROXY_FLEX
  • KocerRoxy
  • LUMIPROXY
  • LemonBright
  • MangoProxy
  • NSocks
  • NiuProxy
  • PROXYLANE
  • PROXY_CC
  • Proxies.fo
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • ThunderProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
91.135.192.0/22
since May 2017
AS29046Internet provider27Radiobaylanys LLP
91.135.192.0/20
since Apr 2026
AS29046Internet provider134
11 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
91.135.192.0/204,096KZ-RBK-20061123Radiobaylanys LLP (ORG-RL35-RIPE) · KZALLOCATED PANov 23, 2006regmaster@rbk.kz
└ 91.135.192.0 - 91.135.197.2551,536RBK-NETRadiobaylanys Almaty Network 91.135.192.0/22ASSIGNED PAJan 26, 2010regmaster@rbk.kz
via KZ-RBK-20061123

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
Apr 2010
Current origin since
Apr 2010 · 17 yr
Origin networks
1