<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" 
      xmlns:thr="http://purl.org/syndication/thread/1.0">
  <link rel="alternate" type="text/html" href="http://blog.tmcnet.com/blog/tom-keating/voip/level-3-packet8-major-outage.asp" />
  <link rel="self" type="application/atom+xml" href="http://blog.tmcnet.com/blog/tom-keating/atom.xml" />
  <id>tag:blog.tmcnet.com,2013:/blog/tom-keating//4/tag:blog.tmcnet.com,2008:/blog/tom-keating//4.37048-</id>
  <updated>2013-02-22T21:04:46Z</updated>
  <title>Comments for <![CDATA[Level 3 &amp; Packet8 major outage]]></title>
  <subtitle>VoIP &amp; Gadgets blog - Latest news in VoIP &amp; gadgets, wireless, mobile phones, reviews, &amp; opinions</subtitle>
  <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.38</generator>
  <entry>
    <id>tag:blog.tmcnet.com,2008:/blog/tom-keating//4.37048</id>
    <link rel="alternate" type="text/html" href="http://blog.tmcnet.com/blog/tom-keating/voip/level-3-packet8-major-outage.asp" />
    <link rel="service.edit" type="application/atom+xml" href="http://blog.tmcnet.com/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=37048" title="Level 3 &amp; Packet8 major outage" />
    <published>2008-07-31T15:37:09Z</published>
    <updated>2008-07-31T17:41:47Z</updated>
    <title>Level 3 &amp; Packet8 major outage</title>
    <summary>BREAKING!A source is telling me that Level 3 Communications and Packet 8 are having a system-wide network outage for the last 30 minutes. Level 3 is a huge provider of VoIP termination and I believe Packet8 uses their network for...</summary>
    <author>
      <name>Tom Keating</name>
      <uri>http://blog.tmcnet.com/blog/tom-keating/</uri>
    </author>
    
    <category term="Packet8" />
    
    <category term="SIP" />
    
    <category term="TMCnet" />
    
    <category term="VoIP" />
    
    <content type="html" xml:lang="en" xml:base="http://blog.tmcnet.com/blog/tom-keating/">
      <![CDATA[BREAKING!<br />A source is telling me that <a href="http://www.level3.com">Level 3 Communications</a> and Packet 8 are having a system-wide network outage for the last 30 minutes. Level 3 is a huge provider of VoIP termination and I believe Packet8 uses their network for termination. Other VoIP service providers (Vonage?) will also be affected if indeed Level 3 is having an outage. I'm trying to confirm this as I type this. <br /><br />I'm currently on hold (5min so far) for Packet8's technical support and sent my contacts at 8x8 an email. I'll update this post when I find out more.<br /><br /><b>Update:</b> Just talked with Packet8 technical support and indeed they are experiencing outages. They also confirmed they use Level 3, so it appears Level 3 is the cause. Contacting Level 3 next. Stay tuned!<br /><br /><b>Update: 1:13pm</b><br />This from my source of the outage who I asked to keep me aprised of when service was restored. The outage seemed to have occured from approximately 11am EDT to 12:15pm EDT (1hr 15min long). He makes a good point about some VoIP customers being medical offices, which are obviously greatly affected by any sort of extended outage.<blockquote><div>Yes... I am an IT Management and Communications consultant - a few of my customers are Packet8 customers (mostly medical offices, which poses many potentially dangerous situations when phones go out).<br /><br />OK - As of 12:15pm EST Level 3 has restored their servers and service has been restored.<br /><br />PS - great blog, thanks for putting this out there...  Looks like a few companies need a crash course on Crisis Communications Management and Planning - "keep you publics informed"... (feel free to blog that too.)</div></blockquote><b>Update: 1:34pm</b><br />Just spoke with Packet8. The issue was due to a Packet8 database crash at Level3's data center. Level3's NOC itself did not experience an outage. Also, stuff was failed over and business customers experienced NO outage - only residential. <strike>I'll upload a recording of the call that explains everything in just a minute.</strike> <br /><br />Here's a <a href="http://blog.tmcnet.com/blog/tom-keating/sounds/packet8-level3.mp3">mp3 recording of my conversation</a> with Packet8 representatives.<br /><br /><b>Highlights of the conversation:</b><br />Packet8 was able to failover their business customers immediately. They were not affected at all. They prioritize the failover of their business customers over their residential. The residential customers would failover after 15 minutes or if they rebooted their device.<br /><br />Medical offices should <b>not</b> be affected if they use the business plan unless they use the softphone application or if they violate the ToS (terms of service) by going with the cheaper residential plan. (which shouldn't be used for business)<br />]]>
      
    </content>
  </entry>

  <entry>
    <id>tag:blog.tmcnet.com,2008:/blog/tom-keating//4.37048-comment:38595</id>
    <thr:in-reply-to ref="tag:blog.tmcnet.com,2008:/blog/tom-keating//4.37048" type="text/html" href="http://blog.tmcnet.com/blog/tom-keating/voip/level-3-packet8-major-outage.asp"/>
    <link rel="alternate" type="text/html" href="http://blog.tmcnet.com/blog/tom-keating/voip/level-3-packet8-major-outage.asp#c38595" />
    <title>Comment from Craig on 2008-07-31</title>
    <author>
        <name>Craig</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>Um.  I have 6 phone lines here, and a fax on the East Coast, and all work fine.  I didn't go down once.  We were up and running all day long.</p>]]>
    </content>
    <published>2008-07-31T16:59:50Z</published>
  </entry>

  <entry>
    <id>tag:blog.tmcnet.com,2008:/blog/tom-keating//4.37048-comment:38597</id>
    <thr:in-reply-to ref="tag:blog.tmcnet.com,2008:/blog/tom-keating//4.37048" type="text/html" href="http://blog.tmcnet.com/blog/tom-keating/voip/level-3-packet8-major-outage.asp"/>
    <link rel="alternate" type="text/html" href="http://blog.tmcnet.com/blog/tom-keating/voip/level-3-packet8-major-outage.asp#c38597" />
    <title>Comment from Carolyn Schuk on 2008-07-31</title>
    <author>
        <name>Carolyn Schuk</name>
        <uri>http://www.voipprincessblog.blogspot.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.voipprincessblog.blogspot.com">
        <![CDATA[<p>I've seen some Packet8 problems over that last week - calls not connecting or just getting a busy signal.  </p>]]>
    </content>
    <published>2008-07-31T17:25:06Z</published>
  </entry>

  <entry>
    <id>tag:blog.tmcnet.com,2008:/blog/tom-keating//4.37048-comment:38598</id>
    <thr:in-reply-to ref="tag:blog.tmcnet.com,2008:/blog/tom-keating//4.37048" type="text/html" href="http://blog.tmcnet.com/blog/tom-keating/voip/level-3-packet8-major-outage.asp"/>
    <link rel="alternate" type="text/html" href="http://blog.tmcnet.com/blog/tom-keating/voip/level-3-packet8-major-outage.asp#c38598" />
    <title>Comment from Alex on 2008-07-31</title>
    <author>
        <name>Alex</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>This is a very interesting piece of info, since the medical office in question is on a Virtual Office business plan and was out for nearly 75 minutes - no dial tone, dead-air on pickups - on all 12 extensions.</p>

<p>The auto-attendant answered calls, but caller choices were only routed to voicemail - no live operators.  Having tested it myself the entire time of the outage, I guarantee this.</p>

<p>In addition, I find it interesting that my first 8 calls to tech support were all transferred to dead-air, eventually being disconnected after approximately 2 minutes of wait-time.</p>]]>
    </content>
    <published>2008-07-31T17:53:17Z</published>
  </entry>

  <entry>
    <id>tag:blog.tmcnet.com,2008:/blog/tom-keating//4.37048-comment:38599</id>
    <thr:in-reply-to ref="tag:blog.tmcnet.com,2008:/blog/tom-keating//4.37048" type="text/html" href="http://blog.tmcnet.com/blog/tom-keating/voip/level-3-packet8-major-outage.asp"/>
    <link rel="alternate" type="text/html" href="http://blog.tmcnet.com/blog/tom-keating/voip/level-3-packet8-major-outage.asp#c38599" />
    <title>Comment from Craig on 2008-07-31</title>
    <author>
        <name>Craig</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>There has been absolutely no problems with QoS from Packet8 Virtual Office over the past week, or past month, or ever for that matter.</p>

<p>I can't speak of Residential (we are a business using several business lines and fax).</p>]]>
    </content>
    <published>2008-07-31T18:01:20Z</published>
  </entry>

  <entry>
    <id>tag:blog.tmcnet.com,2008:/blog/tom-keating//4.37048-comment:38601</id>
    <thr:in-reply-to ref="tag:blog.tmcnet.com,2008:/blog/tom-keating//4.37048" type="text/html" href="http://blog.tmcnet.com/blog/tom-keating/voip/level-3-packet8-major-outage.asp"/>
    <link rel="alternate" type="text/html" href="http://blog.tmcnet.com/blog/tom-keating/voip/level-3-packet8-major-outage.asp#c38601" />
    <title>Comment from Mike on 2008-07-31</title>
    <author>
        <name>Mike</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>RE a crash course on Crisis Communications Management and Planning - "keep you publics informed"</p>

<p>it was great watching this unfold.  I am currently putting together  a report on crisis communications at my company.  this was a valuable lesson in both what to and what not to do</p>]]>
    </content>
    <published>2008-07-31T19:01:19Z</published>
  </entry>

  <entry>
    <id>tag:blog.tmcnet.com,2008:/blog/tom-keating//4.37048-comment:38602</id>
    <thr:in-reply-to ref="tag:blog.tmcnet.com,2008:/blog/tom-keating//4.37048" type="text/html" href="http://blog.tmcnet.com/blog/tom-keating/voip/level-3-packet8-major-outage.asp"/>
    <link rel="alternate" type="text/html" href="http://blog.tmcnet.com/blog/tom-keating/voip/level-3-packet8-major-outage.asp#c38602" />
    <title>Comment from Eric on 2008-07-31</title>
    <author>
        <name>Eric</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>We have many Packet 8 phone lines. Didn't experienced any issue. </p>]]>
    </content>
    <published>2008-07-31T19:32:42Z</published>
  </entry>

  <entry>
    <id>tag:blog.tmcnet.com,2008:/blog/tom-keating//4.37048-comment:38603</id>
    <thr:in-reply-to ref="tag:blog.tmcnet.com,2008:/blog/tom-keating//4.37048" type="text/html" href="http://blog.tmcnet.com/blog/tom-keating/voip/level-3-packet8-major-outage.asp"/>
    <link rel="alternate" type="text/html" href="http://blog.tmcnet.com/blog/tom-keating/voip/level-3-packet8-major-outage.asp#c38603" />
    <title>Comment from C on 2008-07-31</title>
    <author>
        <name>C</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>For the most part this guy can make calls out but nothing is coming in.</p>

<p>Location = Mass</p>]]>
    </content>
    <published>2008-07-31T19:52:47Z</published>
  </entry>

  <entry>
    <id>tag:blog.tmcnet.com,2008:/blog/tom-keating//4.37048-comment:38605</id>
    <thr:in-reply-to ref="tag:blog.tmcnet.com,2008:/blog/tom-keating//4.37048" type="text/html" href="http://blog.tmcnet.com/blog/tom-keating/voip/level-3-packet8-major-outage.asp"/>
    <link rel="alternate" type="text/html" href="http://blog.tmcnet.com/blog/tom-keating/voip/level-3-packet8-major-outage.asp#c38605" />
    <title>Comment from Robert Basye on 2008-07-31</title>
    <author>
        <name>Robert Basye</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>I just contacted customer service has no idea when they will be fixed </p>

<p>Location KY</p>]]>
    </content>
    <published>2008-07-31T20:29:53Z</published>
  </entry>

  <entry>
    <id>tag:blog.tmcnet.com,2008:/blog/tom-keating//4.37048-comment:38606</id>
    <thr:in-reply-to ref="tag:blog.tmcnet.com,2008:/blog/tom-keating//4.37048" type="text/html" href="http://blog.tmcnet.com/blog/tom-keating/voip/level-3-packet8-major-outage.asp"/>
    <link rel="alternate" type="text/html" href="http://blog.tmcnet.com/blog/tom-keating/voip/level-3-packet8-major-outage.asp#c38606" />
    <title>Comment from Kevin on 2008-07-31</title>
    <author>
        <name>Kevin</name>
        <uri>http://www.infodefense.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.infodefense.com">
        <![CDATA[<p>We have the new 675x SIP phones. We are still down. Our phones have been out since about 10:00 CST.  Our location is Dallas, TX.</p>

<p>I was able to reach Packet8 Tech support immediately both times I called today (from a different phone).  They were helpful, offering to call me when the service is restored.  I think it would be helpful if they offered updates from their web site, however.</p>]]>
    </content>
    <published>2008-07-31T21:30:45Z</published>
  </entry>

  <entry>
    <id>tag:blog.tmcnet.com,2008:/blog/tom-keating//4.37048-comment:38628</id>
    <thr:in-reply-to ref="tag:blog.tmcnet.com,2008:/blog/tom-keating//4.37048" type="text/html" href="http://blog.tmcnet.com/blog/tom-keating/voip/level-3-packet8-major-outage.asp"/>
    <link rel="alternate" type="text/html" href="http://blog.tmcnet.com/blog/tom-keating/voip/level-3-packet8-major-outage.asp#c38628" />
    <title>Comment from Alex on 2008-08-01</title>
    <author>
        <name>Alex</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>I am utterly disappointed by Packet8's response to this situation.  Having listened to the audio recording and reading all subsequent blogs and articles written on the matter, I cannot grasp the reasoning behind Martin's remarks.</p>

<p>As the IT consultant for THE medical office in question, I sincerely resent the statement that, "if you were one of our business customers, you were not affected.”  This office, in addition to others who commented on this blog, did lose connection for extended periods; ours lasting for a total of 75 minutes.  For an office of approximately 20 employees in a critical medical capacity, this was unacceptable.  Furthermore, to insinuate that my client "opted – as they shouldn’t – for a cheaper residential line" is an outrage and a blatant disregard or even an acknowledgment of our communications loss.</p>]]>
    </content>
    <published>2008-08-01T15:02:55Z</published>
  </entry>

  <entry>
    <id>tag:blog.tmcnet.com,2008:/blog/tom-keating//4.37048-comment:51996</id>
    <thr:in-reply-to ref="tag:blog.tmcnet.com,2008:/blog/tom-keating//4.37048" type="text/html" href="http://blog.tmcnet.com/blog/tom-keating/voip/level-3-packet8-major-outage.asp"/>
    <link rel="alternate" type="text/html" href="http://blog.tmcnet.com/blog/tom-keating/voip/level-3-packet8-major-outage.asp#c51996" />
    <title>Comment from Dan bohn on 2010-01-12</title>
    <author>
        <name>Dan bohn</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>We are a small business in Oakland CA and still have no service at 1:38 pm</p>]]>
    </content>
    <published>2010-01-12T21:33:29Z</published>
  </entry>

  <entry>
    <id>tag:blog.tmcnet.com,2008:/blog/tom-keating//4.37048-comment:52000</id>
    <thr:in-reply-to ref="tag:blog.tmcnet.com,2008:/blog/tom-keating//4.37048" type="text/html" href="http://blog.tmcnet.com/blog/tom-keating/voip/level-3-packet8-major-outage.asp"/>
    <link rel="alternate" type="text/html" href="http://blog.tmcnet.com/blog/tom-keating/voip/level-3-packet8-major-outage.asp#c52000" />
    <title>Comment from hr on 2010-01-12</title>
    <author>
        <name>hr</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>We have been out and at almost 5 we are still out of all service. We are on a business plan so I dont get that<br />
We are in Dallas Texas. Tried to go to customer service no response and phones there must have been overwhelmed<br />
Still down</p>]]>
    </content>
    <published>2010-01-12T22:53:23Z</published>
  </entry>

</feed>
