Data as of Nov 13, 2026

83.221.181.0/24

8 residential-proxy exits · 30 days

Sharq Telekom CJSC

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

Residential-proxy exits

Proxy exits
8
3.1% of its addresses · 30 days
Providers
47
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

3.0K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • GeekProxy
  • Geonode
  • GonzoProxy
  • IPOasis
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PSBProxy
  • PrivateByte
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • Proxyma
  • RainProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • VProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • Webshare
  • ZENPROXY_PREMIUM

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.180.0/23512SHARQ-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.180.0/23

83.221.180.0/23

Routing history

Pattern
Stable
First seen
Sep 2008
Current origin since
Sep 2008 · 18 yr
Origin networks
1