Data as of Nov 12, 2026

207.255.20.0/24

4 residential-proxy exits · 30 days

Breezeline

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

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Always-on exits
1
25% of its exits
Providers
33
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

3.0K observations

Proxy providers listing exits

  • Ake.net
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • ColaProxy
  • EnigmaProxy
  • FLEETPROXY
  • FastProxy
  • FloppyData
  • GloryCloud
  • IPPeak
  • Infatica
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • Q2IP
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Thordata
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
207.255.16.0/21
since Apr 2009
AS11776Residential27
5 always on
Breezeline
via Breezeline
207.255.0.0/18
since Dec 2005
AS11776Residential161
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.16.0/204,096JST-PA-207-255-16Breezeline (ATLAN-19) · USReallocatedApr 7, 2005abuse@breezeline.com
└ 207.255.20.0/23512WV-KINGWOOD-CPEBreezeline (C09262715) · USReassignedMar 1, 2023abuse@breezeline.com
via JST-PA-207-255-16

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.20.0/23

Routing history

Pattern
Stable
First seen
Feb 2023
Current origin since
Feb 2023 · 3.7 yr
Origin networks
1