Data as of Nov 12, 2026

65.175.185.0/24

2 residential-proxy exits · 30 days

Breezeline

Announcement
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Providers
17
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

700 observations

Proxy providers listing exits

  • 711Proxy
  • B2Proxy
  • BottingTools
  • EZProxies
  • FloppyData
  • GloryCloud
  • IPFly
  • IPPeak
  • Kookey
  • LudaxProxy
  • MoMoProxy
  • Novada
  • Proxy302
  • PuraRoute
  • RainProxy
  • RolaProxy
  • Thordata

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
65.175.160.0/19
since Jul 2020
AS11776Residential57
8 always on
Breezeline
65.175.128.0/17
since Jul 2020
AS11776Residential191
25 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.184.0/23512ME-SANFORD-CPEAtlantic Broadband (C08880079) · 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.184.0/23

Routing history

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