Data as of Nov 10, 2026

75.76.64.0/22

9 residential-proxy exits · 30 days

Breezeline

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
9
0.88% of its addresses · 30 days
Always-on exits
1
11% of its exits
Spread
2 of 4
/24s with at least one exit
Providers
47
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

3.7K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
75.76.66.0/2418
75.76.64.0/2401

Proxy providers listing exits

  • 711Proxy
  • ASHBURNPROXIES
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BlurPath
  • BottingTools
  • Bright Data
  • Byteful
  • CatProxies
  • CliProxy
  • ColaProxy
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • GhostConnect
  • GloryCloud
  • GoProxies
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • NextProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYON
  • PROXYSCRAPE
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • PuraRoute
  • RainProxy
  • ThunderProxy
  • TrueProxies
  • VantageProxies
  • VitalExclusive
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
75.76.66.0/24
since Sep 2022
AS11776Residential8
1 always on
Breezeline

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
75.76.48.0 - 75.76.68.2555,376ATLAN-19Breezeline (ATLAN-19) · USDirect AllocationFeb 13, 2008abuse@breezeline.com
└ 75.76.64.0/24256OH-CLEVELAND-CPEunknown———
└ 75.76.65.0/24256KNOX-75-76-65-0-24unknown———
└ 75.76.66.0/24256OH-CLEVELAND-CPEBreezeline (C05525010) · USReassignedDec 11, 2014abuse@breezeline.com
via ATLAN-19
└ 75.76.67.0/24256OH-COLUMBUS-CPEunknown———

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
Jun 2023
Current origin since
Jun 2023 · 3.4 yr
Origin networks
1