Data as of Nov 12, 2026

207.255.24.0/21

1 residential-proxy exit · 30 days

Breezeline

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
1
0.05% of its addresses · 30 days
Spread
1 of 8
/24s with at least one exit
Providers
19
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

1.5K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • B2Proxy
  • BottingTools
  • Bright Data
  • ColaProxy
  • EZProxies
  • GloryCloud
  • IPFly
  • IPPeak
  • Kookey
  • MoMoProxy
  • PuraRoute
  • RainProxy
  • RoamProxy
  • RolaProxy
  • StrikeProxy
  • Thordata
  • YumiProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
207.255.0.0/18
since Dec 2005
AS11776Residential161
31 always on
Breezeline
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
207.255.24.0/24
since Jan 2014
AS11776ResidentialBreezeline
via Breezeline
207.255.26.0/24
since May 2014
AS11776ResidentialBreezeline
via Breezeline
207.255.27.0/24
since Jan 2014
AS11776Residential1Breezeline
via Breezeline
207.255.28.0/24
since Apr 2024
AS11776ResidentialBreezeline
via Breezeline
207.255.29.0/24
since Jul 2018
AS11776ResidentialBreezeline
via 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.16.0/204,096JST-PA-207-255-16Breezeline (ATLAN-19) · USReallocatedApr 7, 2005abuse@breezeline.com

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Apr 2009
Current origin since
Apr 2009 · 18 yr
Origin networks
1