Data as of Nov 10, 2026

5.167.111.0/24

3 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
3
1.2% of its addresses · 30 days
Providers
19
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

114 observations

Proxy providers listing exits

  • BirdProxies
  • ByteProxies
  • Byteful
  • EnigmaProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • Infatica
  • LemonLabs
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
5.167.96.0/20
since Sep 2012
AS49048Residential298
35 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.167.104.0/212,048ERTH-TVER-PPPOE-7-NETJSC "ER-Telecom Holding" Tver' Branch (ORG-CHTB4-RIPE) · RUASSIGNED PAAug 27, 2012abuse@domru.ru
via RU-RAID-20120725

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

5.167.108.0/22

Routing history

Pattern
Stable
First seen
Sep 2012
Current origin since
Jul 2017 · 9.3 yr
Origin networks
1