<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.emailquote, li.emailquote, div.emailquote
{mso-style-name:emailquote;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:1.0pt;
border:none;
padding:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal-compose;
font-family:"Times New Roman",serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-NZ" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Well it seems that persistence pays.<br>
<br>
NTT now peer across Sydney with Azure.<br>
<br>
Now MSN have updated their routes.<br>
<br>
Hope this improves the general situation for connectivity in Sydney.<br>
<br>
Chris<br>
<br>
-----Original Message-----<br>
From: Chris O'Donoghue <br>
Sent: Monday, 26 March 2018 2:09 PM<br>
To: 'ausnog@lists.ausnog.net' <ausnog@lists.ausnog.net><br>
Subject: MSN (Azure) and NTT peering in Sydney<br>
<br>
Hi all,<br>
<br>
I'm the Ops human for a small AU cloud SaaS provider.<br>
<br>
Some of our infrastructure runs on Dimension Data's cloud while the vast majority runs in Azure.<br>
<br>
The network connectivity between these networks has been pretty poor.<br>
<br>
At first we asked NTT to optimize their path between NTT and MSN as both the forward and reverse path was tromboning, with the path between NTT -> Azure going via Perth, Singapore and Tokyo before returning to Sydney.<br>
We still have the forward path tromboning via Singapore and Tokyo.<br>
<br>
Q: are there any MSN network techs on this list who can assist with fixing this?<br>
<br>
Cheers<br>
<br>
Chris<o:p></o:p></p>
</div>
</body>
</html>