Data as of Nov 15, 2026

23.244.103.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
37
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

6.3K observations

Proxy providers listing exits

  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • ColaProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • FloppyData
  • GloryCloud
  • GonzoProxy
  • IPFly
  • Infatica
  • LudaxProxy
  • MoMoProxy
  • NSocks
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • RainProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • WealthProxies
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
23.244.0.0/17
since Aug 2022
AS11776Residential354
77 always on
Breezeline

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
23.244.0.0/15131,072ATLAN-19Breezeline (ATLAN-19) · USDirect AllocationDec 30, 2020abuse@breezeline.com
└ 23.244.102.0/23512OH-CLEVELAND-CPEBreezeline (C08820453) · USReassignedAug 16, 2022abuse@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

23.244.102.0/23

Routing history

Pattern
Stable
First seen
Sep 2022
Current origin since
Sep 2022 · 4.2 yr
Origin networks
1