Data as of Nov 17, 2026

84.244.50.0/24

5 residential-proxy exits · 30 days

JSC 'ER-Telecom Holding'

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

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Always-on exits
3
60% of its exits
Providers
45
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

5.8K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • GeekProxy
  • Geonode
  • GonzoProxy
  • IPFly
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LightningProxies
  • MangoProxy
  • Maskify
  • NextProxy
  • NodeMaven
  • PSBProxy
  • PrivateByte
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Q2IP
  • Shifter
  • SpyderProxy
  • Thordata
  • ThunderProxy
  • TrustProxy
  • VitalExclusive
  • VitalProxy

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
84.244.0.0/1816,384RU-RAID-20100504JSC "ER-Telecom Holding" (ORG-RA21-RIPE) · RUALLOCATED PAMay 4, 2023abuse@domru.ru
└ 84.244.48.0/221,024IRKNET-NET-5irknet.ruASSIGNED PANov 28, 2012abuse@domru.ru
via RU-RAID-20100504

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 84.244.48.0/20

84.244.48.0/20

Routing history

Pattern
Stable
First seen
Feb 2011
Current origin since
Feb 2011 · 16 yr
Origin networks
1