Azure DevOps Services status
Azure DevOps Services
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 customers are always productive and successful with our service. 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. It's our top priority to communicate the incident status and our next steps to mitigate the issue. We do so through the Azure DevOps Services status portal.
If you're experiencing a problem with any of our Azure DevOps Services, you can check the service health to determine if we're already working on the issue. Many of the events we post are based on our Customer Impact Assessment (CIA). The CIA is modeled after our availability model that measures real customer experiences representing both reliability and performance.
Services within the product suite
Azure DevOps is a product suite of service offerings. The geographic region indicates where an organization is hosted in the cloud. The data residency, sovereignty, compliance, and resilience requirements are honored within the geographical boundaries.
In addition to the 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 corresponds to features that complement the suite, such as extensions.
For more information about pricing and acquisition, see the pricing and acquisition page.
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.
Service health indicators
The Azure DevOps Services status portal indicates the status of Azure DevOps Services according to the following indicators. These indicators reflect the severity of a service health event 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.
- Healthy: Indicates the service is broadly available.
- Degraded: Indicates a lower-severity event that affects the performance of a service feature, but doesn't impact broad service availability.
- Unhealthy: Indicates a high-severity event that affects the performance of a service and its broad availability.
- Advisory: Indicates that a service is under investigation to determine the performance and availability impact.
Service status and event logs
You can access more information on active events from the Status history page. This page provides a view into current active events and past events. Eave event under investigation or previously investigate is logged in the form of an event log. Each log has other associated information such as the impacted service,
geography, and event duration. Choose the provided hyperlink to view the event log, which provides detailed information on the event under investigation.
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.
When and how to report availability issues
If you're experiencing an issue with Azure DevOps and see a corresponding event that's communicated on the service health portal, we're already working to restore normal operations of the service. You don't need to do anything else to notify us.
However, if you don't see your issue reported on the Azure DevOps Services health page, you can ask a question through the Azure DevOps Services virtual support agent.
For issues not related to availability, refer to our Developer Community portal.
You can use the RSS feed to subscribe and receive information in your feed reader.
Use REST APIs to build automated solutions
Looking for Azure DevOps REST APIs? See the latest Azure DevOps REST API reference.
For information about .NET client libraries, see .NET client libraries for Azure DevOps.
Submit and view feedback for