Data as of Nov 14, 2026

37.208.40.0/21

71 residential-proxy exits · 30 days

JSC Transtelecom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
71
3.5% of its addresses · 30 days
Always-on exits
9
13% of its exits
Spread
7 of 8
/24s with at least one exit
Providers
92
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

34K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • 9Proxy
  • APROXY
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CROXY
  • CliProxy
  • DataImpulse
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LUMIPROXY
  • LemonBright
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NSocks
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYLANE
  • PROXYON
  • PROXYSALE
  • PROXYSCRAPE
  • PROXY_CC
  • PacketStream
  • PrivateProxy
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • ResiProxies
  • RolaProxy
  • SIMPLYNODE
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • StrikeProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • Webshare
  • ZENPROXY_PREMIUM

Announcements

Nesting

More-specifics by size

Sized by addresses, colored by each announcement's type. Click a tile with children to zoom in, a leaf to open it.
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
37.208.40.0/24
since Dec 2014
AS41798Residential10JSC Transtelecom
37.208.41.0/24
since Jan 2020
AS41798Residential9
2 always on
JSC Transtelecom
37.208.42.0/24
since Dec 2014
AS41798Residential9
1 always on
JSC Transtelecom
37.208.43.0/24
since Mar 2013
AS41798ResidentialJSC Transtelecom
37.208.44.0/24
since May 2012
AS41798Residential11
3 always on
JSC Transtelecom
37.208.45.0/24
since Dec 2014
AS41798Residential11JSC Transtelecom
37.208.46.0/24
since Dec 2014
AS41798Residential14
2 always on
JSC Transtelecom
37.208.47.0/24
since Dec 2014
AS41798Residential7
1 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
└ 37.208.41.0/24256TTC_pool_for_Corp_customersunknownASSIGNED PADec 11, 2018azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20120328
└ 37.208.42.0/24256TTC_pool_for_Corp_customersTranstelecom Kazakhstan NetworkASSIGNED PAOct 16, 2012azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20120328
└ 37.208.43.0/24256COD_cloud_TTCunknownASSIGNED PAMar 15, 2019azelkhanov@rambler.ru
via KZ-TRANSTELECOM-20120328
└ 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

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Apr 2012
Current origin since
Nov 2021 · 5.0 yr
Origin networks
1