Data as of Nov 21, 2026

209.42.138.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
Providers
31
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

1.1K observations

Proxy providers listing exits

  • 9HTTP
  • Ake.net
  • AnyIP
  • B2Proxy
  • BlurPath
  • BottingTools
  • Bright Data
  • CatProxies
  • CliProxy
  • DataImpulse
  • EnigmaProxy
  • FastProxy
  • FloppyData
  • GloryCloud
  • HPROXY
  • HideProxy
  • IPPeak
  • KocerRoxy
  • LemonBright
  • NovProxy
  • PROXYSCRAPE
  • PrivateProxy
  • Proxies.fo
  • Proxiware
  • RainProxy
  • SPYDERPROXY_BASIC
  • Shifter
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

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.138.0/24256VA-SALUDA-CPEAtlantic Broadband (C06167024) · USReassignedJul 8, 2016abuse@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
May 2016
Current origin since
Aug 2020 · 6.2 yr
Origin networks
2
Last change of origin
Aug 2020
Recorded history

History

Handoffs
1