Data as of Nov 12, 2026

207.255.13.0/24

4 residential-proxy exits · 30 days

Breezeline

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

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Providers
24
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

3.3K observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • B2Proxy
  • BottingTools
  • Bright Data
  • Byteful
  • ColaProxy
  • EZProxies
  • FastProxy
  • GSocks
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • NextProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • RainProxy
  • Thordata
  • ThunderProxy
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
207.255.8.0/21
since Sep 2018
AS11776Residential40
6 always on
Breezeline
via Breezeline
207.255.0.0/18
since Dec 2005
AS11776Residential165
31 always on
Breezeline

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
207.255.0.0/1665,536ATLANTICBB-JOHNSTOWNBreezeline (ATLAN-19) · USDirect AllocationJun 14, 2004abuse@breezeline.com
└ 207.255.8.0/212,048JST-PA-207-255-8Breezeline (ATLAN-19) · USReallocatedApr 7, 2005abuse@breezeline.com
└ 207.255.12.0/23512PA-UNIONTOWN-CPEAtlantic Broadband (C06983755) · USReassignedMay 16, 2018abuse@breezeline.com
via JST-PA-207-255-8

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

207.255.12.0/23

Routing history

Pattern
Stable
First seen
Oct 2021
Current origin since
Oct 2021 · 5.1 yr
Origin networks
1