Data as of Nov 16, 2026

209.203.200.0/22

2 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
2
0.20% of its addresses · 30 days
Always-on exits
1
50% of its exits
Spread
1 of 4
/24s with at least one exit
Providers
20
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

10K observations

Proxy providers listing exits

  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • ColaProxy
  • DataImpulse
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • GonzoProxy
  • Infatica
  • Oxylabs
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • Thordata
  • ThunderProxy

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
209.203.192.0/198,192ATLANTICBBBreezeline (ATLAN-19) · USDirect AllocationOct 6, 2011abuse@breezeline.com
└ 209.203.200.0/221,024JST-PA-209-203-200-0Breezeline (ATLAN-19) · USReallocatedJan 23, 2013abuse@breezeline.com
└ 209.203.200.0/221,024PA-JOHNSTOWN-CPEBreezeline (C09150512) · USReassignedJan 19, 2023abuse@breezeline.com
via JST-PA-209-203-200-0

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
Feb 2012
Current origin since
May 2017 · 9.5 yr
Origin networks
2
Last change of origin
Apr 2012
Recorded history

History

Handoffs
1