We had a brief downtime of about 5 minutes on Tuesday 2019-04-16 16:30Z because awstats suddenly broke. There were hundreds of awstats processes started by cron, consuming RAM, CPU and IOPS. I killed them all and disabled the cron job locally.
Trying to run the command manually, it seems to use very little CPU/IO and process super super slowly. Possibly something changed in the DNS service it uses to resolve the IP addresses. It also complaints about ipv6 plugin is not present or enabled, but that's likely unrelated.
Both ipv6 and ipv4 seem to work okay (tested with ping4 and ping6 from my laptop).