Data as of Nov 19, 2026

173.33.151.0/24

7 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
7
2.7% of its addresses · 30 days
Always-on exits
1
14% of its exits
Providers
29
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

5.9K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CoreProxy
  • DataImpulse
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • Geonode
  • GonzoProxy
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyWing
  • Proxyma
  • Thordata
  • ThunderProxy
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
173.32.0.0/14
since Aug 2008
AS812Residential6,829
1,040 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.33.150.0/23512HSIRogers Cable Inc. AJAX (C02170375) · 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
Oct 2020
Current origin since
Oct 2020 · 6.1 yr
Origin networks
1