Data as of Nov 12, 2026

75.118.201.0/24

3 residential-proxy exits · 30 days

Breezeline

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

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Always-on exits
1
33% of its exits
Providers
33
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

11K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • B2Proxy
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • Decodo
  • EZProxies
  • FastProxy
  • FlashProxy
  • FloppyData
  • Geonode
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • LemonBright
  • LudaxProxy
  • Oxylabs
  • Proxy-Seller
  • Proxy302
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • RoamProxy
  • Thordata
  • ThunderProxy
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
75.118.128.0/17
since Dec 2024
AS11776Residential262
40 always on
Breezeline
75.118.0.0/16
since Jun 2023
AS11776Residential854
145 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.200.0/212,048OH-COLUMBUS-CPEBreezeline (C02132349) · USReassignedJan 14, 2009abuse@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.200.0/21

Routing history

Pattern
Rotating
First seen
Sep 2007
Current origin since
Sep 2022 · 4.2 yr
Origin networks
3
Last change of origin
Sep 2022
Recorded history

History

Handoffs
2