Created

Between 00:01:21 and 00:02:16 UTC we experienced what appears to be a momentary blip in AWS' request routing that resulted in a small fraction of requests receiving 502 errors, which was detected by our automated monitoring. We expect the user impact to have been minimal, as client requests will have automatically retried. We are investigating what may have caused this and if any configuration changes could reduce the likelihood of this kind of issue in the future.