Data as of Nov 22, 2026

209.42.128.0/24

4 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
4
1.6% of its addresses · 30 days
Providers
41
selling exits here
Oct 23, 2026 – Nov 21, 2026

Exits seen per day

6.3K observations

Proxy providers listing exits

  • BirdProxies
  • BottingTools
  • Byteful
  • ColaProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FastProxy
  • FlexyProxies
  • GEEKPROXY_TURBO
  • GloryCloud
  • GonzoProxy
  • IP2WORLD
  • IPFly
  • Infatica
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXIWARE_ECO
  • PROXYSCRAPE
  • PYPROXY
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • 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.128.0/24256VA-SALUDA-CPEAtlantic Broadband (C07533787) · USReassignedApr 6, 2020abuse@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
Mar 2016
Current origin since
Oct 2020 · 6.1 yr
Origin networks
2
Last change of origin
Aug 2020
Recorded history

History

Handoffs
1