Data as of Nov 13, 2026

207.255.168.0/22

3 residential-proxy exits · 30 days

Breezeline

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
3
0.29% of its addresses · 30 days
Spread
2 of 4
/24s with at least one exit
Providers
16
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

175 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
207.255.170.0/2402
207.255.171.0/2401

Proxy providers listing exits

  • BESTPROXY_NET
  • CliProxy
  • EnigmaProxy
  • FastProxy
  • Geonode
  • HELODATA
  • HPROXY
  • HideProxy
  • InfiniteProxies
  • LemonBright
  • PROXYSCRAPE
  • Proxiware
  • RainProxy
  • Shifter
  • VantageProxies
  • ZENPROXY_PREMIUM

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
207.255.169.0/24
since Dec 2016
AS11776ResidentialBreezeline
via Breezeline
207.255.170.0/24
since Dec 2016
AS11776Residential2Breezeline
via Breezeline
207.255.171.0/24
since Oct 2021
AS11776Residential1Breezeline
via 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
207.255.0.0/1665,536ATLANTICBB-JOHNSTOWNBreezeline (ATLAN-19) · USDirect AllocationJun 14, 2004abuse@breezeline.com
└ 207.255.168.0/212,048SMC-PA-207-255-168Breezeline (ATLAN-19) · USReallocatedApr 1, 2005abuse@breezeline.com
└ 207.255.170.0/24256PA-BRADFORD-CPEAtlantic Broadband (C07028403) · USReassignedJul 25, 2018abuse@breezeline.com
via SMC-PA-207-255-168

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
Mar 2012
Current origin since
Mar 2012 · 15 yr
Origin networks
1