Data as of Nov 16, 2026

95.141.138.0/26

1 residential-proxy exit · 30 days

Qmobile JSC

Announcement
RPKI valid
Announced by
Type
Mobile
Risk
10 / 100 · Low
Shared address

Residential-proxy exits

Proxy exits
1
1.6% of its addresses · 30 days
Always-on exits
1
100% of its exits
Providers
35
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

21 observations

Proxy providers listing exits

  • 711Proxy
  • AETHYN_ELITE
  • Ake.net
  • AnyIP
  • BestProxy
  • BirdProxies
  • BottingTools
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlashProxy
  • GEEKPROXY_FLEX
  • Infatica
  • Kookey
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeProxy
  • Novada
  • PROXYSCRAPE
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • RapidProxy
  • Shifter
  • Smartproxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.141.136.0/22
since Apr 2020
AS35104Mobile14
2 always on
Qmobile JSC

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
95.141.128.0/204,096KZ-KAZTRANSCOM-20090605Qmobile JSC (ORG-OA9-RIPE) · KZALLOCATED PAJun 5, 2009abuse@jusanmobile.kz
└ 95.141.138.0/24256QMOBILE"QMobile" JSCASSIGNED PANov 10, 2026abuse@jusanmobile.kz
via KZ-KAZTRANSCOM-20090605

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

95.141.138.0/24

Routing history

Pattern
Stable
First seen
Jul 2009
Current origin since
Dec 2020 · 5.9 yr
Origin networks
1