Data as of Nov 20, 2026

173.35.207.0/24

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

Exits seen per day

6.0K observations

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • 9HTTP
  • AETHYN_BASIC
  • APROXY
  • ASHBURNPROXIES
  • BestProxy
  • ByteProxies
  • CROXY
  • Decodo
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FastProxy
  • GEEKPROXY_TURBO
  • GloryCloud
  • IPMUSK
  • IPRoyal
  • KocerRoxy
  • LUMIPROXY
  • LemonBright
  • LudaxProxy
  • NSocks
  • NiuProxy
  • NovaProxy
  • Oxylabs
  • PROXIWARE_ECO
  • PROXYSCRAPE
  • PROXY_CC
  • Proxies.fo
  • Proxiware
  • Proxy302
  • ProxyEmpire
  • ProxyWing
  • Q2IP
  • RainProxy
  • Shifter
  • Smartproxy
  • ThunderProxy
  • VitalExclusive
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

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.35.206.0/23512HSIRogers Cable Inc. YM (C02173982) · 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
Sep 2021
Current origin since
Sep 2021 · 5.2 yr
Origin networks
1