Data as of Nov 12, 2026

170.103.58.0/23

4 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
4
0.78% of its addresses · 30 days
Always-on exits
1
25% of its exits
Spread
1 of 2
/24s with at least one exit
Providers
33
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

11K observations

Proxy providers listing exits

  • 9Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • ColaProxy
  • DataImpulse
  • Decodo
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • GloryCloud
  • GonzoProxy
  • HideProxy
  • Infatica
  • InfiniteProxies
  • NSocks
  • Novada
  • Oxylabs
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • Shifter
  • Thordata
  • ThunderProxy
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
170.103.32.0/19
since Aug 2023
AS11776Residential57
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.58.0/23512FL-WESTPALMBEACH-CPEBreezeline (C10633172) · USReassignedJan 11, 2024abuse@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
Jan 2024
Current origin since
Jan 2024 · 2.9 yr
Origin networks
1