Service provider being 16724? What bug? With the nexi?<span></span><br><br>On Tuesday, September 6, 2016, Bryan Fields &lt;<a href="mailto:bryan@flscg.org">bryan@flscg.org</a>&gt; wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Starting at about 20:27 EST tonight there was an outage on the uplink to our<br>
service provider.  We suspect this is the same issue as last time as our<br>
equipment kept on working but a suspected bug on the providers router caused<br>
traffic to die.<br>
<br>
We&#39;ve got them opening a ticket again with their vendor and hope we can<br>
resolve this happening.<br>
<br>
Sorry for the outage, but at least it&#39;s not our gear :D<br>
<br>
73&#39;s<br>
--<br>
Bryan Fields, W9CR<br>
Florida Simulcast Group, Inc.<br>
______________________________<wbr>_________________<br>
FSG-public mailing list<br>
<a href="javascript:;" onclick="_e(event, &#39;cvml&#39;, &#39;FSG-public@lists.keekles.org&#39;)">FSG-public@lists.keekles.org</a><br>
<a href="http://lists.keekles.org/cgi-bin/mailman/listinfo/fsg-public" target="_blank">http://lists.keekles.org/cgi-<wbr>bin/mailman/listinfo/fsg-<wbr>public</a><br>
</blockquote>