Data as of Nov 15, 2026

208.90.138.0/24

3 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
3
1.2% of its addresses · 30 days
Always-on exits
2
67% of its exits
Providers
42
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

8.3K observations

Proxy providers listing exits

  • 711Proxy
  • 9HTTP
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CoreProxy
  • DataImpulse
  • Decodo
  • EZProxies
  • FlashProxy
  • FloppyData
  • Geonode
  • GloryCloud
  • HELODATA
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • IPRoyal
  • InfiniteProxies
  • LOKIPROXY
  • LemonBright
  • LudaxProxy
  • MarsProxies
  • Oxylabs
  • Proxiware
  • Proxy302
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • 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
208.90.136.0/212,048METROCAST-MAR-8Breezeline (ATLAN-19) · USDirect AllocationJul 7, 2014abuse@breezeline.com
└ 208.90.138.0/24256VA-SALUDA-CPEAtlantic Broadband (C06931050) · USReassignedMar 23, 2018abuse@breezeline.com
via METROCAST-MAR-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

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Feb 2009
Current origin since
Aug 2020 · 6.2 yr
Origin networks
3
Last change of origin
Aug 2020
Recorded history

History

Handoffs
2