Data as of Nov 17, 2026

77.245.108.0/24

4 residential-proxy exits · 30 days

Qmobile JSC

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

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Always-on exits
1
25% of its exits
Providers
41
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

2.3K observations

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • 9Proxy
  • APROXY
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CROXY
  • EnigmaProxy
  • Evomi
  • Geonode
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LUMIPROXY
  • LightningProxies
  • MangoProxy
  • NSocks
  • NiuProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • PROXYSALE
  • PrivateProxy
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
77.245.108.0/23
since Nov 2018
AS35104Mobile7
1 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
77.245.96.0/204,096KZ-KAZTRANSCOM-20070424Qmobile JSC (ORG-OA9-RIPE) · KZALLOCATED PAApr 24, 2007abuse@jusanmobile.kz
└ 77.245.108.0/24256QMOBILE"QMobile" JSCASSIGNED PASep 11, 2017abuse@jusanmobile.kz
via KZ-KAZTRANSCOM-20070424

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