Data as of Nov 16, 2026

146.168.6.0/23

4 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
4
0.78% of its addresses · 30 days
Always-on exits
1
25% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
34
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

3.7K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
146.168.7.0/2411
146.168.6.0/2403

Proxy providers listing exits

  • 711Proxy
  • AETHYN_ELITE
  • ASHBURNPROXIES
  • B2Proxy
  • BottingTools
  • Bright Data
  • Byteful
  • EZProxies
  • EnigmaProxy
  • FLEETPROXY
  • FastProxy
  • FloppyData
  • GloryCloud
  • IPFly
  • IPPeak
  • KocerRoxy
  • LemonBright
  • LudaxProxy
  • MoMoProxy
  • NodeMaven
  • NovaProxy
  • PROXORA
  • Proxiware
  • ProxyEmpire
  • ProxyRack
  • PuraRoute
  • RainProxy
  • RolaProxy
  • SPYDERPROXY_PREMIUM
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • YumiProxy

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
146.168.0.0/1665,536ATLAN-19Breezeline (ATLAN-19) · USDirect AllocationDec 27, 2017abuse@breezeline.com
└ 146.168.6.0/23512NH-BELMONT-CPEAtlantic Broadband (C07009888) · USReassignedJun 26, 2018abuse@breezeline.com
via ATLAN-19

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

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Jul 2020
Current origin since
Jul 2020 · 6.3 yr
Origin networks
1