Data as of Nov 21, 2026

104.129.204.0/23

5 residential-proxy exits · 30 days

Zscaler, Inc.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Corporate gateway

Residential-proxy exits

Proxy exits
5
0.98% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
8
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

31 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
104.129.205.0/2404
104.129.204.0/2401

Proxy providers listing exits

  • AnyIP
  • EnigmaProxy
  • FloppyData
  • RoamProxy
  • Shifter
  • VantageProxies
  • YumiProxy
  • ZENPROXY_LITE

Operators, sellers and brokers

Corporate gateways

NameParentIn 104.129.204.0/23/24s
Zscaler
512100%
2

Announcements

More specific

Announcements inside

PrefixOriginTypeOperatorProxy exitsHolderRPKI
104.129.204.0/24
since Jun 2015
AS22616Corporate gatewayCorporate gatewaysoperated by Zscaler1Zscaler, Inc.
104.129.205.0/24
since Jun 2015
AS22616Corporate gatewayCorporate gatewaysoperated by Zscaler4Zscaler, Inc.

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
104.129.192.0/204,096ZSCALER-CLOUDZscaler, Inc. (ZSCAL) · USDirect AllocationJun 18, 2014poc-abuse@zscaler.com
└ 104.129.204.0/24256ZSCALER-ATL2Zscaler, Inc. (C05687140) · USReassignedApr 17, 2015poc-abuse@zscaler.com
via ZSCALER-CLOUD
└ 104.129.205.0/24256ZSCALER-ATL2Zscaler, Inc. (C05687144) · USReassignedApr 17, 2015poc-abuse@zscaler.com
via ZSCALER-CLOUD

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

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Jun 2015
Current origin since
Apr 2019 · 7.6 yr
Origin networks
1