Previous incidents

After an investigation, we have determined that the reason for this issue was a firewall rule that got triggered after an influx of suspicious requests. This was fixed by revising the rule, and by adding further upstream filtering/ddos protection.