Data as of Nov 10, 2026

173.44.70.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
1
25% of its exits
Providers
36
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

812 observations

Proxy providers listing exits

  • 711Proxy
  • B2Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • Geonode
  • GoProxies
  • GonzoProxy
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • LemonBright
  • NovProxy
  • Novada
  • Oxylabs
  • Proxies.fo
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • Thordata
  • ThunderProxy
  • VitalExclusive

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
173.44.64.0 - 173.44.115.25513,312METROCAST-BLOCK-6Breezeline (ATLAN-19) · USDirect AllocationJan 20, 2010abuse@breezeline.com
└ 173.44.70.0/24256PA-POCONO-CPEAtlantic Broadband (C06930882) · USReassignedMar 23, 2018abuse@breezeline.com
via METROCAST-BLOCK-6

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
Nov 2020
Current origin since
Nov 2020 · 6.0 yr
Origin networks
1