Data as of Nov 10, 2026

72.45.45.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
Providers
26
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

4.8K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • Decodo
  • FastProxy
  • FlashProxy
  • Geonode
  • GonzoProxy
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonBright
  • NovProxy
  • Oxylabs
  • Proxy-Seller
  • ProxyEmpire
  • ProxyWing
  • Proxyma
  • Shifter
  • Thordata
  • ThunderProxy
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
72.45.40.0/21
since Oct 2006
AS11776Residential53
13 always on
Breezeline
via Breezeline

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
72.45.0.0/1816,384ATLANTICBB-JOHNSTOWNBreezeline (ATLAN-19) · USDirect AllocationApr 18, 2005abuse@breezeline.com
└ 72.45.40.0/212,048JST-PA-72-45-40-0Breezeline (ATLAN-19) · USReallocatedOct 29, 2008abuse@breezeline.com
└ 72.45.44.0/221,024PA-JOHNSTOWN-CPEBreezeline (C09557843) · USReassignedMay 25, 2023abuse@breezeline.com
via JST-PA-72-45-40-0

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

72.45.44.0/22

Routing history

Pattern
Stable
First seen
Jun 2017
Current origin since
Jun 2017 · 9.4 yr
Origin networks
1