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

188.134.4.0/22

9 residential-proxy exits · 30 days

JSC 'ER-Telecom Holding'

Announcement
188.134.0.0/19
No RPKI
Announced by
AS41733
Type
Business

Residential-proxy exits

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

Exits seen per day

1.9K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
188.134.4.0/2414
188.134.5.0/2411
188.134.7.0/2403
188.134.6.0/2401

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPPeak
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyStyler
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
188.134.0.0/1732,768RU-RAID-20090427JSC "ER-Telecom Holding" (ORG-RA21-RIPE) · RUALLOCATED PAApr 27, 2009abuse@domru.ru
└ 188.134.0.0/198,192INTERZET-IPOEJSC "INTERZET" Spb branchASSIGNED PAApr 18, 2025abuse@domru.ru
via RU-RAID-20090427

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.134.0.0/19

188.134.0.0/19

Routing history

Pattern
Stable
First seen
Apr 2025
Current origin since
Apr 2025 · 1.6 yr
Origin networks
1