Data as of Nov 19, 2026

173.34.178.0/23

11 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
11
2.1% of its addresses · 30 days
Always-on exits
1
9.1% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
54
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

9.3K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
173.34.178.0/2415
173.34.179.0/2406

Proxy providers listing exits

  • 2Captcha
  • AETHYN_BASIC
  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GEEKPROXY_TURBO
  • GSocks
  • GloryCloud
  • GonzoProxy
  • IP2WORLD
  • IPFly
  • IPOasis
  • Infatica
  • KocerRoxy
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXIWARE_ECO
  • PROXYSCRAPE
  • PYPROXY
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • ZENPROXY_LITE

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.34.178.0/23512HSIRogers Cable Inc. GRNSBR (C02171213) · 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
Mar 2024
Current origin since
Mar 2024 · 2.7 yr
Origin networks
1