Data as of Nov 11, 2026

207.255.40.0/24

7 residential-proxy exits · 30 days

Breezeline

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

Residential-proxy exits

Proxy exits
7
2.7% of its addresses · 30 days
Always-on exits
1
14% of its exits
Providers
43
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

6.2K observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • ColaProxy
  • DataImpulse
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • Geonode
  • GhostConnect
  • GloryCloud
  • IPFly
  • IPMUSK
  • IPPeak
  • InfiniteProxies
  • Kookey
  • LemonBright
  • LudaxProxy
  • NovaProxy
  • PROXYON
  • Proxiware
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • ResiProxies
  • RoamProxy
  • SPYDERPROXY_PREMIUM
  • Thordata
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
207.255.0.0/18
since Dec 2005
AS11776Residential165
31 always on
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.32.0/198,192JST-PA-207-255-32Breezeline (ATLAN-19) · USReallocatedApr 7, 2005abuse@breezeline.com

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

207.255.40.0/21

Routing history

Pattern
Stable
First seen
Apr 2009
Current origin since
Jan 2014 · 13 yr
Origin networks
2
Last change of origin
Jan 2014
Recorded history

History

Handoffs
2