Data as of Nov 10, 2026

142.167.178.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
1
7.7% of its exits
Providers
40
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

1.7K observations

Proxy providers listing exits

  • 911Proxy
  • BestProxy
  • BlurPath
  • BottingTools
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FLEETPROXY
  • FastProxy
  • FloppyData
  • GSocks
  • GloryCloud
  • IPFly
  • IPMUSK
  • IPPeak
  • LUMIPROXY
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NSocks
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • ProxyEmpire
  • ProxyGeo
  • PuraRoute
  • RainProxy
  • RapidProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • SwiftProxy
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
142.167.0.0/16
since Aug 2016
AS855Residential1,750
244 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
142.167.0.0/1665,536SNI1-BELL-ALIANT-167Bell Canada (LINX) · CADirect AllocationAug 26, 1992abuse@bellnexxia.net
└ 142.167.178.0/24256HSE-DYNAMIC-1769438551-CASympatico HSE (C11486826) · CAReassignedJan 26, 2026abuse@bellnexxia.net
via SNI1-BELL-ALIANT-167

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