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

5.167.140.0/24

11 residential-proxy exits · 30 days

JSC 'ER-Telecom Holding'

Announcement
5.167.128.0/20
No RPKI
Announced by
AS52207
Type
Residential
Risk
0 / 100 · Low
Proxy exits nearby

Residential-proxy exits

Proxy exits
11
4.3% of its addresses · 30 days
Always-on exits
3
27% of its exits
Providers
45
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

9.6K observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonode
  • GloryCloud
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • MangoProxy
  • MarsProxies
  • NSocks
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • StrikeProxy
  • ThunderProxy
  • VitalExclusive

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.136.0/212,048ERTH-TULA-PPPOE-10-NETJSC "ER-Telecom Holding" Tula Branch (ORG-CHTB2-RIPE)ASSIGNED 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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced 5.167.128.0/20

5.167.128.0/20

Routing history

Pattern
Stable
First seen
Sep 2012
Current origin since
Aug 2016 · 10 yr
Origin networks
1