LAYER3 INTEL
Get started
Sign in
Data as of Nov 10, 2026

207.255.78.0/24

3 residential-proxy exits · 30 days

Breezeline

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

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Always-on exits
1
33% of its exits
Providers
28
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

2.6K observations

Proxy providers listing exits

  • 711Proxy
  • B2Proxy
  • BottingTools
  • CliProxy
  • ColaProxy
  • EZProxies
  • EnigmaProxy
  • FLEETPROXY
  • FastProxy
  • GloryCloud
  • IPFly
  • IPMUSK
  • IPPeak
  • Kookey
  • LudaxProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxy302
  • ProxyEmpire
  • PuraRoute
  • RainProxy
  • RoamProxy
  • RolaProxy
  • SPYDERPROXY_PREMIUM
  • Thordata
  • VantageProxies
  • YumiProxy
  • ZENPROXY_LITE

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.64.0/198,192JST-PA-207-255-64Breezeline (ATLAN-19) · USReallocatedApr 8, 2005abuse@breezeline.com
└ 207.255.64.0/198,192PA-ALTOONA-CPEAtlantic Broadband (C08026205) · USReassignedSep 13, 2021abuse@breezeline.com
via JST-PA-207-255-64

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced 207.255.64.0/19

207.255.64.0/19

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Dec 2005 · 21 yr
Origin networks
2
Last change of origin
Dec 2005
Recorded history

History

Handoffs
1