Data as of Nov 19, 2026

65.175.246.0/24

2 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
2
0.78% of its addresses · 30 days
Always-on exits
1
50% of its exits
Providers
20
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

646 observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • FloppyData
  • GloryCloud
  • IPFly
  • IPPeak
  • Kookey
  • MoMoProxy
  • Novada
  • ProxyWing
  • RapidProxy
  • RoamProxy
  • RolaProxy
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • YumiProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
65.175.192.0/18
since Jul 2020
AS11776Residential106
11 always on
Breezeline
65.175.128.0/17
since Jul 2020
AS11776Residential196
21 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
65.175.128.0/1732,768METROCAST-NETBreezeline (ATLAN-19) · USDirect AllocationMar 1, 2004abuse@breezeline.com
└ 65.175.246.0/24256ME-SANFORD-CPEAtlantic Broadband (C06929366) · USReassignedMar 22, 2018abuse@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

Summary

Routing history

Pattern
Stable
First seen
Apr 2023
Current origin since
Apr 2023 · 3.6 yr
Origin networks
1