Data as of Nov 12, 2026

37.208.45.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
42
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

849 observations

Proxy providers listing exits

  • 2Captcha
  • BartProxies
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HydraProxy
  • IPOasis
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LUMIPROXY
  • MangoProxy
  • NSocks
  • NiuProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • Proxyma
  • RainProxy
  • ResiProxies
  • Shifter
  • Smartproxy
  • Thordata
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
37.208.40.0/21
since Nov 2021
AS41798Residential67
6 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.44.0/221,024TTC_pool_for_Corp_customersunknownASSIGNED PAMar 15, 2019azelkhanov@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