Data as of Nov 12, 2026

159.2.51.0/24

13 residential-proxy exits · 30 days

Bell Canada

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
13
5.1% of its addresses · 30 days
Always-on exits
2
15% of its exits
Providers
57
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

6.8K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonode
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPMUSK
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • Thordata
  • ThunderProxy
  • TrueProxies
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
159.2.32.0/19
since Apr 2017
AS855Residential174
20 always on
Bell Canada

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
159.2.0.0/1665,536ALIANTBell Canada (LINX) · CADirect AllocationNov 2, 2016abuse@bellnexxia.net
└ 159.2.51.0/24256HSE-DYNAMIC-1769465385-CASympatico HSE (C11487478) · CAReassignedJan 26, 2026abuse@bellnexxia.net
via ALIANT

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
Nov 2025
Current origin since
Nov 2025 · 1.0 yr
Origin networks
1