Data as of Nov 14, 2026

83.221.176.0/24

2 residential-proxy exits · 30 days

Sharq Telekom CJSC

Announcement
No RPKI
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Always-on exits
1
50% of its exits
Providers
23
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

1.2K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • FastProxy
  • FlashProxy
  • GonzoProxy
  • IPRoyal
  • Infatica
  • KocerRoxy
  • LemonBright
  • NodeMaven
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • Shifter
  • Thordata
  • ThunderProxy
  • VibeProxies
  • VitalExclusive

Registrations in this block

The registry's network records over this block, widest first, each 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

Routing timeline

Who has announced 83.221.176.0/22

83.221.176.0/22

Routing history

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