Data as of Nov 12, 2026

207.255.16.0/21

27 residential-proxy exits · 30 days

Breezeline

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
27
1.3% of its addresses · 30 days
Always-on exits
6
22% of its exits
Spread
8 of 8
/24s with at least one exit
Providers
63
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

30K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • CliProxy
  • ColaProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • LemonLabs
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
207.255.0.0/18
since Dec 2005
AS11776Residential165
31 always on
Breezeline
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
207.255.16.0/22
since Oct 2021
AS11776Residential16
4 always on
Breezeline
via Breezeline
207.255.20.0/23
since Feb 2023
AS11776Residential7
2 always on
Breezeline
via Breezeline
207.255.22.0/23
since Feb 2023
AS11776Residential4Breezeline
via Breezeline

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, 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.16.0/221,024PA-ALTOONA-CPEBreezeline (C09132148) · USReassignedJan 10, 2023abuse@breezeline.com
via JST-PA-207-255-16
└ 207.255.20.0/23512WV-KINGWOOD-CPEBreezeline (C09262715) · USReassignedMar 1, 2023abuse@breezeline.com
via JST-PA-207-255-16
└ 207.255.22.0/23512WV-KINGWOOD-CPEBreezeline (C09262716) · 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

Summary

Routing history

Pattern
Stable
First seen
Apr 2009
Current origin since
Apr 2009 · 18 yr
Origin networks
1