Data as of Nov 13, 2026

207.255.102.0/24

3 residential-proxy exits · 30 days

Breezeline

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

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Always-on exits
1
33% of its exits
Providers
25
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

2.2K observations

Proxy providers listing exits

  • 711Proxy
  • AnyIP
  • B2Proxy
  • BottingTools
  • Bright Data
  • ByteProxies
  • EZProxies
  • FastProxy
  • FlashProxy
  • FloppyData
  • GloryCloud
  • IPFly
  • IPPeak
  • Kookey
  • LemonBright
  • LudaxProxy
  • MoMoProxy
  • Novada
  • PuraRoute
  • RainProxy
  • RolaProxy
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • YumiProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
207.255.96.0/21
since Aug 2016
AS11776Residential13
1 always on
Breezeline
via Breezeline
207.255.96.0/19
since Dec 2005
AS11776Residential51
2 always on
Breezeline
via Breezeline

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
207.255.0.0/1665,536ATLANTICBB-JOHNSTOWNBreezeline (ATLAN-19) · USDirect AllocationJun 14, 2004abuse@breezeline.com
└ 207.255.96.0/198,192UNT-PA-207-255-96Breezeline (ATLAN-19) · USReallocatedApr 1, 2005abuse@breezeline.com
└ 207.255.102.0/23512PA-ALTOONA-CPEAtlantic Broadband (C08431935) · USReassignedMay 19, 2022abuse@breezeline.com
via UNT-PA-207-255-96

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

207.255.102.0/23

Routing history

Pattern
Stable
First seen
May 2022
Current origin since
May 2022 · 4.5 yr
Origin networks
1