Data as of Nov 12, 2026

134.56.3.0/24

4 residential-proxy exits · 30 days

Hotwire Communications

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

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Always-on exits
2
50% of its exits
Providers
36
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

3.4K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • ColaProxy
  • EnigmaProxy
  • Evomi
  • FastProxy
  • Geonode
  • GloryCloud
  • IPFly
  • IPPeak
  • InfiniteProxies
  • Kookey
  • LemonBright
  • MoMoProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Proxiware
  • ProxyEmpire
  • ProxyWing
  • Proxyma
  • RainProxy
  • RapidProxy
  • RoamProxy
  • RolaProxy
  • SwiftProxy
  • Thordata
  • VantageProxies
  • VitalExclusive
  • YumiProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
134.56.0.0/18
since Sep 2017
AS23089Residential161
34 always on
Hotwire Communications
via Hotwire Fision

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
134.56.0.0/1665,536HOTWIHotwire Communications (HOTWI) · USDirect AllocationMay 18, 2017abuse@hotwirecommunication.com
└ 134.56.0.0/1665,536FISION-BLK-134-56-0-0-16Hotwire Fision (HF-138) · USReallocatedJun 2, 2017abuse@hotwirecommunication.com
└ 134.56.0.0/198,192FISION-BLK2-MIAMI-AHotwire Fision (HF-138) · USReassignedDec 20, 2018abuse@hotwirecommunication.com

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

134.56.0.0/22

Routing history

Pattern
Stable
First seen
Apr 2024
Current origin since
Apr 2024 · 2.6 yr
Origin networks
1