Data as of Nov 17, 2026

173.35.112.0/23

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

Exits seen per day

11K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
173.35.112.0/2427
173.35.113.0/2406

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYON
  • PROXYSCRAPE
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • Proxyma
  • Q2IP
  • RainProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
173.35.112.0/20
since Apr 2009
AS812Residential120
20 always on
Rogers Communications Canada Inc.
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.35.112.0/23512HSIRogers Cable Inc. POPF (C02173093) · 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 2020
Current origin since
Dec 2020 · 5.9 yr
Origin networks
1