outages.live
Live

Azure DevOps

Azure DevOps is reporting degraded

Checked Degraded

Service maintenance is in effect

Service maintenance is in effect

Azure DevOps reports degraded service in the Australia region. The provider is investigating the problem. No cause or workaround is available at this time.

Degraded

User reports

What people told outages.live in the last 24 hours, reviewed before it shows. Not from the Azure DevOps status page.

No reviewed reports in the last 24 hours.

History

90 days agoToday

outages.live tracks Azure DevOps since . The days before that show only what Azure DevOps published.

Incidents in 90 days

1

Days with an incident

1

Median duration

No data

Longest incident

No data

Components

56

Core services

United States Operational
90 days agoNo incidentsToday
Canada Operational
90 days agoNo incidentsToday
Brazil Operational
90 days agoNo incidentsToday
Europe Operational
90 days agoNo incidentsToday
United Kingdom Operational
90 days agoNo incidentsToday
Asia Pacific Operational
90 days agoNo incidentsToday
Australia Degraded
90 days ago1 day with an incidentToday
India Operational
90 days agoNo incidentsToday

Boards

United States Operational
90 days agoNo incidentsToday
Canada Operational
90 days agoNo incidentsToday
Brazil Operational
90 days agoNo incidentsToday
Europe Operational
90 days agoNo incidentsToday
United Kingdom Operational
90 days agoNo incidentsToday
Asia Pacific Operational
90 days agoNo incidentsToday
Australia Operational
90 days agoNo incidentsToday
India Operational
90 days agoNo incidentsToday

Repos

United States Operational
90 days agoNo incidentsToday
Canada Operational
90 days agoNo incidentsToday
Brazil Operational
90 days agoNo incidentsToday
Europe Operational
90 days agoNo incidentsToday
United Kingdom Operational
90 days agoNo incidentsToday
Asia Pacific Operational
90 days agoNo incidentsToday
Australia Operational
90 days agoNo incidentsToday
India Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

No incident in the last 90 days.

Affected components

1
  • AustraliaCore servicesDegraded

Follow Azure DevOps

Your coding agent knows when Azure DevOps is down, and tells you when a failure is theirs, not yours. You can also get Azure DevOps incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "azuredevops" and tell me if Azure DevOps has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=azuredevops
Slack
/feed subscribe https://outages.cc/feed.xml?providers=azuredevops

Go from tracking outages to fixing production issues with Polylane.

Try Polylane