Azure DevOps Service Status
We have a team of engineers around the world who look after the health of Azure DevOps 24 hours a day. Their primary goal is to ensure that our users are productive and successful with our service at all times. From time to time, like any online service, our service experiences performance slowdowns and stability issues. In these cases, we aim to respond quickly to restore the service, and also make it a top priority to communicate the incident status and our next steps to mitigate the issue on the Azure DevOps Service Status Portal.
If you are experiencing a problem with any of our Azure DevOps services, you can check the service health to determine if we are already working on the issue before you contact our support team or spend time troubleshooting. Many of the events we post here are based on our Customer Impact Assessment (CIA). CIA is modeled on the same telemetry we use in our availability model that measures real customer representing both reliability and performance.
The severity of a service health event is based on the number of customers affected by the issue. Typically, the highest severity events impact a large percentage of our customers and render some parts of the product unusable. These events are represented as "Unhealthy" in the service status portal. Lower severity events affect the performance of a specific feature in a service but does not make the service broadly unavailable. These events are reflected as "Degraded" in the service status portal.
Services in a Product Suite
Azure DevOps is a product suite of service offerings. For more information about pricing and acquisition, see the pricing and acquisition page for more information on how to access different services in the suite. The geographic region is indicative of where the user's account is hosted in the cloud and the data residency, sovereignty, compliance, and resilience requirements are honored within the geographical boundaries.
In addition to the list of specific Azure DevOps services, the matrix also displays two other categories: Core and Other. The Core category encompasses the set of features that are fundamental to all five services, such as authentication or the web portal. The Other category is the list of features that complement the suite, such as extensions.
Service Health Portal
Service Health Matrix
The service status portal provides a two-dimensional matrix view of active events mapped to a given service and geography. To help clarify which specific aspects of the service are affected, we communicate impact of each of these services by geographic region in the service matrix.
More information on active events are found in the form of an "event log" that's displayed on the top of the service health matrix. Each log will have additional associated information in the form of the impacted service and geography as well as the duration of a specific event. You can click through the provided hyperlink to navigate into the event log, which provides detailed information on the event being investigated.
The Status history section provides a view into current active events as well as past events. You can also filter the logs to adjust the scope of your search into past events. In addition, you can use the REST API build automated alerting solutions to help you stay on top of events with Azure DevOps services.
You can use the RSS feed to subscribe and receive information in your feed reader.
Using REST APIs
For users who are looking to build an automated solution to monitor the infrastructure incidents, we provide REST APIs to retrieve the current health status of each of the Azure DevOps services.
Looking for Azure DevOps REST APIs? See the newest Azure DevOps REST API reference. api-version = 5.1
For information about .NET client libraries, see .NET client libraries for Azure DevOps (and TFS).
If you're experiencing an issue with Azure DevOps and see a corresponding event communicated on the service health portal,be assured that we're working to restore normal operations of the service. You don't need to take any further action to notify us. However, if you don't see your issue reported on the Azure DevOps service health page, refer to the resources available on Azure DevOps support page. That page has resources to report bugs, interact with a friendly support bot, and contact our support team for additional assistance.