Data as of Nov 13, 2026

207.255.14.0/23

4 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
4
0.78% of its addresses · 30 days
Always-on exits
1
25% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
36
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

5.8K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
207.255.14.0/2412
207.255.15.0/2402

Proxy providers listing exits

  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • FloppyData
  • GloryCloud
  • GonzoProxy
  • IPMUSK
  • Infatica
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NodeMaven
  • NovProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • Q2IP
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
207.255.8.0/21
since Sep 2018
AS11776Residential38
6 always on
Breezeline
via Breezeline
207.255.0.0/18
since Dec 2005
AS11776Residential160
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.8.0/212,048JST-PA-207-255-8Breezeline (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
Oct 2021
Current origin since
Oct 2021 · 5.1 yr
Origin networks
1