Data as of Nov 13, 2026

37.208.40.0/24

9 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
9
3.5% of its addresses · 30 days
Providers
31
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

320 observations

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • ASHBURNPROXIES
  • BestProxy
  • BottingTools
  • CliProxy
  • DataImpulse
  • FastProxy
  • GloryCloud
  • IPFly
  • KindProxy
  • Kookey
  • LUMIPROXY
  • LemonBright
  • NSocks
  • NodeProxy
  • Novada
  • PROXYSALE
  • PROXYSCRAPE
  • PROXY_CC
  • Proxy4U
  • ProxyRack
  • RainProxy
  • RapidProxy
  • RolaProxy
  • Shifter
  • Smartproxy
  • TalorData
  • Thordata
  • ThunderProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
37.208.40.0/21
since Nov 2021
AS41798Residential67
7 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.208.40.0/212,048KZ-TRANSTELECOM-20120328JSC Transtelecom (ORG-TA238-RIPE) · KZALLOCATED PAMar 28, 2012azelkhanov@rambler.ru
└ 37.208.40.0/24256TTC_pool_for_Corp_customersTranstelecom Kazakhstan NetworkASSIGNED PAOct 11, 2012azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20120328

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