LAYER3 INTEL
Get started
Sign in
Data as of Nov 10, 2026

207.255.32.0/23

4 residential-proxy exits · 30 days

Breezeline

Announcement
this exact prefix
RPKI valid
Announced by
AS11776
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
4
0.78% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
5
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

43 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
207.255.32.0/2403
207.255.33.0/2401

Proxy providers listing exits

  • ColaProxy
  • FastProxy
  • FloppyData
  • LemonBright
  • Thordata

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
207.255.32.0/21
since Apr 2009
AS11776Residential20
4 always on
Breezeline
via Breezeline
207.255.0.0/18
since Dec 2005
AS11776Residential163
35 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
207.255.0.0/1665,536ATLANTICBB-JOHNSTOWNBreezeline (ATLAN-19) · USDirect AllocationJun 14, 2004abuse@breezeline.com
└ 207.255.32.0/198,192JST-PA-207-255-32Breezeline (ATLAN-19) · USReallocatedApr 7, 2005abuse@breezeline.com
└ 207.255.32.0/23512WV-KINGWOOD-CPEBreezeline (C09262711) · USReassignedMar 1, 2023abuse@breezeline.com
via JST-PA-207-255-32

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Feb 2023
Current origin since
Feb 2023 · 3.7 yr
Origin networks
1