Data as of Nov 15, 2026

88.151.176.0/24

5 residential-proxy exits · 30 days

BiKaDa TOO

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low
Recent change
New origin Jul 2026
from AS41371 BiKaDa TOO, after 3 years unannounced

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Providers
40
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

1.0K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • ASHBURNPROXIES
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EZProxies
  • EnigmaProxy
  • FlashProxy
  • GonzoProxy
  • IPFly
  • IPOasis
  • IPPeak
  • Infatica
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Novada
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
88.151.176.0/21
since Oct 2006
AS41371Residential133
13 always on
BiKaDa TOO

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
88.151.176.0/212,048KZ-SKYTELECOM-20060310BiKaDa TOO (ORG-BT99-RIPE) · KZALLOCATED PADec 21, 2016ripe@bikada.kz
└ 88.151.176.0/24256KZ-SKYTELECOM-20060310BiKaDa TOO (ORG-BT99-RIPE) · KZASSIGNED PAFeb 12, 2024ripe@bikada.kz

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Sep 2016
Current origin since
Jul 2026 · 4 mo
Origin networks
1