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

83.221.176.0/22

9 residential-proxy exits · 30 days

Sharq Telekom CJSC

Announcement
this exact prefix
No RPKI
Announced by
AS31203
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
9
0.88% of its addresses · 30 days
Always-on exits
3
33% of its exits
Spread
3 of 4
/24s with at least one exit
Providers
40
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

4.0K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
83.221.179.0/2424
83.221.176.0/2412
83.221.178.0/2403

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • Geonode
  • GonzoProxy
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • Novada
  • Oxylabs
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VibeProxies
  • VitalExclusive
  • VitalProxy

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
83.221.166.0 - 83.221.182.2554,352UZ-SHARQ-TELEKOM-20040415Sharq Telekom CJSC (ORG-STC7-RIPE) · UZALLOCATED PAAug 17, 2026odeberdiev@st.uz
└ 83.221.176.0/221,024SHARQ-TELEKOMunknownASSIGNED PAJul 24, 2025odeberdiev@st.uz
via UZ-SHARQ-TELEKOM-20040415

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

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Feb 2008
Current origin since
Feb 2008 · 19 yr
Origin networks
1