Availability Degradation in all regions

Mitigation is still in progress, our engineers are engaged with the Azure Front Door team, which is performing a global rollback. The current estimate for completion is 10:30pm UTC. Thank you for your patience throughout this issue.

Mitigation is still in progress, our engineers are engaged with the Azure Front Door team, which is performing a global rollback. Currently 5% of the Azure Front Door environments have been rolled back, with a target of 50% expected within the next hour. Thank you for your patience throughout this issue.

Mitigation is in progress, our engineers are engaged with the Azure Front Door team, which is performing a global rollback that is estimated to complete in 4 hours. During this time we expect some customers to experience partial recovery. Thank you for your patience throughout this issue.

Our engineers are still actively engaged and collaborating with the Azure team on a mitigation. The Azure Front Door team is currently exploring a mitigation for a single environment to confirm the approach.
Thank you for your patience throughout this issue.

We are currently experiencing an issue that may result in self-hosted agent failures during various git operations. You may encounter errors such as:


```
error: RPC failed; curl 56 GnuTLS recv error (-54): Error in the pull function.
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: fetch-pack: invalid index-pack output
##[error]Git fetch failed with exit code: 128
```


Please note that this issue may impact customers in all regions.
Our Engineers are actively working to address this issue and mitigate its impact as quickly as possible.

Thank you for your patience and understanding.

The incident is anticipated to have a global impact, rather than being limited to a specific region. The investigation remains ongoing.

Work is still in progress. There are some paths to follow so far but mitigatios still needs further investigations.

Our engineers are still working to understand and mitigate the issue.

Our engineers are working to understand and mitigate the issue.

Our engineers are currently investigating an event impacting Azure DevOps. Users might experience slowness for boards and pipelines.
The event is under investigation and we will post an update as soon as we know more.