Data as of Nov 10, 2026

207.255.16.0/22

15 residential-proxy exits · 30 days

Breezeline

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

Residential-proxy exits

Proxy exits
15
1.5% of its addresses · 30 days
Always-on exits
5
33% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
55
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

15K observations

/24s with the most always-on exits

Proxy providers listing exits

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

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
207.255.16.0/21
since Apr 2009
AS11776Residential26
6 always on
Breezeline
via Breezeline
207.255.0.0/18
since Dec 2005
AS11776Residential163
35 always on
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

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
Oct 2021
Current origin since
Oct 2021 · 5.1 yr
Origin networks
1