Data as of Nov 11, 2026

46.255.68.0/23

4 residential-proxy exits · 30 days

Sharq Telekom CJSC

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

Residential-proxy exits

Proxy exits
4
0.78% of its addresses · 30 days
Spread
1 of 2
/24s with at least one exit
Providers
27
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

836 observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • B2Proxy
  • BlurPath
  • BottingTools
  • CliProxy
  • DataImpulse
  • EVOPROXY
  • EZProxies
  • FastProxy
  • GloryCloud
  • IPFly
  • IPPeak
  • KindProxy
  • Kookey
  • LudaxProxy
  • MoMoProxy
  • NovProxy
  • Proxy4U
  • PuraRoute
  • RainProxy
  • RapidProxy
  • RoamProxy
  • RolaProxy
  • StrikeProxy
  • SwiftProxy
  • TalorData

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
46.255.64.0/212,048UZ-SHARQ-TELEKOM-20101227Sharq Telekom CJSC (ORG-STC7-RIPE) · UZALLOCATED PADec 27, 2010odeberdiev@st.uz
└ 46.255.68.0/23512SHARQ-TELEKOMunknownASSIGNED PAMar 28, 2019odeberdiev@st.uz
via UZ-SHARQ-TELEKOM-20101227

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 this prefix

Summary

Routing history

Pattern
Stable
First seen
Jun 2018
Current origin since
Jun 2018 · 8.4 yr
Origin networks
1