Data as of Nov 11, 2026

207.255.8.0/21

40 residential-proxy exits · 30 days

Breezeline

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
40
2.0% of its addresses · 30 days
Always-on exits
6
15% of its exits
Spread
8 of 8
/24s with at least one exit
Providers
76
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

40K 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
  • CoreProxy
  • DataImpulse
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonode
  • GhostConnect
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • IPFly
  • IPMUSK
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NextProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • PrivateProxy
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • RoamProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • TrueProxies
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • WealthProxies
  • 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.8.0/23
since Oct 2021
AS11776Residential13
3 always on
Breezeline
via Breezeline
207.255.10.0/23
since Oct 2021
AS11776Residential12
2 always on
Breezeline
via Breezeline
207.255.12.0/23
since Oct 2021
AS11776Residential10Breezeline
via Breezeline
207.255.14.0/23
since Oct 2021
AS11776Residential5
1 always on
Breezeline
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.8.0/212,048JST-PA-207-255-8Breezeline (ATLAN-19) · USReallocatedApr 7, 2005abuse@breezeline.com
└ 207.255.8.0/23512PA-UNIONTOWN-CPEAtlantic Broadband (C06983751) · USReassignedMay 16, 2018abuse@breezeline.com
via JST-PA-207-255-8
└ 207.255.10.0/23512PA-UNIONTOWN-CPEAtlantic Broadband (C06983752) · USReassignedMay 16, 2018abuse@breezeline.com
via JST-PA-207-255-8
└ 207.255.12.0/23512PA-UNIONTOWN-CPEAtlantic Broadband (C06983755) · USReassignedMay 16, 2018abuse@breezeline.com
via JST-PA-207-255-8

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
Sep 2018 · 8.2 yr
Origin networks
1