Data as of Nov 18, 2026

216.36.15.0/24

4 residential-proxy exits · 30 days

Breezeline

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

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Providers
28
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

668 observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • B2Proxy
  • BESTPROXY_NET
  • BlurPath
  • Bright Data
  • CatProxies
  • CliProxy
  • EnigmaProxy
  • FastProxy
  • GloryCloud
  • HELODATA
  • HPROXY
  • HideProxy
  • IPPeak
  • KocerRoxy
  • LemonBright
  • NovProxy
  • NovaProxy
  • PROXYSCRAPE
  • PrivateProxy
  • Proxy302
  • RainProxy
  • SPYDERPROXY_BASIC
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • 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
216.36.0.0/198,192GMPEXPRESSBreezeline (ATLAN-19) · USDirect AllocationJul 5, 2005abuse@breezeline.com
└ 216.36.15.0/24256METROCAST-MD-STMARY2Metrocast Communications (C01495583) · USReassignedNov 14, 2006abuse@breezeline.com
via GMPEXPRESS

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
Oct 2006
Current origin since
Feb 2026 · 9 mo
Origin networks
2
Last change of origin
Feb 2026
Recorded history

History

Handoffs
1