Data as of Nov 11, 2026

83.69.236.0/24

17 residential-proxy exits · 30 days

Citytelecom LLC

Announcement
this exact prefix
No RPKI
Announced by
Type
Hosting
Risk
50 / 100 · Medium

Residential-proxy exits

Proxy exits
17
6.6% of its addresses · 30 days
Providers
48
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

910 observations

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EVOPROXY
  • EnigmaProxy
  • FlashProxy
  • FlexyProxies
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • IPOasis
  • IPRoyal
  • Infatica
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PSBProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • 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.69.224.0/198,192RU-CITYTELECOM1-20040604Citytelecom LLC (ORG-SO181-RIPE) · RUALLOCATED PAMar 14, 2023abuse@citytelecom.ru
└ 83.69.236.0/24256Hostline-NETunknownASSIGNED PAApr 25, 2019abuse@citytelecom.ru
via RU-CITYTELECOM1-20040604

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
Sep 2013
Current origin since
Sep 2021 · 5.1 yr
Origin networks
2
Last change of origin
Sep 2021
Recorded history

History

Handoffs
1