Data as of Nov 11, 2026

138.207.158.0/23

9 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
9
1.8% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
18
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

913 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
138.207.159.0/2405
138.207.158.0/2404

Proxy providers listing exits

  • Byteful
  • CliProxy
  • ColaProxy
  • FastProxy
  • GloryCloud
  • IPFly
  • IPPeak
  • Infatica
  • KocerRoxy
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • NovProxy
  • PuraRoute
  • RainProxy
  • Thordata
  • ThunderProxy
  • VitalExclusive

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
138.207.128.0/1732,768ATLAN-19Breezeline (ATLAN-19) · USDirect AllocationOct 21, 2015abuse@breezeline.com
└ 138.207.158.0/23512FL-MIAMI-NBAY-CPEAtlantic Broadband (C07696901) · USReassignedNov 30, 2020abuse@breezeline.com
via ATLAN-19

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
Sep 2018
Current origin since
Jan 2020 · 6.8 yr
Origin networks
2
Last change of origin
Jan 2020
Recorded history

History

Handoffs
1