## Azure DevOps – Packages/Artifacts Availability Degradation Azure DevOps Artifacts in India experienced a 44.5-hour degradation after Maven Central began throttling requests from the Azure infrastructure node, returning HTTP 429 errors on 425,000 of 426,000 calls with no successful requests since 10:18 UTC on November 5. This resulted in 33,700 failed requests affecting 67 organizations, 143 feeds, and 341 users. Engineers reduced outbound traffic to Maven Central across two hot paths to get below the throttling threshold, though throttling persisted despite the significant traffic reduction.
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.
We applied changes to reduce outbound traffic to Maven Central in 2 hot paths. The goal is to get us under the throttling limit Maven Central is imposing. Despite these changes bringing traffic down significantly, we are still being throttled.
Our engineers are working to understand and mitigate the issue.
Our engineers are currently investigating an event impacting Azure DevOps. The event is being triaged and we will post an update as soon as we know more.
Maven Central returns 429s to every request from pkgs-cin-1 : 425k of 426k calls, with no successful call since 10:18 UTC on 5 Nov.
33.7k failed requests across 67 orgs, 143 feeds and 341 users.
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