Data as of Nov 18, 2026

65.175.183.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
Providers
31
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

515 observations

Proxy providers listing exits

  • 2Captcha
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • ColaProxy
  • EZProxies
  • EnigmaProxy
  • FastProxy
  • FloppyData
  • GonzoProxy
  • Infatica
  • LudaxProxy
  • MangoProxy
  • NovaProxy
  • Novada
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyWing
  • Proxyma
  • RainProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
65.175.160.0/19
since Jul 2020
AS11776Residential59
6 always on
Breezeline
65.175.128.0/17
since Jul 2020
AS11776Residential196
22 always on
Breezeline

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
65.175.128.0/1732,768METROCAST-NETBreezeline (ATLAN-19) · USDirect AllocationMar 1, 2004abuse@breezeline.com
└ 65.175.182.0/23512ME-SANFORD-CPEAtlantic Broadband (C08880073) · USReassignedSep 12, 2022abuse@breezeline.com
via METROCAST-NET

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.175.182.0/23

Routing history

Pattern
Stable
First seen
Sep 2022
Current origin since
Sep 2022 · 4.2 yr
Origin networks
1