Data as of Nov 18, 2026

37.17.180.0/24

4 residential-proxy exits · 30 days

JSC Transtelecom

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

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Always-on exits
2
50% of its exits
Providers
31
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

2.9K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • EnigmaProxy
  • FlashProxy
  • GSocks
  • GonzoProxy
  • IPOasis
  • Infatica
  • KocerRoxy
  • LemonBright
  • MangoProxy
  • NSocks
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • Shifter
  • Smartproxy
  • Thordata
  • VibeProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
37.17.176.0/21
since Feb 2012
AS41798Residential70
12 always on
JSC Transtelecom

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
37.17.176.0/212,048KZ-TRANSTELECOM-20111219JSC Transtelecom (ORG-TA238-RIPE) · KZALLOCATED PADec 19, 2011azelkhanov@rambler.ru
└ 37.17.180.0/24256Nat_AlmatyTranstelecom Kazakhstan NetworkASSIGNED PAMar 12, 2012azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20111219

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

Summary

Routing history

Pattern
Stable
First seen
Dec 2011
Current origin since
Jan 2023 · 3.8 yr
Origin networks
1