Data as of Nov 14, 2026

37.112.86.0/24

1 residential-proxy exit · 30 days

JSC 'ER-Telecom Holding'

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

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Always-on exits
1
100% of its exits
Providers
20
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

782 observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • FlashProxy
  • GonzoProxy
  • IPOasis
  • Infatica
  • LightningProxies
  • MangoProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • Shifter
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
37.112.64.0/19
since Nov 2014
AS49048Residential1,218
70 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
37.112.0.0/15131,072RU-RAID-20120209JSC "ER-Telecom Holding" (ORG-RA21-RIPE) · RUALLOCATED PAFeb 9, 2012abuse@domru.ru
└ 37.112.80.0/212,048ERTH-TVER-PPPOE-15-NETJSC "ER-Telecom Holding" Tver' Branch (ORG-CHTB4-RIPE) · RUASSIGNED PAOct 31, 2014abuse@domru.ru
via RU-RAID-20120209

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

37.112.84.0/22

Routing history

Pattern
Stable
First seen
Mar 2012
Current origin since
Jul 2017 · 9.3 yr
Origin networks
2
Last change of origin
Jul 2017
Recorded history

History

Handoffs
1