Data as of Nov 10, 2026

142.167.68.0/24

7 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
7
2.7% of its addresses · 30 days
Always-on exits
2
29% of its exits
Providers
37
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

2.4K observations

Proxy providers listing exits

  • Ake.net
  • AnyIP
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GloryCloud
  • GonzoProxy
  • HydraProxy
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • RainProxy
  • ThunderProxy
  • TrueProxies
  • VantageProxies
  • VitalData
  • VitalExclusive
  • ZENPROXY_LITE

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.68.0/24256HSE-DYNAMIC-1771429266-CASympatico HSE (C11516685) · CAReassignedFeb 18, 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
Feb 2026
Current origin since
Feb 2026 · 9 mo
Origin networks
1