Data as of Nov 20, 2026

207.255.38.0/24

6 residential-proxy exits · 30 days

Breezeline

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

Residential-proxy exits

Proxy exits
6
2.3% of its addresses · 30 days
Always-on exits
2
33% of its exits
Providers
46
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

16K observations

Proxy providers listing exits

  • 9Proxy
  • AnyIP
  • BESTPROXY_NET
  • BUYPERSONALPROXY
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • ColaProxy
  • Decodo
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FastProxy
  • FlashProxy
  • FloppyData
  • GEEKPROXY_TURBO
  • Geonode
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • HASDATA
  • IP2WORLD
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • LudaxProxy
  • MoMoProxy
  • NovaProxy
  • Oxylabs
  • PROXIWARE_ECO
  • PROXYSCRAPE
  • PYPROXY
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • Q2IP
  • RainProxy
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
207.255.32.0/21
since Apr 2009
AS11776Residential20
3 always on
Breezeline
via Breezeline
207.255.0.0/18
since Dec 2005
AS11776Residential160
35 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.36.0/22

Routing history

Pattern
Stable
First seen
Oct 2011
Current origin since
Jun 2018 · 8.4 yr
Origin networks
2
Last change of origin
May 2014
Recorded history

History

Handoffs
1