Data as of Nov 18, 2026

137.103.18.0/24

10 residential-proxy exits · 30 days

Breezeline

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

Residential-proxy exits

Proxy exits
10
3.9% of its addresses · 30 days
Always-on exits
4
40% of its exits
Providers
49
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

28K observations

Proxy providers listing exits

  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FastProxy
  • FlashProxy
  • FloppyData
  • GEEKPROXY_TURBO
  • Geonode
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • HideProxy
  • IPFly
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • NovaProxy
  • Oxylabs
  • PROXIWARE_ECO
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • Q2IP
  • RainProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
137.103.0.0/19
since Oct 2016
AS11776Residential199
46 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.16.0/212,048PA-UNIONTOWN-CPEBreezeline (C09648798) · USReassignedJun 12, 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.16.0/21

Routing history

Pattern
Stable
First seen
Mar 2020
Current origin since
Mar 2020 · 6.6 yr
Origin networks
1