Data as of Nov 13, 2026

46.52.134.0/23

3 residential-proxy exits · 30 days

JSC 'ER-Telecom Holding'

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

Residential-proxy exits

Proxy exits
3
0.59% of its addresses · 30 days
Always-on exits
1
33% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
23
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

545 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
46.52.135.0/2412
46.52.134.0/2401

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlashProxy
  • GonzoProxy
  • IPFly
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • Shifter
  • VitalExclusive
  • VitalProxy

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.52.128.0 - 46.52.223.25524,576RU-RAID-20100816JSC "ER-Telecom Holding" (ORG-RA21-RIPE) · RUALLOCATED PAMay 30, 2011abuse@domru.ru
└ 46.52.134.0/23512ENFORTA-MMKEnfortaASSIGNED PASep 16, 2010abuse@domru.ru
via RU-RAID-20100816

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
Oct 2010
Current origin since
Aug 2020 · 6.2 yr
Origin networks
2
Last change of origin
Aug 2020
Recorded history

History

Handoffs
1