Data as of Nov 13, 2026

37.34.168.0/22

1 residential-proxy exit · 30 days

Mobile Telecommunications Company K.S.C.P.

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

Residential-proxy exits

Proxy exits
1
0.10% of its addresses · 30 days
Always-on exits
1
100% of its exits
Spread
1 of 4
/24s with at least one exit
Providers
20
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

937 observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • BottingTools
  • ByteProxies
  • Byteful
  • Decodo
  • FlashProxy
  • Geonode
  • InfiniteProxies
  • LemonBright
  • NSocks
  • Novada
  • Oxylabs
  • Proxy-Cheap
  • ProxyEmpire
  • ProxyRack
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
37.34.160.0/20
since Aug 2015
AS42961Mobile48
3 always on
Mobile Telecommunications Company K.S.C.P.
via Zain KW
37.34.160.0/19
since Feb 2012
AS42961Mobile216
16 always on
Mobile Telecommunications Company K.S.C.P.
via Zain KW
37.34.128.0/18
since Feb 2012
AS42961Mobile248
20 always on
Mobile Telecommunications Company K.S.C.P.

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
37.34.128.0/1732,768KW-MTC-20120103Mobile Telecommunications Company K.S.C.P. (ORG-MTC1-RIPE) · KWALLOCATED PAJan 3, 2012abuse@kw.zain.com
└ 37.34.136.0 - 37.34.255.25530,720ZAIN-KWZain KWSUB-ALLOCATED PANov 21, 2021abuse@kw.zain.com
via KW-MTC-20120103

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
Apr 2021
Current origin since
Apr 2021 · 5.6 yr
Origin networks
1