Data as of Nov 19, 2026

142.166.140.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
Providers
57
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

5.6K observations

Proxy providers listing exits

  • 711Proxy
  • AETHYN_BASIC
  • AETHYN_ELITE
  • Ake.net
  • AnyIP
  • B2Proxy
  • BUYPERSONALPROXY
  • BottingTools
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLEETPROXY
  • FastProxy
  • FlexyProxies
  • FloppyData
  • GEEKPROXY_TURBO
  • GSocks
  • GhostConnect
  • GloryCloud
  • HASDATA
  • IP2WORLD
  • IPFly
  • IPMUSK
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LITPORT_LIMA
  • LOKIPROXY
  • LemonBright
  • LudaxProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PROXIWARE_ECO
  • PROXYSAVER
  • PROXYSCRAPE
  • PYPROXY
  • Proxiware
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • Shifter
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
142.166.0.0/16
since Aug 2016
AS855Residential981
21 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.166.0.0/1665,536SNI1-BELL-ALIANT-166Bell Canada (LINX) · CADirect AllocationAug 26, 1992abuse@bellnexxia.net
└ 142.166.140.0/24256HSE-DYNAMIC-1771429505-CASympatico HSE (C11516691) · CAReassignedFeb 18, 2026abuse@bellnexxia.net
via SNI1-BELL-ALIANT-166

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