Data as of Nov 17, 2026

137.103.152.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
25
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

2.7K observations

Proxy providers listing exits

  • Ake.net
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • FlashProxy
  • FloppyData
  • Geonode
  • GloryCloud
  • IPPeak
  • KocerRoxy
  • LemonBright
  • MoMoProxy
  • NovProxy
  • Oxylabs
  • Proxiware
  • Proxy302
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • Thordata
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
137.103.128.0/19
since Jan 2017
AS11776Residential176
30 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.152.0/221,024MD-CUMBERLAND-CPEBreezeline (C10813236) · USReassignedApr 11, 2024abuse@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.152.0/22

Routing history

Pattern
Stable
First seen
Jul 2020
Current origin since
Jul 2020 · 6.4 yr
Origin networks
1