Data as of Nov 15, 2026

170.103.50.0/23

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

Exits seen per day

1.9K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
170.103.51.0/2414
170.103.50.0/2404

Proxy providers listing exits

  • Ake.net
  • AnyIP
  • BottingTools
  • CliProxy
  • Decodo
  • EnigmaProxy
  • FastProxy
  • FloppyData
  • GloryCloud
  • Infatica
  • KocerRoxy
  • LemonBright
  • LudaxProxy
  • MoMoProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • ProxyEmpire
  • Q2IP
  • RainProxy
  • Shifter
  • ThunderProxy
  • VantageProxies

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
170.103.32.0/19
since Aug 2023
AS11776Residential59
9 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.50.0/23512FL-MIAMI-NBAY-CPEBreezeline (C10482064) · USReassignedNov 30, 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
Nov 2023
Current origin since
Nov 2023 · 3.0 yr
Origin networks
1