Data as of Nov 10, 2026

46.196.4.0/22

15 residential-proxy exits · 30 days

Turksat Uydu Haberlesme Kablo TV ve Isletme A.S.

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

Residential-proxy exits

Proxy exits
15
1.5% of its addresses · 30 days
Always-on exits
1
6.7% of its exits
Spread
3 of 4
/24s with at least one exit
Providers
67
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

5.7K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
46.196.5.0/2414
46.196.4.0/24010
46.196.7.0/2401

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 711Proxy
  • Ake.net
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LemonBright
  • LemonPrime
  • MangoProxy
  • MoMoProxy
  • NextProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • Proxies.fo
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • RoamProxy
  • Shifter
  • Smartproxy
  • SwiftProxy
  • Thordata
  • VantageProxies
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

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
46.196.0.0/15131,072TR-TURKSAT-UYDU-KABLO-20101220Turksat Uydu Haberlesme Kablo TV ve Isletme A.S. (ORG-TUHV1-RIPE) · TRALLOCATED PADec 20, 2010abuse@turksat.com.tr
└ 46.196.0.0/1665,536TURKSAT-NETTurksat KabloASSIGNED PADec 20, 2010abuse@turksat.com.tr
via TR-TURKSAT-UYDU-KABLO-20101220

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 2011
Current origin since
Apr 2011 · 16 yr
Origin networks
1