Data as of Nov 14, 2026

37.208.47.0/24

7 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
7
2.7% of its addresses · 30 days
Always-on exits
1
14% of its exits
Providers
41
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

1.9K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • GSocks
  • GonzoProxy
  • IPOasis
  • IPROCKET_PREMIUM
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • Oxylabs
  • PROXYLANE
  • PROXYON
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • Proxyma
  • RainProxy
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VibeProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
37.208.40.0/21
since Nov 2021
AS41798Residential71
9 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