We found out last night that there was a "legacy" route on zayo's side that was incorrectly routing our traffic. It seems ok now.<br><br><br>Sent from ProtonMail Mobile<br><br><br><br>-------- Original Message --------<br>On Apr 9, 2020, 14:23, Forrest Christian (List Account) < lists@packetflux.com> wrote:<blockquote class="protonmail_quote"><br><div dir="auto"><div>Replying on list...as others may be seeing something similar.</div><div dir="auto"><br></div><div dir="auto">We had a problem which started over the weekend involving Allstream.  One of their customers were announcing our prefixes, resulting in broken connectivity.  </div><div dir="auto"><br></div><div dir="auto">I ended up calling the Zayo NOC, since Allstream seems to be part of zayo.  I also figured their NOC could earn some of the money we&#39;re paying them for transit.  If you&#39;re not a zayo customer,  YMMV.</div><div dir="auto"><br></div><div dir="auto">The report we got back was that some customer of Allstream was announcing our prefixes &quot;illegaly&quot; and filters had been applied.  They also implied a bit of clue would be dispensed.   Not sure if this is your issue or not. <br><br><div class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr">On Thu, Apr 9, 2020, 12:59 PM David Pieper &lt;<a href="mailto:david@davidpieper.com">david@davidpieper.com</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>Seeing some strange routing with Allstream and need to get it resolved. Please contact off list.<br></div><div><br></div><div>Thanks,<br></div><div>AS46276<br></div></blockquote></div></div></div>
</div>