Data as of Nov 16, 2026

65.60.175.0/24

3 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
3
1.2% of its addresses · 30 days
Always-on exits
1
33% of its exits
Providers
30
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

1.9K observations

Proxy providers listing exits

  • Ake.net
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • ColaProxy
  • EnigmaProxy
  • FastProxy
  • FlexyProxies
  • FloppyData
  • Geonix
  • GloryCloud
  • IPFly
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • MangoProxy
  • MoMoProxy
  • NovaProxy
  • Proxiware
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • Proxyma
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • WealthProxies

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
65.60.128.0/17
since Jun 2023
AS11776Residential616
124 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
65.60.128.0/1732,768WIDEOPENWESTBreezeline (ATLAN-19) · USDirect AllocationNov 1, 2002abuse@breezeline.com
└ 65.60.175.0/24256OH-COLUMBUS-CPEBreezeline (C02412470) · USReassignedJan 29, 2010abuse@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

Summary

Routing history

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

History

Handoffs
4