4 ms·
I certainly hope not. I'm not going to argue that this was anything but a disappointment to our customers - and one that we're eager to prevent from happening
by ethomson 8y ago
I certainly hope not. I'm not going to argue that this was anything but a disappointment to our customers - and one that we're eager to prevent from happening again.
But we have never said that this was Azure's fault. It wasn't. We've put the blame where it belongs: on us. We're nearly done writing up the root cause analysis and an analysis of our next steps to prevent this from happening in the future.
- Someone1234 8y agoDo you happen to know where the root cause analysis will be posted if it is made public?
- ethomson 8y agoIt will be on our service availability blog: https://blogs.msdn.microsoft.com/vsoservice/ https://blogs.msdn.microsoft.com/vsoservice/, and I'll reply here with a direct link once it's online.
- ethomson 8y agoUpdate: the Director of Engineering for Azure DevOps has posted this. https://blogs.msdn.microsoft.com/vsoservice/?p=17485 https://blogs.msdn.microsoft.com/vsoservice/?p=17485
- GordonS 8y ago3 weeks ago there was a different outage that meant no hosted build agents were working in the west europe region, and it lasted for more than 24 hours. Now, what I hated the most about this was the communication - there wasn't any. Why not email impacted users to let them know you're aware and working on a fix?
- ethomson 8y agoYou can subscribe to get emails for availability incidents on our service availability blog, https://blogs.msdn.microsoft.com/vsoservice/ https://blogs.msdn.microsoft.com/vsoservice/ (it's in the right-hand sidebar).
- GordonS 8y agoHuh, I hadn't noticed that - I've subscribed now. I do still think it would be better if you proactively sent out emails only to affected customers though.