Data as of Nov 21, 2026

159.250.112.0/24

3 residential-proxy exits · 30 days

Breezeline

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

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Always-on exits
1
33% of its exits
Providers
30
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

7.0K observations

Proxy providers listing exits

  • 711Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • DataImpulse
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • HELODATA
  • IPFly
  • IPMUSK
  • Infatica
  • LemonBright
  • PacketStream
  • Proxy-Seller
  • ProxyEmpire
  • ProxyWing
  • PuraRoute
  • RainProxy
  • RapidProxy
  • SwiftProxy
  • Thordata
  • ThunderProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
159.250.96.0/19
since Oct 2020
AS11776Residential78
10 always on
Breezeline

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
159.250.0.0/1665,536ATLAN-19Breezeline (ATLAN-19) · USDirect AllocationSep 3, 2019abuse@breezeline.com
└ 159.250.96.0/198,192FL-MIAMI-NBAY-CPEAtlantic Broadband (C07659202) · USReassignedOct 12, 2020abuse@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

159.250.112.0/21

Routing history

Pattern
Stable
First seen
Oct 2020
Current origin since
Oct 2020 · 6.1 yr
Origin networks
1