Data as of Nov 11, 2026

69.80.176.0/24

37 residential-proxy exits · 30 days

Apogee Telecom Inc.

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

Residential-proxy exits

Proxy exits
37
14% of its addresses · 30 days
Providers
37
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

6.1K observations

Proxy providers listing exits

  • Ake.net
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • ColaProxy
  • Datarama
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlexyProxies
  • GSocks
  • Geonode
  • GloryCloud
  • GonzoProxy
  • IPMUSK
  • Infatica
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • RainProxy
  • ResiProxies
  • SPYDERPROXY_PREMIUM
  • Thordata
  • ThunderProxy
  • VantageProxies
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
69.80.176.0/21
since Aug 2018
AS54607Residential133Apogee Telecom Inc.

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
69.80.128.0/1816,384APOGEEApogee Telecom Inc. (APOG) · USDirect AllocationJul 26, 2005abuse@apogeenet.net
└ 69.80.176.0/24256BOLD-S-CANTONunknownReassignedApr 30, 2025abuse@apogeenet.net
via APOGEE

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Rotating
First seen
Apr 2024
Current origin since
Jun 2025 · 1.4 yr
Origin networks
2
Last change of origin
Jun 2025
Recorded history

History

Handoffs
1