<html><head><meta http-equiv="content-type" content="text/html; charset=us-ascii"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Hi Rob,<div><br></div><div>The root cause of this issue is not Microsoft, however it appears to be an issue within the TPG network. This route is not active within AS4826, however TPG believes we are advertising it to them - which we are not, nor have we ever.</div><div><br></div><div>We are escalating it within TPG now for them to check.</div><div><br></div><div>Regards,</div><div>Phil</div><div>AS4826<br><div><br><blockquote type="cite"><div>On 26 Jan 2023, at 4:15 pm, Rob Thomas <xrobau@gmail.com> wrote:</div><br class="Apple-interchange-newline"><div><div dir="ltr">Looks like you've typo'ed a BGP announcement - you're announcing <a href="http://104.0.0.0/13">104.0.0.0/13</a> into the DFZ, but you SHOULD be announcing <a href="http://104.40.0.0/13">104.40.0.0/13</a> - This is breaking everyone that isn't doing RPKI.<div><br></div><div>AT&T AS7018 have <a href="http://104.0.0.0/12">104.0.0.0/12</a> with a real ROA.</div><div><br></div><div>--Rob</div><div><br></div></div>
_______________________________________________<br>AusNOG mailing list<br>AusNOG@ausnog.net<br>https://lists.ausnog.net/mailman/listinfo/ausnog<br></div></blockquote></div><br></div></body></html>