Data as of Nov 10, 2026

207.255.136.0/21

19 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
19
0.93% of its addresses · 30 days
Always-on exits
4
21% of its exits
Spread
8 of 8
/24s with at least one exit
Providers
62
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

17K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • AnyIP
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • ColaProxy
  • CoreProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • Geonode
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • MarsProxies
  • MrScraper
  • NodeMaven
  • NovaProxy
  • Novada
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • RainProxy
  • ResiProxies
  • SPYDERPROXY_PREMIUM
  • Shifter
  • SpyderProxy
  • Thordata
  • ThunderProxy
  • TrueProxies
  • VantageProxies
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_LITE

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.136.0/212,048BFD-PA-207-255-136Breezeline (ATLAN-19) · USReallocatedMar 30, 2005abuse@breezeline.com
└ 207.255.136.0/212,048PA-BRADFORD-CPEAtlantic Broadband (C07444319) · USReassignedOct 22, 2019abuse@breezeline.com
via BFD-PA-207-255-136

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

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Mar 2011 · 16 yr
Origin networks
4
Last change of origin
Mar 2011
Recorded history

History

Handoffs
3