Unless my memory tricks me, a few days ago the % answered was around 74%, and the next it drops to 63%. Any reason why?
There was a bug in the algorithm that calculates
IsAnswered. That field is used to calculate the % answered value.
The bug is now gone as of two days ago:
I've updated the query to check for nulls on the IsAnswered field - this will be deployed in the next build (rev 2014.6.16.1659, meta rev 2014.6.16.2312).
The query runs on a daily schedule, so may be a day or two before it kicks off.
(from Oded's answer)
Since this was fixed, our % answered is now... correct.