Can confirm we started seeing these errors on shard n185 today during a deployment.
We started receiving HTTP 502 errors beginning at UTC 2020-01-29T23:52:36.8973977Z.
Further attempts started working around 2020-01-30T06:29:40.0682225Z UTC - so it would have been fixed sometime between those two times.
Hope this helps - I've also logged a case.