Data as of Nov 12, 2026

70.31.8.0/22

11 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
11
1.1% of its addresses · 30 days
Spread
4 of 4
/24s with at least one exit
Providers
56
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

15K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
70.31.10.0/2404
70.31.11.0/2403
70.31.8.0/2402
70.31.9.0/2402

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • AnyIP
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonode
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • IPMUSK
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • Maskify
  • MoMoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • PrivateByte
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • Q2IP
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • TrueProxies
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
70.31.0.0/16
since Jan 2009
AS577Residential2,046
134 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
70.24.0.0/13524,288BELLCANADA-18Bell Canada (LINX) · CADirect AllocationJan 28, 2008abuse@bellnexxia.net
└ 70.31.8.0/221,024HSE-DYNAMIC-1641910281-CASympatico HSE (C08160199) · CAReassignedJan 11, 2022abuse@bellnexxia.net
via BELLCANADA-18

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
Reactivated
First seen
Jun 2012
Current origin since
Jan 2022 · 4.8 yr
Origin networks
2
Last change of origin
Jan 2022
Recorded history

History

Handoffs
1