Data as of Nov 10, 2026

5.166.46.0/24

7 residential-proxy exits · 30 days

JSC 'ER-Telecom Holding'

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

Residential-proxy exits

Proxy exits
7
2.7% of its addresses · 30 days
Providers
37
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

1.7K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FlashProxy
  • FloppyData
  • GSocks
  • GonzoProxy
  • HydraProxy
  • Infatica
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • Proxyma
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
5.166.32.0/19
since Oct 2013
AS51604Residential1,291
64 always on
JSC "ER-Telecom Holding"

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
5.164.0.0/14262,144RU-RAID-20120725JSC "ER-Telecom Holding" (ORG-RA21-RIPE) · RUALLOCATED PAJul 25, 2012abuse@domru.ru
└ 5.166.40.0/212,048ERTH-EKAT-PPPOE-35-NETJSC "ER-Telecom Holding" Yekaterinburg Branch (ORG-CHYB1-RIPE) · RUASSIGNED PAAug 12, 2012abuse@domru.ru

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

5.166.44.0/22

Routing history

Pattern
Stable
First seen
Aug 2012
Current origin since
Apr 2014 · 13 yr
Origin networks
2
Last change of origin
Apr 2014
Recorded history

History

Handoffs
1