[Outages-discussion] Azure Outageks

[Matt Hoppes]

Yes, neither of those are acceptable explanation is for a data center of this size going off-line for 37 hours.

> On Sep 5, 2018, at 22:14, James <jamesam at gmail.com> wrote:
> 
> Their infrastructure didn’t failover as consumers thought, or it didn’t failover as planned.  Probably hadn’t tested/planned for this possibility.
> 
>> On Wed, Sep 5, 2018 at 8:25 PM <frnkblk at iname.com> wrote:
>> Do you mean more than what's been covered here?
>> https://www.datacenterdynamics.com/news/microsoft-azure-suffers-outage-after
>> -cooling-issue/
>> https://www.zdnet.com/article/microsoft-south-central-u-s-datacenter-outage-
>> takes-down-a-number-of-cloud-services/
>> 
>> Frank
>> 
>> -----Original Message-----
>> From: Outages-discussion <outages-discussion-bounces at outages.org> On Behalf
>> Of Matt Hoppes
>> Sent: Wednesday, September 5, 2018 6:09 PM
>> To: outages-discussion at outages.org
>> Subject: [Outages-discussion] Azure Outageks
>> 
>> Can anyone shed light on the nearly 37 hour Azure Outage that just happened?
>> 
>> How did this get so bad for so long?  Where was redundancy?
>> _______________________________________________
>> Outages-discussion mailing list
>> Outages-discussion at outages.org
>> https://puck.nether.net/mailman/listinfo/outages-discussion
>> 
>> 
>> _______________________________________________
>> Outages-discussion mailing list
>> Outages-discussion at outages.org
>> https://puck.nether.net/mailman/listinfo/outages-discussion
> -- 
> _
> James Mitchell
> 636-634-0196
> Jamesam at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages-discussion/attachments/20180905/e3cbe1b9/attachment.html>