Data as of Nov 13, 2026

176.32.128.0/28

1 residential-proxy exit · 30 days

CityTelekom Ltd.

Announcement
RPKI valid
Announced by
Type
Business
Risk
0 / 100 · Low
Proxy exits nearby

Residential-proxy exits

Proxy exits
1
6.3% of its addresses · 30 days
Always-on exits
3
100% of its exits
Providers
44
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

188 observations

Proxy providers listing exits

  • 2Captcha
  • 9Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CliProxy
  • Datarama
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • Infatica
  • InfiniteProxies
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Novada
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyStyler
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Shifter
  • Thordata
  • ThunderProxy
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
176.32.128.0/19
since Dec 2012
AS56791Residential5,589
8 always on
CityTelekom Ltd.

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
176.32.128.0/198,192RU-CITYTELEKOM-20110523CityTelekom Ltd. (ORG-CL576-RIPE) · RUALLOCATED PAMay 26, 2020abuse-ct@soyka.su
└ 176.32.128.0/2816CT-ARMAVIR-INFRAunknownASSIGNED PAOct 29, 2020abuse-ct@soyka.su
via RU-CITYTELEKOM-20110523

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

176.32.128.0/23

Routing history

Pattern
Stable
First seen
Dec 2018
Current origin since
Dec 2018 · 7.9 yr
Origin networks
1