Data as of Nov 17, 2026

142.166.156.0/24

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

Exits seen per day

1.3K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • CoreProxy
  • DataImpulse
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonode
  • GonzoProxy
  • IPRoyal
  • Infatica
  • KocerRoxy
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • RainProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalData
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
142.166.0.0/16
since Aug 2016
AS855Residential924
38 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.156.0/24256HSE-DYNAMIC-1769438295-CASympatico HSE (C11486818) · CAReassignedJan 26, 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
Rotating
First seen
Nov 2005
Current origin since
Nov 2025 · 1.0 yr
Origin networks
2
Last change of origin
Nov 2025
Recorded history

History

Handoffs
1