Data as of Nov 11, 2026

207.255.255.0/24

5 residential-proxy exits · 30 days

Breezeline

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential
Risk
30 / 100 · Medium
Recently moved
Recent change
New origin Aug 2026
from AS3356 Level 3 Parent, LLC, after 4.9 years unannounced

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Always-on exits
1
20% of its exits
Providers
33
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

3.3K observations

Proxy providers listing exits

  • Ake.net
  • Byteful
  • CliProxy
  • ColaProxy
  • EnigmaProxy
  • Evomi
  • FastProxy
  • GSocks
  • GloryCloud
  • IPMUSK
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • Proxiware
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Thordata
  • ThunderProxy
  • TrueProxies
  • VantageProxies
  • VitalExclusive
  • WealthProxies
  • ZENPROXY_LITE

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.255.0/24256ABBN-MD-207-255-255Breezeline (ATLAN-19) · USReallocatedApr 7, 2005abuse@breezeline.com
└ 207.255.255.0/24256IMC-207-255-255-0-1IMC (C03101298) · USReassignedJul 13, 2012abuse@breezeline.com
via ABBN-MD-207-255-255

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
Reactivated
First seen
Jun 2012
Current origin since
Aug 2026 · 3 mo
Origin networks
4
Last change of origin
Aug 2026
Recorded history

History

Handoffs
4