Data as of Nov 22, 2026

137.103.50.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
2
50% of its exits
Providers
47
selling exits here
Oct 23, 2026 – Nov 21, 2026

Exits seen per day

12K observations

Proxy providers listing exits

  • 711Proxy
  • AETHYN_ELITE
  • B2Proxy
  • BirdProxies
  • BottingTools
  • Byteful
  • EZProxies
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FastProxy
  • FloppyData
  • GEEKPROXY_TURBO
  • GSocks
  • GloryCloud
  • HASDATA
  • IP2WORLD
  • IPFly
  • IPMUSK
  • IPPeak
  • Infatica
  • LudaxProxy
  • MoMoProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • PROXIWARE_ECO
  • PROXYLANE
  • PROXYSCRAPE
  • PYPROXY
  • ProxyEmpire
  • ProxyWing
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • RoamProxy
  • RolaProxy
  • SOTAPROXY
  • Shifter
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • WealthProxies
  • YumiProxy
  • ZENPROXY_LITE

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.48.0/221,024FL-MIAMI-NBAY-CPEBreezeline (C10506007) · USReassignedDec 6, 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

Who has announced 137.103.50.0/23

137.103.50.0/23

Routing history

Pattern
Stable
First seen
Jan 2024
Current origin since
Jan 2024 · 2.8 yr
Origin networks
1