Data as of Nov 10, 2026

65.60.167.0/24

5 residential-proxy exits · 30 days

Breezeline

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

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Always-on exits
1
20% of its exits
Providers
36
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

5.1K observations

Proxy providers listing exits

  • B2Proxy
  • BirdProxies
  • Bright Data
  • ByteProxies
  • Byteful
  • CliProxy
  • ColaProxy
  • EnigmaProxy
  • FLEETPROXY
  • FastProxy
  • FloppyData
  • GloryCloud
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Thordata
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
65.60.128.0/17
since Jun 2023
AS11776Residential593
132 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.160.0/212,048OH-COLUMBUS-CPEBreezeline (C02132661) · 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.160.0/21

Routing history

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

History

Handoffs
2