Data as of Nov 18, 2026

75.118.56.0/24

8 residential-proxy exits · 30 days

Breezeline

Announcement
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
8
3.1% of its addresses · 30 days
Always-on exits
1
13% of its exits
Providers
34
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

3.7K observations

Proxy providers listing exits

  • Ake.net
  • AnyIP
  • B2Proxy
  • BlurPath
  • Bright Data
  • Byteful
  • CliProxy
  • ColaProxy
  • Decodo
  • EnigmaProxy
  • FastProxy
  • FloppyData
  • GloryCloud
  • IPFly
  • IPPeak
  • KocerRoxy
  • LemonBright
  • LemonPrime
  • MoMoProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PROXYSAVER
  • Proxiware
  • Proxy302
  • ProxyEmpire
  • ProxyWing
  • PuraRoute
  • RainProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • WealthProxies

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
75.118.0.0/17
since Dec 2024
AS11776Residential610
119 always on
Breezeline
75.118.0.0/16
since Jun 2023
AS11776Residential878
161 always on
Breezeline

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
75.118.0.0/1665,536WIDEOPENWESTBreezeline (ATLAN-19) · USDirect AllocationNov 2, 2006abuse@breezeline.com
└ 75.118.56.0/212,048OH-CLEVELAND-CPEBreezeline (C02118315) · USReassignedDec 18, 2008abuse@breezeline.com
via WIDEOPENWEST

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

Covering aggregate above, the prefix's own history below

75.118.56.0/21

Routing history

Pattern
Rotating
First seen
Dec 2006
Current origin since
Sep 2022 · 4.2 yr
Origin networks
4
Last change of origin
Sep 2022
Recorded history

History

Handoffs
5