Data as of Nov 14, 2026

65.60.172.0/24

7 residential-proxy exits · 30 days

Breezeline

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

Residential-proxy exits

Proxy exits
7
2.7% of its addresses · 30 days
Always-on exits
2
29% of its exits
Providers
43
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

8.5K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • ColaProxy
  • DataImpulse
  • EZProxies
  • EnigmaProxy
  • FlashProxy
  • FloppyData
  • Geonode
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NodeMaven
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • RoamProxy
  • RolaProxy
  • Shifter
  • ThunderProxy
  • VitalExclusive
  • YumiProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
65.60.128.0/17
since Jun 2023
AS11776Residential602
114 always on
Breezeline

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
65.60.128.0/1732,768WIDEOPENWESTBreezeline (ATLAN-19) · USDirect AllocationNov 1, 2002abuse@breezeline.com
└ 65.60.172.0/23512OH-COLUMBUS-CPEBreezeline (C02132555) · USReassignedJan 14, 2009abuse@breezeline.com
via WIDEOPENWEST

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

65.60.172.0/23

Routing history

Pattern
Rotating
First seen
May 2005
Current origin since
Sep 2022 · 4.2 yr
Origin networks
4
Last change of origin
Sep 2022
Recorded history

History

Handoffs
4