LAYER3 INTEL
Get started
Sign in
Data as of Nov 12, 2026

188.0.147.0/24

17 residential-proxy exits · 30 days

Qmobile JSC

Announcement
this exact prefix
RPKI valid
Announced by
AS35104
Type
Mobile
Risk
10 / 100 · Low
Shared address

Residential-proxy exits

Proxy exits
17
6.6% of its addresses · 30 days
Always-on exits
1
5.9% of its exits
Providers
46
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

2.5K observations

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • ASHBURNPROXIES
  • Ake.net
  • BartProxies
  • BestProxy
  • BirdProxies
  • ByteProxies
  • Byteful
  • CROXY
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FastProxy
  • GSocks
  • Geonix
  • GhostConnect
  • GonzoProxy
  • HideProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonBright
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXYON
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

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
188.0.128.0/198,192KZ-KAZTRANSCOM-20110524Qmobile JSC (ORG-OA9-RIPE) · KZALLOCATED PASep 1, 2014abuse@jusanmobile.kz
└ 188.0.147.0/24256JUSAN-MOBILE"Jusan-Mobile" JSCASSIGNED PAJun 9, 2020abuse@jusanmobile.kz
via KZ-KAZTRANSCOM-20110524

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Nov 2016
Current origin since
Nov 2016 · 10 yr
Origin networks
1