3 ms·
If not a configuration issue, care to speculate what actually happened? There could've been malicious intent, whether on the part of an internal or external act
by JMTQp8lwXL 8y ago
If not a configuration issue, care to speculate what actually happened? There could've been malicious intent, whether on the part of an internal or external actor --and it really could be either-- given the amount of criticism Facebook has drawn in the past few years. But perhaps Facebook's PR statement would've addressed that, had it been the case.
- ajsharp 8y agoThese are basically my thoughts on it: https://twitter.com/ajsharp/status/1106308735142526976 https://twitter.com/ajsharp/status/1106308735142526976. Normally, this level of outage would come with a technical post-mortem. Instead, they issue a super vague statement.
- nuclear_eclipse 8y agoWe likely won't even have an internal post-mortem for at least a couple weeks. There's no way you can possibly expect a full breakdown of what went wrong at this scale less than 24 hours after it gets resolved.
- ajsharp 8y agoGoogle managed to put one together in a little over a day: https://status.cloud.google.com/incident/storage/19002 https://status.cloud.google.com/incident/storage/19002.
- ceejayoz 8y agoExpectations are vastly different for a business-focused hosting platform with SLAs than a social network.