Azure DevOps experienced a 2.3-hour minor incident where a network infrastructure issue caused intermittent 429 (Too Many Requests) errors for workloads in the East US and East US 2 regions. All major components were affected, including Pipelines, Repos, Boards, Artifacts, Test Plans, and Core Services. The errors were not caused by customer traffic levels, and engineering teams worked to resolve the issue while advising customers to shift workloads to other regions or implement retries as a workaround.
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.
There's active incident affecting network infrastructure which is intermittently causing 429 (Too Many Requests) responses for Azure DevOps customers with workloads originating in or targeting the East US/East US2 regions.
Engineering teams are working on mitigating the issue. In the meantime, customers can move workloads to other regions or utilize retries to complete their operations.
The 429 responses are not directly related to individual customer-generated traffic.
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