502 (Bad Gateway)

This is a reoccurrence of an earlier issue resulting in 502 (Bad Gateway) errors when trying to download packages and artifacts. We are in contact with the corresponding networking team to mitigate the issue.

The issue is now fully mitigated. By taking the faulty machines offline, we were able to restore the traffic.

Our engineers will be investigating this further to learn from and reduce the risk of potential recurrences. We apologize for the impact this had on our customers.

We have identified that the issue is within one of our internal partners, Azure Front Door. Two faulty machines responsible for routing incoming traffic to the proper destination are causing these disruptions.

The problem appears to be intermittent in some cases, so we recommend that our customers retry if that is a feasible alternative.

Our engineers are diligently working to restore the affected machines and mitigate the issue. We apologize for any inconvenience this may be causing to our customers.

Our engineers continue working to understand this network issue and mitigate it.

Our engineers are currently investigating an event impacting Azure DevOps. There are 502 (Bad Gateway) errors occurring when trying to download packages and artifacts.

The event is being triaged and we will post an update as soon as we know more.