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

95.141.138.0/24

3 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
3
1.2% of its addresses · 30 days
Always-on exits
1
33% of its exits
Providers
33
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

2.3K observations

Proxy providers listing exits

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

Announcements

Less specific

Covering announcements

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

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
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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

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