LAYER3 INTEL
Get started
Sign in
Data as of Nov 10, 2026

5.167.51.0/24

10 residential-proxy exits · 30 days

JSC 'ER-Telecom Holding'

Announcement
5.167.48.0/21
No RPKI
Announced by
AS57378
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
10
3.9% of its addresses · 30 days
Always-on exits
1
10% of its exits
Providers
37
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

849 observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPPeak
  • Infatica
  • LemonPrime
  • MangoProxy
  • NSocks
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYWING_BASIC
  • PacketStream
  • PrivateByte
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • VantageProxies
  • VitalExclusive
  • VitalProxy

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.48.0/212,048ERTH-ROSTOV-PPPOE-5-NETJSC "ER-Telecom Holding" Rostov-na-Donu Branch (ORG-CHRB2-RIPE) · RUASSIGNED PAAug 22, 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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced 5.167.48.0/21

5.167.48.0/21

Routing history

Pattern
Stable
First seen
Oct 2012
Current origin since
Oct 2012 · 14 yr
Origin networks
1