Data as of Nov 20, 2026

134.41.190.0/24

4 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
4
1.6% of its addresses · 30 days
Providers
21
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

272 observations

Proxy providers listing exits

  • 711Proxy
  • B2Proxy
  • DataImpulse
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FloppyData
  • IPMUSK
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LudaxProxy
  • MangoProxy
  • NiuProxy
  • NovaProxy
  • ProxyEmpire
  • RainProxy
  • RapidProxy
  • SCRAPELESS
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
134.41.0.0/16
since Nov 2016
AS855Residential2,216
102 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.190.0/24256HSE-DYNAMIC-1769463147-CASympatico HSE (C11487344) · 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
Oct 2025
Current origin since
Oct 2025 · 1.1 yr
Origin networks
1