I have been seeing this error a lot lately.
We have looked at the requests in question and everything looks OK on our end, maybe a communication hiccup between us and your browser. We have added logic which will try to recover from that state. Thanks for the heads up and let us know if you’re still experiencing issues with this.