Data as of Nov 11, 2026

141.136.112.64/28

1 residential-proxy exit · 30 days

JSC 'ER-Telecom Holding'

Announcement
No RPKI
Announced by
Type
Business
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
1
6.3% of its addresses · 30 days
Providers
26
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

35 observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GonzoProxy
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • MangoProxy
  • NodeMaven
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
141.136.112.0/21
since Sep 2019
AS25227Unknown16
1 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
141.136.112.0/212,048RU-RAID-20110630JSC "ER-Telecom Holding" (ORG-RA21-RIPE) · RUALLOCATED PAOct 2, 2026abuse@domru.ru
└ 141.136.112.64/2816NCP_yamskay-ru-netNCP pool for Yamskay str.ASSIGNED PAApr 23, 2014abuse@domru.ru
via RU-RAID-20110630

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

141.136.112.0/24

Routing history

Pattern
Stable
First seen
Nov 2016
Current origin since
Aug 2019 · 7.2 yr
Origin networks
2
Last change of origin
Aug 2019
Recorded history

History

Handoffs
1