Data as of Nov 17, 2026

137.103.237.0/24

4 residential-proxy exits · 30 days

Breezeline

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

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Always-on exits
1
25% of its exits
Providers
36
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

2.7K observations

Proxy providers listing exits

  • Ake.net
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • ColaProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • Geonode
  • GhostConnect
  • GloryCloud
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LudaxProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • PYPROXY
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • Q2IP
  • RainProxy
  • Thordata
  • VitalExclusive
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
137.103.224.0/19
since Jan 2020
AS11776Residential85
21 always on
Breezeline

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
137.103.0.0/1665,536ATLANTICBBBreezeline (ATLAN-19) · USDirect AllocationOct 10, 2016abuse@breezeline.com
└ 137.103.236.0/23512FL-WESTPALMBEACH-CPEBreezeline (C09196239) · USReassignedFeb 10, 2023abuse@breezeline.com
via ATLANTICBB

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

137.103.236.0/23

Routing history

Pattern
Stable
First seen
Nov 2022
Current origin since
Nov 2022 · 4.0 yr
Origin networks
1