We have investigated and the cause of the problem was a temporary storage issue which has since been resolved.

We are taking steps to improve as well as fix the monitoring where this happened and make sure such an issue does not occur again.