Service maintenance is in effect
DegradedOfficial update
0
Azure DevOps reports degraded service in the Australia region. The provider is investigating the problem. No cause or workaround is available at this time.
State
Components degraded
Started
Ongoing for
1 h 52 min
Worst impact
Degraded
Timeline
1 update16:3917:0717:3518:0318:31
DegradedUpdate postedTimes in UTC
Components degraded
1 h 52 min 100%
Updates
Times in UTCAs posted by Azure DevOps
Components degraded
Affected components
1Australia
Azure DevOps in the last 90 days
Full history90 days agoToday
Incidents in 90 days
1
Days with an incident
1
Median duration
Not enough data
This incident
Not comparable
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=azuredevopsSlack
/feed subscribe https://outages.cc/feed.xml?providers=azuredevopsFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane