Data as of Nov 12, 2026

46.29.13.0/24

24 residential-proxy exits · 30 days

TeleMaks Ltd

Announcement
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
24
9.4% of its addresses · 30 days
Always-on exits
1
4.2% of its exits
Providers
47
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

12K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • IPFly
  • IPOasis
  • IPPeak
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Registrations in this block

The registry's network records over this block, widest first, each 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.13.0/24256RU-TELEMAKS-20130206-1TeleMaks PPP clientsASSIGNED PAFeb 6, 2013abuse@hitel.ru
via RU-TELEMAKS-20100730

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 46.29.8.0/21

46.29.8.0/21

Routing history

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