Data as of Nov 20, 2026

173.32.206.0/23

14 residential-proxy exits · 30 days

Rogers Communications Canada Inc.

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

Residential-proxy exits

Proxy exits
14
2.7% of its addresses · 30 days
Always-on exits
2
14% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
50
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

13K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
173.32.207.0/2418
173.32.206.0/2416

Proxy providers listing exits

  • 711Proxy
  • AETHYN_BASIC
  • AETHYN_ELITE
  • B2Proxy
  • BirdProxies
  • BottingTools
  • Byteful
  • CatProxies
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FastProxy
  • FlashProxy
  • FloppyData
  • GEEKPROXY_TURBO
  • GloryCloud
  • HPROXY
  • HideProxy
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • LudaxProxy
  • MrScraper
  • NovaProxy
  • Novada
  • PROXIWARE_ECO
  • PROXYSCRAPE
  • PYPROXY
  • Proxio
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • ProxyEmpire
  • ProxyGeo
  • ProxyWing
  • Proxying
  • Proxyma
  • RainProxy
  • RapidProxy
  • SIMPLYNODE
  • SPYDERPROXY_BASIC
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
173.32.0.0/14
since Aug 2008
AS812Residential6,834
1,049 always on
Rogers Communications Canada 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
173.32.0.0/14262,144ROGERS-CAB-HSDRogers Communications Canada Inc. (RCC-182) · CADirect AllocationAug 6, 2008abuse@rogers.com
└ 173.32.206.0/23512HSIRogers Cable Inc. NFCB (C02172305) · CAReassignedMar 3, 2009abuse@rogers.com
via ROGERS-CAB-HSD

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
Stable
First seen
Jul 2022
Current origin since
Jul 2022 · 4.4 yr
Origin networks
1