Data as of Nov 10, 2026

207.255.52.0/23

11 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
11
2.1% of its addresses · 30 days
Always-on exits
1
9.1% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
51
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

21K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
207.255.53.0/2419
207.255.52.0/2402

Proxy providers listing exits

  • 9Proxy
  • Ake.net
  • AnyIP
  • BirdProxies
  • BlurPath
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • ColaProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FloppyData
  • Geonode
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • NextProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • WealthProxies
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
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.32.0/198,192JST-PA-207-255-32Breezeline (ATLAN-19) · USReallocatedApr 7, 2005abuse@breezeline.com
└ 207.255.52.0/23512PA-UNIONTOWN-CPEAtlantic Broadband (C06983759) · USReassignedMay 16, 2018abuse@breezeline.com
via JST-PA-207-255-32

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