Data as of Nov 15, 2026

142.166.152.0/24

8 residential-proxy exits · 30 days

Bell Canada

Announcement
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
8
3.1% of its addresses · 30 days
Always-on exits
1
13% of its exits
Providers
33
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

963 observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • GoProxies
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • NovProxy
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • Shifter
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
142.166.0.0/16
since Aug 2016
AS855Residential901
47 always on
Bell Canada

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
142.166.0.0/1665,536SNI1-BELL-ALIANT-166Bell Canada (LINX) · CADirect AllocationAug 26, 1992abuse@bellnexxia.net
└ 142.166.152.0/221,024FIBREOP-142-166-152-0-1645796979Bell Aliant / FibreOp (C08205764) · CAReassignedFeb 25, 2022abuse@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

142.166.152.0/22

Routing history

Pattern
Stable
First seen
Feb 2022
Current origin since
Feb 2022 · 4.7 yr
Origin networks
1