Hiya,
In this instance, this appeared to be a temporary networking hiccup. To prevent DDoS-like scenarios, we cache this outcome under the same TTL as normal results (5mins). The message is different simply because we don't persist the error information, so when it redraws it uses the "default" no results screen.
I do not expect any one thing to be actionable here, so I am going to close this; we are aware of several systemic issues causing things like this in general that we are working on resolving.
Thank you for reporting with all the details as shown! 😃
