Data as of Nov 12, 2026

23.245.136.0/23

4 residential-proxy exits · 30 days

Breezeline

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

Residential-proxy exits

Proxy exits
4
0.78% of its addresses · 30 days
Always-on exits
1
25% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
34
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

2.8K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
23.245.137.0/2411
23.245.136.0/2403

Proxy providers listing exits

  • 2Captcha
  • B2Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • CliProxy
  • ColaProxy
  • DataImpulse
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • FloppyData
  • GonzoProxy
  • IPPeak
  • Infatica
  • LemonBright
  • LudaxProxy
  • NodeMaven
  • NovProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • RainProxy
  • Shifter
  • Thordata
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
23.245.128.0/19
since Jun 2023
AS11776Residential73
17 always on
Breezeline

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

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

Summary

Routing history

Pattern
Stable
First seen
Jun 2023
Current origin since
Jun 2023 · 3.4 yr
Origin networks
1