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

188.234.76.0/22

5 residential-proxy exits · 30 days

JSC 'ER-Telecom Holding'

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

Residential-proxy exits

Proxy exits
5
0.49% of its addresses · 30 days
Always-on exits
2
40% of its exits
Spread
2 of 4
/24s with at least one exit
Providers
34
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

6.1K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
188.234.79.0/2424
188.234.76.0/2401

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • GonzoProxy
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • NovaProxy
  • Novada
  • Oxylabs
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VantageProxies

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
188.232.0.0/14262,144RU-RAID-20110126JSC "ER-Telecom Holding" (ORG-RA21-RIPE) · RUALLOCATED PAJan 26, 2011abuse@domru.ru
└ 188.234.72.0/212,048ERTH-OMSK-PPPOE-31-NETJSC "ER-Telecom Holding" Omsk Branch (ORG-CHOB1-RIPE) · RUASSIGNED PADec 26, 2014abuse@domru.ru
via RU-RAID-20110126

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 188.234.72.0/21

188.234.72.0/21

Routing history

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

History

Handoffs
1