Data as of Nov 14, 2026

23.245.36.0/23

5 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
5
0.98% of its addresses · 30 days
Always-on exits
1
20% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
25
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

2.5K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
23.245.36.0/2412
23.245.37.0/2403

Proxy providers listing exits

  • Ake.net
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • FastProxy
  • FloppyData
  • GloryCloud
  • IPPeak
  • Infatica
  • KocerRoxy
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NovProxy
  • Oxylabs
  • Proxiware
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • Shifter
  • ThunderProxy
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
23.245.32.0/20
since Jun 2022
AS11776Residential63
10 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.36.0/23512PA-BRADFORD-CPEBreezeline (C09092205) · USReassignedDec 20, 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

Summary

Routing history

Pattern
Stable
First seen
Dec 2022
Current origin since
Dec 2022 · 3.9 yr
Origin networks
1