Data as of Nov 16, 2026

173.32.58.0/23

8 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
8
1.6% of its addresses · 30 days
Always-on exits
1
13% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
33
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

4.8K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
173.32.58.0/2417
173.32.59.0/2401

Proxy providers listing exits

  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GhostConnect
  • GloryCloud
  • IPFly
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • LudaxProxy
  • MoMoProxy
  • NovProxy
  • NovaProxy
  • Proxiware
  • Proxy302
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
173.32.0.0/14
since Aug 2008
AS812Residential6,761
989 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.58.0/23512HSIRogers Cable Inc. ETOB (C02173256) · 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
Apr 2020
Current origin since
Oct 2023 · 3.1 yr
Origin networks
1