Resolved after 3 hours 45 minutes, affecting Boards (United States) and Repos (United States) and 1 more, on September 29, 2026.
The root cause of this issue was memory exhaustion on the application servers. We collected a live memory dump during the incident and determined that the issue is triggered by a specific data pattern that exposes a product defect, resulting in excessive memory consumption. Our engineers have identified the underlying bug and are working on a fix to prevent this condition from occurring in the future.
Affected components
Update timeline
- identified Sep 29, 2026, 12:56 PM UTC
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.
- identified Sep 29, 2026, 02:05 PM UTC
Our engineers are actively working to understand and mitigate the issue, while continuing recovery efforts to reduce customer impact.
- identified Sep 29, 2026, 04:41 PM UTC
Customer impact has been mitigated. The incident will remain open while our engineers continue their investigation to better understand the underlying cause.
- identified Sep 29, 2026, 06:41 PM UTC
The issue is now fully mitigated. 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.
- resolved Sep 29, 2026, 07:29 PM UTC
The root cause of this issue was memory exhaustion on the application servers. We collected a live memory dump during the incident and determined that the issue is triggered by a specific data pattern that exposes a product defect, resulting in excessive memory consumption. Our engineers have identified the underlying bug and are working on a fix to prevent this condition from occurring in the future.
Your product runs on more than Azure DevOps
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services