Data as of Nov 14, 2026

84.235.36.0/22

2 residential-proxy exits · 30 days

Saudi Telecom Company JSC

Announcement
this exact prefix
RPKI valid
Announced by
Type
Business
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
2
0.20% of its addresses · 30 days
Spread
1 of 4
/24s with at least one exit
Providers
29
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

77 observations

Proxy providers listing exits

  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • GloryCloud
  • GonzoProxy
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • LemonBright
  • NextProxy
  • NiuProxy
  • Novada
  • Oxylabs
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • RapidProxy
  • Shifter
  • SwiftProxy
  • Thordata
  • ThunderProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
84.235.0.0/18
since Aug 2005
AS25019Residential19
1 always on
Saudi Telecom Company JSC
84.235.0.0/17
since Jul 2012
AS39386Business25
1 always on
Saudi Telecom Company 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
84.235.0.0/1732,768SA-STC-20040616Saudi Telecom Company JSC (ORG-SSTC1-RIPE) · SAALLOCATED PAJun 16, 2004registry@stc.com.sa
└ 84.235.36.0 - 84.235.40.2551,280SAUDINET_DIADIA customersASSIGNED PANov 9, 2014registry@stc.com.sa
via SA-STC-20040616

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
May 2014
Current origin since
May 2014 · 13 yr
Origin networks
1