Data as of Nov 18, 2026

185.44.236.0/23

14 residential-proxy exits · 30 days

Gorodskie Telekommunikatsionnye Sistemy LLC

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

Residential-proxy exits

Proxy exits
14
2.7% of its addresses · 30 days
Always-on exits
3
21% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
61
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

7.0K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
185.44.236.0/2438
185.44.237.0/2406

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FastProxy
  • FlashProxy
  • FloppyData
  • GEEKPROXY_TURBO
  • GSocks
  • Geonode
  • GonzoProxy
  • HASDATA
  • HELODATA
  • IPFly
  • IPOasis
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • Infatica
  • InfiniteProxies
  • LOKIPROXY
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXYLANE
  • PROXYSCRAPE
  • PYPROXY
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • Shifter
  • Thordata
  • VantageProxies
  • VitalExclusive
  • VitalProxy
  • YumiProxy
  • ZENPROXY_LITE

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
185.44.236.0/221,024RU-GTSYSTEMS-20140113Gorodskie Telekommunikatsionnye Sistemy LLC (ORG-GTSL7-RIPE) · RUALLOCATED PAOct 28, 2019lir-adm@kgts.su
└ 185.44.236.0/23512GTSYSTEMS-NETGorodskie Telekommunikatsionnye Sistemy LLCASSIGNED PAJan 13, 2014lir-adm@kgts.su
via RU-GTSYSTEMS-20140113

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
Jan 2014
Current origin since
Jan 2014 · 13 yr
Origin networks
1