Data as of Nov 14, 2026

5.165.141.0/24

42 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
42
16% of its addresses · 30 days
Always-on exits
2
4.8% of its exits
Providers
73
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

6.6K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • Ake.net
  • BartProxies
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FlashProxy
  • FlexyProxies
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GonzoProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPROCKET_PREMIUM
  • Infatica
  • InfiniteProxies
  • KindProxy
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • MoMoProxy
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYLANE
  • PROXYSCRAPE
  • PrivateProxy
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Q2IP
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • SwiftProxy
  • VantageProxies
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
5.165.128.0/20
since Aug 2012
AS49048Residential836
43 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.165.136.0/212,048ERTH-TVER-PPPOE-5-NETJSC "ER-Telecom Holding" Tver' Branch (ORG-CHTB4-RIPE) · RUASSIGNED PAAug 5, 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.165.140.0/22

Routing history

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