Data as of Nov 10, 2026

206.53.84.0/22

20 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
20
2.0% of its addresses · 30 days
Always-on exits
6
30% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
62
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

26K observations

/24s with the most always-on exits

Proxy providers listing exits

  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • Bright Data
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CliProxy
  • ColaProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • Geonode
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • IPMUSK
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • NodeMaven
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYON
  • PROXYSCRAPE
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • RainProxy
  • ResiProxies
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • WealthProxies
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
206.53.64.0/19
since May 2020
AS11776Residential41
11 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
206.53.64.0/198,192ATLANTICBB-CTBreezeline (ATLAN-19) · USDirect AllocationMay 26, 2004abuse@breezeline.com
└ 206.53.84.0/221,024CT-MONTVILLE-CPEAtlantic Broadband (C07750564) · USReassignedFeb 9, 2021abuse@breezeline.com
via ATLANTICBB-CT

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
Stable
First seen
Jul 2020
Current origin since
Jul 2020 · 6.3 yr
Origin networks
1