Data as of Nov 11, 2026

46.28.90.0/24

8 residential-proxy exits · 30 days

JSC 'ER-Telecom Holding'

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

Residential-proxy exits

Proxy exits
8
3.1% of its addresses · 30 days
Always-on exits
1
13% of its exits
Providers
36
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

1.8K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • IPOasis
  • IPPeak
  • Infatica
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • RainProxy
  • Shifter
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
46.28.88.0/21
since Oct 2015
AS25227Unknown34
4 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
46.28.88.0/212,048RU-RAID-20100721JSC "ER-Telecom Holding" (ORG-RA21-RIPE) · RUALLOCATED PAOct 1, 2026abuse@domru.ru
└ 46.28.90.0/24256Avantel-MoscowAvantel Static IP blockASSIGNED PASep 24, 2015abuse@domru.ru
via RU-RAID-20100721

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

Covering aggregate above, the prefix's own history below

46.28.88.0/22

Routing history

Pattern
Stable
First seen
May 2011
Current origin since
Oct 2015 · 11 yr
Origin networks
2
Last change of origin
Oct 2015
Recorded history

History

Handoffs
1