Yes. A similar Analytics outage has previously caused Azure DevOps Boards → Analytics to fail with TF400893: Unable to contact the server, and the accepted guidance in that case was that it was a current service issue under investigation.
For Velocity and Burndown widgets specifically, both rely on Analytics data:
- In-context reports such as team velocity and sprint burndown derive data from Analytics.
- The newer Sprint Burndown widget also uses Analytics.
Given that the issue is happening across multiple projects and only affects Velocity and Burndown widgets, that pattern is consistent with an Analytics service problem rather than a single-project dashboard configuration issue.
Practical checks:
- Open a project and go to Boards → Analytics.
- If Analytics pages also fail or show no data, that further points to an Analytics-side issue.
- Check whether only Analytics-backed widgets are affected.
- If non-Analytics dashboard widgets still work, that strengthens the same conclusion.
- If the issue is transient, it may resolve without manual intervention.
- There is no supported way to manually re-initialize or rebuild Azure DevOps Analytics data.
References: