This issue was related to this issue:
The site’s cache was recently upgraded as part of the effort to improve performance. The new cache needed some tweaking to get working properly. The tweaks have been made and we should be in good shape moving forward, but I’m still tracking this.