Data as of Nov 13, 2026

176.212.0.0/22

2 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
2
0.20% of its addresses · 30 days
Spread
2 of 4
/24s with at least one exit
Providers
20
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

562 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
176.212.0.0/2401
176.212.1.0/2401

Proxy providers listing exits

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

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
176.212.0.0/20
since Sep 2015
AS41727Residential117JSC "ER-Telecom Holding"

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
176.212.0.0/14262,144RU-RAID-20110928JSC "ER-Telecom Holding" (ORG-RA21-RIPE) · RUALLOCATED PASep 28, 2011abuse@domru.ru
└ 176.212.0.0/204,096ERTH-KIROV-176-212-0JSC "ER-Telecom Holding" Kirov Branch (ORG-CHKB3-RIPE) · RUASSIGNED PAJul 9, 2026abuse@domru.ru
via RU-RAID-20110928

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

Summary

Routing history

Pattern
Stable
First seen
Oct 2011
Current origin since
Dec 2017 · 8.9 yr
Origin networks
1