Data as of Nov 11, 2026

173.34.78.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
Spread
2 of 2
/24s with at least one exit
Providers
30
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

327 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
173.34.78.0/2404
173.34.79.0/2404

Proxy providers listing exits

  • 711Proxy
  • B2Proxy
  • BuyingProxy
  • CliProxy
  • DataImpulse
  • Datarama
  • EZProxies
  • Evomi
  • FLEETPROXY
  • FastProxy
  • GloryCloud
  • IPFly
  • IPPeak
  • InfiniteProxies
  • LemonBright
  • LudaxProxy
  • MoMoProxy
  • NovProxy
  • NovaProxy
  • Novada
  • PROXYSCRAPE
  • PrivateByte
  • Proxio
  • Proxiware
  • Proxy4U
  • PuraRoute
  • RainProxy
  • RapidProxy
  • ThunderProxy
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
173.32.0.0/14
since Aug 2008
AS812Residential6,524
963 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.78.0/23512HSIRogers Cable Inc. HNSN (C02170692) · 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
Dec 2025
Current origin since
Dec 2025 · 11 mo
Origin networks
1