Data as of Nov 14, 2026

142.166.20.0/24

14 residential-proxy exits · 30 days

Bell Canada

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low
Proxy exits nearby

Residential-proxy exits

Proxy exits
14
5.5% of its addresses · 30 days
Always-on exits
4
29% of its exits
Providers
66
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

9.6K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonode
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NextProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PrivateByte
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • RainProxy
  • RapidProxy
  • Shifter
  • StrikeProxy
  • SwiftProxy
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • Thordata
  • ThunderProxy
  • TrueProxies
  • VantageProxies
  • VitalExclusive
  • YumiProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
142.166.0.0/16
since Aug 2016
AS855Residential832
57 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.20.0/24256HSE-DYNAMIC-1769443968-CASympatico HSE (C11487009) · 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
Stable
First seen
Oct 2025
Current origin since
Oct 2025 · 1.1 yr
Origin networks
1