Data as of Nov 19, 2026

134.41.250.0/24

16 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
16
6.3% of its addresses · 30 days
Providers
49
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

9.2K observations

Proxy providers listing exits

  • AETHYN_ELITE
  • Ake.net
  • AnyIP
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • FLEETPROXY
  • FastProxy
  • GSocks
  • GloryCloud
  • IPFly
  • IPMUSK
  • IPPeak
  • Infatica
  • KocerRoxy
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NextProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PROXORA
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • Q2IP
  • RH7Proxy
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
134.41.0.0/16
since Nov 2016
AS855Residential2,204
106 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
134.41.0.0/1665,536ALIANTBell Canada (LINX) · CADirect AllocationNov 8, 2016abuse@bellnexxia.net
└ 134.41.250.0/24256HSE-DYNAMIC-1769461450-CASympatico HSE (C11487230) · 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
Dec 2025
Current origin since
Dec 2025 · 12 mo
Origin networks
1