LAYER3 INTEL
Get started
Sign in
Data as of Nov 12, 2026

208.68.32.0/22

11 residential-proxy exits · 30 days

Wightman Telecom

Announcement
this exact prefix
No RPKI
Announced by
AS29974
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
11
1.1% of its addresses · 30 days
Always-on exits
1
9.1% of its exits
Spread
3 of 4
/24s with at least one exit
Providers
52
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

11K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
208.68.35.0/2415
208.68.32.0/2403
208.68.34.0/2403

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • Geonode
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • IPFly
  • IPMUSK
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonBright
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NodeMaven
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_LITE

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
208.68.32.0/221,024WIGHTMAN-08Wightman Telecom (WIGHT) · CADirect AllocationAug 27, 2012abuse@wightman.ca
└ 208.68.32.8/298CW-WIGHTMANunknown———

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Jun 2006
Current origin since
May 2026 · 6 mo
Origin networks
3
Last change of origin
May 2013
Recorded history

History

Handoffs
2