Fixed Spikes of 404 Errors

We have identified and fixed an issue that caused a small burst of unexpected 404 errors to happen shortly after our daily deployment.
The issue would usually happen between 12:00 and 13:00 UTC. The fix is live since February 22th 2022.


Great news.

Does this only fix 404 errors? Or would this fix also include these errors we’ve been receiving around the same times as well?

  • <ProtocolError for 502 not supported>
  • <urlopen error [Errno 54] Connection reset by peer>
  • <urlopen error [Errno 60] Operation timed out>
  • <ProtocolError for 405 Method Not Allowed>
  • <ProtocolError for 502 Bad Gateway>