Data as of Nov 15, 2026

216.36.14.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
Always-on exits
2
50% of its exits
Providers
42
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

6.9K observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • ColaProxy
  • DataImpulse
  • Decodo
  • EZProxies
  • EnigmaProxy
  • FastProxy
  • FloppyData
  • GloryCloud
  • IPFly
  • IPPeak
  • Infatica
  • Kookey
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • RoamProxy
  • RolaProxy
  • Shifter
  • TalorData
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • YumiProxy

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.14.0/24256METROCAST-MD-STMARY1Metrocast Communications (C01946026) · USReassignedJun 10, 2008abuse@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
Dec 2006
Current origin since
Feb 2026 · 9 mo
Origin networks
4
Last change of origin
Feb 2026
Recorded history

History

Handoffs
3