Data as of Nov 18, 2026

134.56.183.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
Providers
32
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

2.0K observations

Proxy providers listing exits

  • 711Proxy
  • ASHBURNPROXIES
  • B2Proxy
  • BottingTools
  • BuyingProxy
  • DataImpulse
  • Datarama
  • EZProxies
  • Evomi
  • FastProxy
  • FlashProxy
  • GloryCloud
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • InfiniteProxies
  • KocerRoxy
  • Kookey
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • Novada
  • PrivateByte
  • Proxy302
  • Proxy4U
  • PuraRoute
  • RainProxy
  • RoamProxy
  • RolaProxy
  • ThunderProxy
  • YumiProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
134.56.160.0/19
since Jun 2018
AS23089Residential244
26 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.128.0/1732,768FISION-BLK2-MIAMI-DHotwire Fision (HF-138) · USReassignedDec 20, 2018abuse@hotwirecommunication.com

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

134.56.182.0/23

Routing history

Pattern
Stable
First seen
Jul 2024
Current origin since
Jul 2024 · 2.3 yr
Origin networks
1