Azure DevOps·6 Nov 2026 · 10:31 UTCResolvedHigh priority

Azure DevOps Artifacts degraded by Maven Central throttling

Azure DevOps Artifacts users in India encountered package retrieval failures as requests to Maven Central were throttled with HTTP 429 responses. The incident lasted nearly two days.

Reported duration1d 21h 26m
Impact scopeRegional
Incident categoryDeveloper platforms / package registry

Calculated from 10:31 UTC Nov 6 to 07:57 UTC Nov 8.

WHAT HAPPENED

Incident summary

Azure DevOps Artifacts users in India encountered package retrieval failures as requests to Maven Central were throttled with HTTP 429 responses. The incident lasted nearly two days.

The status mirror reported hundreds of thousands of failed Maven Central calls affecting dozens of organizations, feeds and users. The incident ended on Nov 8 after mitigation.

ROOT CAUSE

What the provider reported

Microsoft said outbound traffic to Maven Central was reduced on two hot paths to get below the upstream throttling limit. Requests were still being throttled after that change, according to the status update.

Editorial note: This is a concise summary of the provider’s public explanation, not an independent technical investigation.

AFFECTED SURFACE

Services and systems

Azure DevOps ArtifactsIndia regionMaven package requests

Reported scope: Global / affected users

EVENT TIMELINE

Latest source updates

Showing up to the 3 latest updates available in the source record. UTC is fixed; local time is converted in this browser (your local timezone).

  1. Maven Central request failures confirmed

    The status mirror reported that Maven Central was returning 429 responses to nearly all requests from an Azure Artifacts India node, affecting organizations, feeds and users.

  2. Outbound traffic reduced

    Microsoft reported reducing outbound traffic to Maven Central in two hot paths, but throttling continued.

  3. Artifacts incident resolved

    The status mirror marked the India-region Artifacts issue resolved after approximately one day and twenty-one hours.

Latest source record: ·

COMMUNITY SIGNAL

What did this incident feel like?

React anonymously. Counts are shared across visitors and are not a measure of the number of customers affected.

Community signal
Shared anonymous reactions