Data as of Nov 12, 2026

69.171.201.0/24

7 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
7
2.7% of its addresses · 30 days
Always-on exits
1
14% of its exits
Providers
35
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

5.2K observations

Proxy providers listing exits

  • Ake.net
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • DataImpulse
  • EnigmaProxy
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FloppyData
  • GloryCloud
  • GonzoProxy
  • Infatica
  • KocerRoxy
  • LemonBright
  • LudaxProxy
  • MoMoProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • Q2IP
  • RainProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
69.171.200.0/22
since Jun 2023
AS11776Residential16
4 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
69.171.192.0 - 69.171.205.2553,584WIDEOPENWESTBreezeline (ATLAN-19) · USDirect AllocationMar 6, 2009abuse@breezeline.com
└ 69.171.201.0/24256OH-CLEVELAND-CPEBreezeline (C09160439) · USReassignedJan 24, 2023abuse@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
Aug 2021
Current origin since
Sep 2022 · 4.2 yr
Origin networks
2
Last change of origin
Sep 2022
Recorded history

History

Handoffs
1