Data as of Nov 19, 2026

173.35.112.0/20

121 residential-proxy exits · 30 days

Rogers Communications Canada Inc.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
121
3.0% of its addresses · 30 days
Always-on exits
21
17% of its exits
Spread
16 of 16
/24s with at least one exit
Providers
116
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

133K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • 9HTTP
  • 9Proxy
  • AETHYN_ELITE
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • HASDATA
  • IP2WORLD
  • IPFly
  • IPMUSK
  • IPOasis
  • IPPeak
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • JoyProxy
  • KindProxy
  • KocerRoxy
  • Kookey
  • LUMIPROXY
  • LemonBright
  • LemonLabs
  • LightningProxies
  • LudaxProxy
  • MagneticProxy
  • MangoProxy
  • MarsProxies
  • MoMoProxy
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXIWARE_ECO
  • PROXORA
  • PROXYON
  • PROXYSCRAPE
  • PROXY_CC
  • PYPROXY
  • PacketStream
  • PrivateProxy
  • Proxies.fo
  • Proxio
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyStyler
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • RoamProxy
  • RolaProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

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.
Nesting

More-specifics by size

Sized by addresses, colored by each announcement's type. Click a tile with children to zoom in, a leaf to open it.
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
173.35.112.0/23
since Dec 2020
AS812Residential13
2 always on
Rogers Communications Canada Inc.
173.35.114.0/23
since Dec 2020
AS812Residential20
3 always on
Rogers Communications Canada Inc.
173.35.116.0/23
since Dec 2020
AS812Residential15
4 always on
Rogers Communications Canada Inc.
173.35.118.0/23
since Dec 2020
AS812Residential8
2 always on
Rogers Communications Canada Inc.
173.35.120.0/23
since Feb 2021
AS812Residential11
1 always on
Rogers Communications Canada Inc.
173.35.122.0/23
since Oct 2023
AS812Residential19
1 always on
Rogers Communications Canada Inc.
173.35.124.0/23
since Oct 2023
AS812Residential17
3 always on
Rogers Communications Canada Inc.
173.35.126.0/23
since Apr 2021
AS812Residential17
5 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
└ 173.35.114.0/23512HSIRogers Cable Inc. POPF (C02173094) · CAReassignedMar 3, 2009abuse@rogers.com
via ROGERS-CAB-HSD
└ 173.35.116.0/23512HSIRogers Cable Inc. POPF (C02173095) · CAReassignedMar 3, 2009abuse@rogers.com
via ROGERS-CAB-HSD
└ 173.35.118.0/23512HSIRogers Cable Inc. POPF (C02173096) · 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
Apr 2009
Current origin since
Apr 2009 · 18 yr
Origin networks
1