<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"><meta name="Generator" content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang="EN-US" link="blue" vlink="purple"><div class="WordSection1"><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Yes, matches our time window.</span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Level3 did a very poor job managing this. NO network events still posted on their portal and NOC had no idea, while their team was obviously working to fix it in the background.</span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p><div><div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in"><p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> VoiceOps [mailto:<a href="mailto:voiceops-bounces@voiceops.org">voiceops-bounces@voiceops.org</a>] <b>On Behalf Of </b>Michael Lunsford<br><b>Sent:</b> Wednesday, February 25, 2015 10:39 AM<br><b>To:</b> Zak Rupas<br><b>Cc:</b> <a href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</a><br><b>Subject:</b> Re: [VoiceOps] Level 3 Issues</span></p></div></div><p class="MsoNormal"> </p><div><p class="MsoNormal">We had inbound TF failures from the Level3 Dallas NBS from approx 11:10 EDT to 12:20 EDT.</p></div><div><p class="MsoNormal"> </p></div><p class="MsoNormal"> </p><div><div><p class="MsoNormal">On Feb 25, 2015, at 12:24 PM, Zak Rupas <<a href="mailto:zak@simplesignal.com">zak@simplesignal.com</a>> wrote:</p></div><p class="MsoNormal"> </p><div><div><p class="MsoNormal">anyone engaged with Level 3 TAC being told any updates or reason why? I keep calling and get robo responses</p></div><div><p class="MsoNormal"><br clear="all"></p><div><div><div><div><div><div><div><p class="MsoNormal" style><span style="font-size:13.5pt;font-family:"Arial","sans-serif"">Zak Rupas</span><br><span style="font-size:8.5pt;font-family:"Arial","sans-serif"">VoIP Engineer<br><b>SimpleSignal</b><br>Anywhere: 303-242-8606</span></p><p class="MsoNormal" style><span style="font-size:8.5pt;font-family:"Arial","sans-serif""><img border="0" id="_x0000_i1025" src="https://docs.google.com/uc?export=download&id=0B4JIPE-HkXDaSERnbENRU05fSVE&revid=0B4JIPE-HkXDaVTZyVzZZZy9SUFZ0Rjl2NlNJRWNuclJLWjZrPQ"></span></p><p class="MsoNormal"> </p></div></div></div></div></div></div></div><p class="MsoNormal"> </p><div><p class="MsoNormal">On Wed, Feb 25, 2015 at 10:18 AM, Feby Francis <<a href="mailto:feby.francis@crosstel.com" target="_blank">feby.francis@crosstel.com</a>> wrote:</p><div><div><p class="MsoNormal" style>Looks like Level-3 inbound TF service is down for last 30 min. </p><p class="MsoNormal" style> </p><p class="MsoNormal" style>Anyone else with same problem.</p><p class="MsoNormal" style> </p><p class="MsoNormal" style>Feby Francis</p><p class="MsoNormal" style> </p><p class="MsoNormal" style><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> VoiceOps [mailto:<a href="mailto:voiceops-bounces@voiceops.org" target="_blank">voiceops-bounces@voiceops.org</a>] <b>On Behalf Of </b>Michael Jacobs<br><b>Sent:</b> Wednesday, February 25, 2015 12:06 PM<br><b>To:</b> <a href="mailto:voiceops@voiceops.org" target="_blank">voiceops@voiceops.org</a><br><b>Subject:</b> [VoiceOps] Level 3 Issues</span></p><p class="MsoNormal" style> </p><div><p class="MsoNormal" style>Anyone else having a large issue with Level 3?</p></div></div></div><p class="MsoNormal" style="margin-bottom:12.0pt"><br>_______________________________________________<br>VoiceOps mailing list<br><a href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</a><br><a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a></p></div><p class="MsoNormal"> </p></div><p class="MsoNormal">_______________________________________________<br>VoiceOps mailing list<br><a href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</a><br><a href="https://puck.nether.net/mailman/listinfo/voiceops">https://puck.nether.net/mailman/listinfo/voiceops</a></p></div></div><p class="MsoNormal"> </p></div></body></html>