Data as of Nov 13, 2026

207.255.27.0/24

1 residential-proxy exit · 30 days

Breezeline

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

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Providers
19
selling exits here
Oct 14, 2026 – Nov 12, 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.24.0/21
since Apr 2009
AS11776Residential1Breezeline
via Breezeline
207.255.0.0/18
since Dec 2005
AS11776Residential161
31 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.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
Jan 2014
Current origin since
Jan 2014 · 13 yr
Origin networks
1