Data as of Nov 15, 2026

207.255.134.0/24

1 residential-proxy exit · 30 days

Breezeline

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

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Always-on exits
1
100% of its exits
Providers
19
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

3.4K observations

Proxy providers listing exits

  • Ake.net
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • FlashProxy
  • FlexyProxies
  • Geonode
  • GloryCloud
  • IPRoyal
  • MoMoProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
207.255.128.0/21
since Dec 2005
AS11776Residential13
3 always on
Breezeline
via 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.128.0/212,048UNT-PA-207-255-128Breezeline (ATLAN-19) · USReallocatedApr 1, 2005abuse@breezeline.com
└ 207.255.132.0/221,024PA-UNIONTOWN-CPEAtlantic Broadband (C07026186) · USReassignedJul 20, 2018abuse@breezeline.com
via UNT-PA-207-255-128

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

Routing timeline

Covering aggregate above, the prefix's own history below

207.255.132.0/22

Routing history

Pattern
Stable
First seen
Oct 2021
Current origin since
Oct 2021 · 5.1 yr
Origin networks
1