Data as of Nov 10, 2026

5.167.202.0/24

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

Exits seen per day

4.8K observations

Proxy providers listing exits

  • 9Proxy
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FlexyProxies
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
5.167.192.0/20
since Jun 2021
AS51570Residential185
10 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.200.0/212,048ERTH-SPB-PPPOE-24-NETJSC "ER-Telecom Holding" Saint-Petersburg Branch (ORG-CHSB2-RIPE) · RUASSIGNED PAMay 3, 2018abuse@domru.ru

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

5.167.200.0/22

Routing history

Pattern
Stable
First seen
Sep 2012
Current origin since
Jun 2019 · 7.4 yr
Origin networks
5
Last change of origin
Jun 2019
Recorded history

History

Handoffs
4