Data as of Nov 20, 2026

209.42.150.0/24

5 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
5
2.0% of its addresses · 30 days
Always-on exits
1
20% of its exits
Providers
35
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

18K observations

Proxy providers listing exits

  • AETHYN_ELITE
  • AnyIP
  • BirdProxies
  • BlurPath
  • BottingTools
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLEETPROXY
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • GloryCloud
  • HASDATA
  • HPROXY
  • IPPeak
  • Infatica
  • LudaxProxy
  • NovProxy
  • NovaProxy
  • PROXIWARE_ECO
  • PROXORA
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • VantageProxies
  • 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
209.42.128.0/198,192METRO-13Breezeline (ATLAN-19) · USDirect AllocationFeb 11, 2016abuse@breezeline.com
└ 209.42.150.0/24256VA-SALUDA-CPEAtlantic Broadband (C07026062) · USReassignedJul 20, 2018abuse@breezeline.com
via METRO-13

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
Aug 2016
Current origin since
Aug 2020 · 6.2 yr
Origin networks
3
Last change of origin
Aug 2020
Recorded history

History

Handoffs
2