Data as of Nov 11, 2026

170.103.32.0/23

3 residential-proxy exits · 30 days

Breezeline

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

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

Exits seen per day

1.2K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
170.103.33.0/2402
170.103.32.0/2401

Proxy providers listing exits

  • Ake.net
  • BottingTools
  • CliProxy
  • Decodo
  • EnigmaProxy
  • FastProxy
  • GloryCloud
  • IPFly
  • IPMUSK
  • LudaxProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • Proxiware
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • VantageProxies
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
170.103.32.0/19
since Aug 2023
AS11776Residential55
8 always on
Breezeline

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
170.103.0.0/1816,384ATLAN-19Breezeline (ATLAN-19) · USDirect AllocationMay 23, 2023abuse@breezeline.com
└ 170.103.32.0/23512FL-MIAMI-NBAY-CPEBreezeline (C10169903) · USReassignedSep 19, 2023abuse@breezeline.com
via ATLAN-19

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
Sep 2023
Current origin since
Sep 2023 · 3.2 yr
Origin networks
1