LAYER3 INTEL
Get started
Sign in
Data as of Nov 11, 2026

46.29.8.0/21

89 residential-proxy exits · 30 days

TeleMaks Ltd

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

Residential-proxy exits

Proxy exits
89
4.3% of its addresses · 30 days
Always-on exits
4
4.5% of its exits
Spread
8 of 8
/24s with at least one exit
Providers
69
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

28K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
46.29.12.0/24126
46.29.13.0/24125
46.29.9.0/24113
46.29.8.0/2417
46.29.15.0/2406
46.29.14.0/2405
46.29.10.0/2404
46.29.11.0/2404

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Datarama
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NSocks
  • NextProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • ResiProxies
  • RolaProxy
  • Shifter
  • Smartproxy
  • Thordata
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • YumiProxy
  • 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.29.8.0/212,048RU-TELEMAKS-20100730TeleMaks Ltd (ORG-TL175-RIPE) · RUALLOCATED PAJul 30, 2010abuse@hitel.ru
└ 46.29.8.0/2732RU-TELEMAKS-20101126TeleMaks CoreASSIGNED PANov 29, 2010abuse@hitel.ru
via RU-TELEMAKS-20100730
└ 46.29.8.32 - 46.29.8.255224RU-TELEMAKS-20140621-1TeleMaks PtP static routing clients.ASSIGNED PAJun 21, 2014abuse@hitel.ru
via RU-TELEMAKS-20100730
└ 46.29.9.0/24256RU-TELEMAKS-20140621-2TeleMaks PtP static routing clients.ASSIGNED PAJun 21, 2014abuse@hitel.ru
via RU-TELEMAKS-20100730
└ 46.29.10.0/24256RU-TELEMAKS-20140621-3TeleMaks PtP static routing clients.ASSIGNED PAJun 21, 2014abuse@hitel.ru
via RU-TELEMAKS-20100730
└ 46.29.11.0/24256RU-TELEMAKS-20140621-4TeleMaks PtP static routing clients.ASSIGNED PAJun 21, 2014abuse@hitel.ru
via RU-TELEMAKS-20100730
└ 46.29.12.0/24256RU-TELEMAKS-20110505TeleMaks PPP clientsASSIGNED PAMay 5, 2011abuse@hitel.ru
via RU-TELEMAKS-20100730
└ 46.29.13.0/24256RU-TELEMAKS-20130206-1TeleMaks PPP clientsASSIGNED PAFeb 6, 2013abuse@hitel.ru
via RU-TELEMAKS-20100730
└ 46.29.14.0/24256RU-TELEMAKS-20130206-2TeleMaks SR networkASSIGNED PAFeb 6, 2013abuse@hitel.ru
via RU-TELEMAKS-20100730
└ 46.29.15.0/24256RU-TELEMAKS-20201119-7unknownASSIGNED PANov 19, 2020abuse@hitel.ru

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Oct 2011
Current origin since
Oct 2011 · 15 yr
Origin networks
1