Azure DevOps users experienced intermittent 500 failures for Maven packaging operations in Azure Artifacts when feeds were configured to upstream to Maven Central, affecting multiple regions globally. The issue was caused by traffic volume and limit problems with the Maven Central upstream provider. The incident lasted 1.7 hours and was resolved through engagement between the Azure Artifacts engineering team and the public package provider to address the traffic constraints.
Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
Users may experience intermittent impact for Maven-related Azure Artifacts operations.
Specifically, when the feed upstreams to Maven Central, operations that trigger upstream traffic _may_ see an intermittent failure (500). If your feed _does not_ currently need to retrieve packages from the Maven Central upstream, you can avoid the impact by removing the upstream from your feed.
The Azure Artifacts engineering team is engaging with the public package provider to address traffic volumes and limits.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with