LAYER3 INTEL
Get started
Sign in
Data as of Nov 13, 2026

216.36.16.0/24

4 residential-proxy exits · 30 days

Breezeline

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

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Always-on exits
1
25% of its exits
Providers
36
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

6.2K observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • BottingTools
  • Bright Data
  • Byteful
  • CatProxies
  • CliProxy
  • CoreProxy
  • EnigmaProxy
  • FastProxy
  • FloppyData
  • GloryCloud
  • IPFly
  • IPRoyal
  • LemonBright
  • LudaxProxy
  • MarsProxies
  • MoMoProxy
  • NodeMaven
  • NovProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxying
  • PuraRoute
  • Q2IP
  • RainProxy
  • SpyderProxy
  • Thordata
  • 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.16.0/23512METROCAST-MD-STMARY2Metrocast Communications (C01495584) · 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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Sep 2020
Current origin since
Sep 2020 · 6.1 yr
Origin networks
1