Data as of Nov 18, 2026

79.122.212.0/22

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.29% of its addresses · 30 days
Always-on exits
1
33% of its exits
Spread
3 of 4
/24s with at least one exit
Providers
25
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

2.0K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
79.122.212.0/2411
79.122.214.0/2401
79.122.215.0/2401

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • FlashProxy
  • GonzoProxy
  • IPFly
  • IPOasis
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • Shifter
  • Smartproxy
  • 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
79.122.128.0/1732,768RU-RAID-20070726JSC "ER-Telecom Holding" (ORG-RA21-RIPE) · RUALLOCATED PAJul 26, 2007abuse@domru.ru
└ 79.122.212.0/24256ENFORTA-PRMEnfortaASSIGNED PAApr 19, 2017abuse@domru.ru
via RU-RAID-20070726
└ 79.122.213.0/24256ENFORTA-PRMEnfortaASSIGNED PAApr 19, 2017abuse@domru.ru
via RU-RAID-20070726
└ 79.122.214.0/24256ENFORTA-PRMEnfortaASSIGNED PAApr 19, 2017abuse@domru.ru
via RU-RAID-20070726
└ 79.122.215.0/304ENFORTA-PRMEnfortaASSIGNED PAApr 19, 2017abuse@domru.ru
via RU-RAID-20070726
└ 79.122.215.4/304ENFORTA-PRMEnfortaASSIGNED PAApr 19, 2017abuse@domru.ru
via RU-RAID-20070726
└ 79.122.215.8/304ENFORTA-PRM-BereznikiEnfortaASSIGNED PAApr 19, 2017abuse@domru.ru
via RU-RAID-20070726
└ 79.122.215.12 - 79.122.215.255244ENFORTA-PRMEnfortaASSIGNED PAApr 19, 2017abuse@domru.ru
via RU-RAID-20070726

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
Jan 2009
Current origin since
Jan 2009 · 18 yr
Origin networks
1