Data as of Nov 14, 2026

205.220.28.0/23

3 residential-proxy exits · 30 days

Zscaler, Inc.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Corporate gateway
Risk
20 / 100 · Low

Residential-proxy exits

Proxy exits
3
0.59% of its addresses · 30 days
Spread
1 of 2
/24s with at least one exit
Providers
4
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

5 observations

Proxy providers listing exits

  • AnyIP
  • BottingTools
  • FLEETPROXY
  • FloppyData

Operators, sellers and brokers

Corporate gateways

NameParentIn 205.220.28.0/23/24s
Zscaler
512100%
2

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
205.220.0.0/17
since Dec 2024
AS22616Corporate gateway33Zscaler, 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
205.220.0.0/1732,768ZSCALZscaler, Inc. (ZSCAL) · USDirect AllocationNov 27, 2024poc-abuse@zscaler.com
└ 205.220.28.0/23512ZSCALER-MIA4Zscaler, Inc. (C11305639) · USReassignedAug 5, 2025poc-abuse@zscaler.com
via ZSCAL

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Feb 2026
Current origin since
Feb 2026 · 9 mo
Origin networks
1