<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Helvetica,sans-serif">
<p>Microsoft have publically and openly acknowledged that they had an issue yesterday with their network platform.</p>
<p><br>
</p>
<p>The fact that you did not receive calls from your customers may not necessarily indicate the absence of an issue; in fact, I'd say it indicates an increasing acknowledgement and (sadly) acceptance of outages with cloud services in general. What would have
once resulted in system admins and support staff getting strips torn off them for services being down is now met with little more than a knowing nod and "Ahhh. We should let the team know about that".</p>
<p><br>
</p>
<p>It's also worth noting that direct connectivity to Azure or AWS is great for some businesses, but not applicable or suitable for others - nor is it a guarantee of being unaffected by these kind of issues. As an example, <span style="font-size:12pt">a small
5 person business that relies on 365 for email hosting cannot</span><span style="font-size:12pt">, and should not have to, in most cases procure an ExpressR</span><span style="font-size:12pt">oute just to get connectivity to their email or presence platform</span><span style="font-size:12pt">.</span></p>
<p><span style="font-size:12pt"><br>
</span></p>
<p><span style="font-size:12pt">But hey, that's what happens when you put all your eggs on someone elses computer(s).</span></p>
<p><br>
</p>
<p><span style="font-size:12pt">Regards,</span><br>
</p>
<p>-Brad.</p>
<p><br>
</p>
<p><br>
</p>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> AusNOG <ausnog-bounces@lists.ausnog.net> on behalf of Chad Kelly <chad@cpkws.com.au><br>
<b>Sent:</b> Thursday, 21 November 2019 11:53:30 AM<br>
<b>To:</b> ausnog@lists.ausnog.net<br>
<b>Subject:</b> Re: [AusNOG] Microsoft cloud issues?</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">On 11/21/2019 12:00 PM, ausnog-request@lists.ausnog.net wrote:<br>
<br>
> We just had a 8 hour issue with no emails yesterday<br>
<br>
I was at the Microsoft Head Office in Melbourne yesterday and was still <br>
able to recieve mail fine.<br>
<br>
I'd say some of these issues were specific to certain networks.<br>
<br>
I didn't get any urgent calls from customers either.<br>
<br>
Microsoft have connectivity directly with most ISPs in Au now a days. <br>
I'd suggest not relying on free peering.<br>
<br>
I'd get direct connectivity.<br>
<br>
As for Teams for corporate use I would suggest running a Hybrid Cloud <br>
environment for it.<br>
<br>
I did notice some delays to email on Tuesday night but none of our stuff <br>
was down totally.<br>
<br>
Regards Chad.<br>
<br>
<br>
<br>
<br>
-- <br>
Chad Kelly<br>
Manager<br>
CPK Web Services<br>
Phone 03 5273 0246<br>
Web <a href="http://www.cpkws.com.au">www.cpkws.com.au</a><br>
<br>
_______________________________________________<br>
AusNOG mailing list<br>
AusNOG@lists.ausnog.net<br>
<a href="http://lists.ausnog.net/mailman/listinfo/ausnog">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
</div>
</span></font>
</body>
</html>